Iran strikes US bases in Bahrain with ballistic missiles launched from Jam

Short-range ballistic missiles left southern Iran just before 02:00 UTC on 13 July 2026, arced across the Gulf, and hit multiple US-occupied sites in Bahrain, where fire and smoke have since been visible across several bases. Iranian state-aligned outlets and Persian-language channels framed the salvo as a deliberate strike against American military targets; on-the-ground accounts in Bahrain described warning sirens and explosions near the installations.

What began as a Telegram-circulated launch video has hardened, in the space of three hours, into a clearly visible campaign: smoke covering the skies over parts of the host nation, fires at multiple bases, and a coordinated set of claims from Tehran that this was intentional. The trajectory, the launch origin, and the chosen target set suggest a calibrated message rather than a miscalculation.

What the first two hours looked like

At 01:56 UTC the channel Middle East Spectator posted launch footage it identified as Iranian ballistic missiles bound for Bahrain. Five minutes later, the OSINT-focused account @Osinttechnical shared what it called a "technical salvo" on X, naming the launch point as Jam, a city in Iran's southern Bushehr Province on the Persian Gulf coast, and the destination as US forces in Bahrain. By 02:05 UTC, Fars News International, the English arm of outlets close to the Islamic Revolutionary Guard Corps, was reporting explosions and warning sirens at the US base. Smoke-plume imagery began circulating at 02:18 UTC. By 03:35 UTC, Tasnim, another Iranian state-aligned outlet, was describing smoke and fire at "American bases in Bahrain," saying the plumes had covered skies across the country's regions. An hour later, Press TV confirmed the picture in English-language terms, with smoke rising over "US military bases and strategic assets" and fires at multiple sites.

The sequencing matters. It is unusual to have launch footage, a named launch point, a named target, on-the-ground audio of sirens, and visual confirmation of fires all circulate within roughly two and a half hours. That density of self-attributed evidence is itself a signal about how Tehran wants the strike read.

The launch: Iran doing what Iran says it will do

Iranian state-aligned outlets are explicit about responsibility. The language in the Fars and Tasnim reports refers not to a "missile incident" but to attacks on "American military targets." Press TV's framing, also in English, names the affected sites as US bases and "strategic assets." The fact that an Iranian short-range ballistic missile salvo travelled from Jam across roughly 200 miles of Gulf water and produced visible damage inside a host nation that hosts the US Navy's Fifth Fleet is not in dispute among these sources; what differs is whether the engagement is described as an act of war, a calibrated retaliation, or a symbolic strike.

There is, for now, no independent casualty count in circulation, and no on-the-record comment from US Central Command or the Bahraini government in the items available. What can be said from the available material is the direction, type, and apparent effect of the strike.

The message behind the launch point

Launching from Jam is not a coincidence of geography. Jam sits in a corridor along Iran's southern coast that has hosted missile operations in previous confrontations and gives Iranian forces a short, low-trajectory shot across the Gulf toward Bahrain's Manama area and the installations clustered around it. The choice of short-range ballistic missiles, rather than the longer-range systems Iran has demonstrated in the past, also signals range-discipline: this salvo was built to hit what's in front of it, not to demonstrate intercontinental reach. Combined with the speed of publication in Persian and English, the pattern fits a model in which Iran is interested less in plausible deniability than in being clearly seen as the actor.

That clarity is unusual inside the conventions of the region, where states tend to deny or obfuscate. The fact that Iranian state-aligned outlets are naming the strike, naming its target, and circulating visual evidence is part of the message. Iran's wartime communication has in past cycles prioritised attribution only when it considered attribution useful.

What we verified and what remains uncorroborated

Verified from the source set available to this publication: launch footage from a southern Iranian origin point circulating at 01:56 UTC on 13 July; a claim, with attached video, by an OSINT account identifying the launch point as Jam and the target as US forces in Bahrain at 02:01 UTC; reports from Fars News International of warning sirens and explosions at a US base; visual evidence of smoke over Bahrain beginning 02:18 UTC; Tasnim's report at 03:35 UTC describing smoke and fire across American bases in Bahrain; Press TV's English-language confirmation at 04:20 UTC that smoke and fires were visible at multiple US sites.

Not verified, and not in evidence in the source set: any official statement from the Bahraini Ministry of Foreign Affairs, the US Department of Defense, or US Central Command; any casualty count, on either side; any independent on-the-ground reporting from Bahraini outlets not in the Iranian state-aligned cluster; any technical assessment of which base or bases were struck and what damage was sustained; any statement of Iranian intent at the political level, as distinct from the operational messaging of Fars, Tasnim, and Press TV.

This distinction matters. The Iranian state-aligned outlets used here should be read as Iran's chosen communication channel, not as independent confirmation of facts they would otherwise have an interest in shaping. Where their reports converge with OSINT visual evidence, confidence rises. Where they stand alone, the picture is materially incomplete.

What to watch next

The next 12 to 24 hours will determine whether this was a one-off salvo or the opening move of a wider campaign. The signals worth tracking are straightforward and short: any statement from US Central Command or the Pentagon, which would shift the picture from "what Iran says it did" to "what the United States concedes was done to it." Any second salvo reported from Jam or another southern launch site. Any statement from Manama describing what landed on Bahraini soil. Any wider Iranian messaging, in Arabic or English, framing this in a broader strategic context.

Until those four arrive, the record reads: a named launch point, a named target type, visible fires, and silence from the principal parties whose bases were hit. That silence is itself information.

How Monexus framed this versus the wire: we are publishing on the operational record as it stands at the time of writing, with explicit attribution to Iranian state-aligned outlets as such, rather than laundering their reports into undated prose. Where Western wire confirmation exists, we will fold it in; until then, the ledger above is what is verifiable.

Wire provenance

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

• https://t.me/Middle_East_Spectator
• https://twitter.com/Osinttechnical/status/2076486091385851988/video/1
• https://t.me/FarsNewsInt
• https://t.me/wfwitness
• https://t.me/JahanTasnim
• https://t.me/presstv