Missiles from Khomeyn: Iran strikes Iraqi Kurdistan as Erbil hears explosions

At 09:28 UTC on 18 July 2026, the open-source channel AMK Mapping logged at least two ballistic missile launches from Khomeyn, a town in Iran's western Markazi province. Twenty-two minutes later, witnesses in Erbil reported hearing explosions, and AMK followed with a second bulletin at 09:50 UTC tying the salvo, including accompanying drones, to Iraqi Kurdistan. The sequence, captured almost in real time by two independent Telegram feeds, is the clearest public record yet of a direct Iranian strike on the Kurdish-administered north of Iraq in the current escalation cycle.

The strikes land inside a long-running shadow war between Tehran and the Kurdish parties that host Iranian opposition movements on Iraqi soil. Erbil is the political centre of the Kurdistan Region of Iraq and the home of several Iranian Kurdish factions whose presence Iran has repeatedly demanded be shut down. The geometry is familiar: missiles arc west from Iran, drones glide low, and explosions echo across a city that doubles as a regional air hub and a base for US and coalition personnel. What is new is the public traceability of the salvo within an hour, and the willingness of Iranian-adjacent analysts to attach the launch site by name.

What the open-source record shows

AMK Mapping's first alert specified at least two ballistic missile launches originating from Khomeyn. The second alert, twenty-two minutes later, added that missiles and drones "likely targeted Iraqi Kurdistan," with explosions heard in Erbil. A separate channel, WFWitness, corroborated the explosions on the ground in Erbil at roughly the same timestamp. Two independent feeds, both oriented to the Iranian operational theatre, agreeing on direction and effect in under thirty minutes is a high standard for this kind of incident. The thread does not specify munitions type, warhead yield, point of impact, or casualties; AMK's language is deliberately cautious ("likely targeted"), which is the right register for the data available.

The provenance matters. AMK Mapping is an open-source account that tracks Iranian military activity from commercial satellite, flight-tracking, and on-the-ground corroboration. It is not a wire service and not a party to the conflict. Its bulletins are best read as a starting ledger: here is a launch, here is a downstream effect, here is a probable vector. Readers looking for confirmed targets, intercept data, or attribution statements from Tehran, Baghdad, or Erbil will have to wait for state and wire confirmations, which had not appeared in the feeds captured for this brief at the time of publication.

The Erbil question

Erbil has been a recurring target for Iranian-aligned actors. Tehran has framed previous strikes on Iraqi Kurdistan as defensive, arguing that the territory hosts Iranian Kurdish opposition groups, principally the KDPI and PJAK, whose presence threatens Iranian border security. The framing is contested in Baghdad and Erbil, where both the federal government and the Kurdistan Regional Government balance a security relationship with Washington and a commercial and energy relationship with Tehran. Strikes on Erbil put that balance under acute pressure, because the city also hosts a US Consulate, a long-standing coalition presence, and the offices of foreign oil companies. A missile landing in Erbil is, in practice, a missile landing inside a multi-power diplomatic compound, whether or not any particular projectile is aimed at Western personnel.

The counter-read is that Erbil strikes have, in past cycles, been narrowly targeted at Iranian-opposition offices or compounds on the city's outskirts, and the explosion reports captured here do not specify a hit site. A reader looking for the most optimistic version of the events could read the audible explosions as either a successful strike on a discrete Iranian-opposition target, an interception by Kurdish or coalition air defence, or a debris impact. None of those can be confirmed from the captured feeds, and each implies a different political outcome.

What this fits

The salvo is the latest data point in a multi-year pattern: Iranian ballistic and drone launches from western Iranian launch belts directed at targets in Iraqi Kurdistan, Tel Aviv-adjacent sites in the Levant, or Syrian infrastructure, often packaged with simultaneous messaging aimed at domestic audiences. The shared geometry is short range, west-trending, and pointed at non-state or quasi-state adversaries inside countries that Iran does not want to formally war with. That pattern is part of why these strikes are hard to attribute in real time; they are designed to be deniable at the strategic level while being obvious at the tactical level. AMK's paired alerts make the tactical layer harder to obscure.

There is also a regional context. The Iran-Iraq border in the south and the Iran-Kurdistan border in the west have been tense since Iran's domestic crackdown following the 2022–23 protest cycle and the parallel Israeli campaign against Iranian-axis assets further west. Strikes on Erbil put Baghdad in a familiar bind: the federal government has condemned previous Iranian strikes on Iraqi soil as a violation of sovereignty, while avoiding any action that would sever the Iranian gas and electricity flows on which Iraqi grid stability depends. The Kurdish authorities in Erbil have a parallel incentive to keep both Tehran and Washington comfortable, which is hard to do when ballistic missiles are landing inside the provincial capital.

What remains uncertain

The captured feeds do not specify casualty figures, the precise point of impact, the type of warhead, or whether any projectile was intercepted. They do not name a target. They do not carry any Iranian state-media confirmation, Iraqi federal statement, KRG statement, or US/coalition attribution. The most a reader can responsibly say at 09:50 UTC on 18 July 2026 is: ballistic missiles and drones were launched from Khomeyn in western Iran, and explosions were heard in Erbil at a roughly consistent timestamp. The next data points to watch are an Iranian statement, an Iraqi federal or KRG statement, satellite imagery of any impact crater or structural damage, and any debris analysis that would identify the specific Iranian missile family in use. Until at least one of those lands, this article is a record of an observed sequence, not a finding of intent.

The structural bet is unchanged: Iran continues to use short-range fires to police its periphery while preserving its strategic ambiguity, and Iraqi Kurdistan continues to absorb the cost of hosting the actors Tehran wants silenced. Erbil's residents hear the explosions either way.

Desk note: Monexus is reporting from open-source Telegram feeds rather than wire confirmation, because the wire cycle had not closed on this incident at the time of publication. The framing privileges what the feeds actually show (a launch, a sound, a probable vector) over what they do not (casualties, targets, attribution). When wire confirmation arrives, this article will be updated; the underlying geometry of the salvo will not change.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/s/AMK_Mapping
• https://t.me/s/AMK_Mapping
• https://t.me/s/wfwitness