Wire
14:46ZTWOMAJORSFwd from @📝Everyone on the Caspian got worried📝Following the AFU strike on an Iranian vessel and the escala…14:45ZIDFOFFICIAIDF: A short while ago, a drone was located in the area of Kibbutz Nahal Oz.Following a review, it was determ…14:45ZNOELREPORTRomania declared a Russian embassy staff member persona non grata after repeated violations of its airspace b…14:45ZDDGEOPOLITYemen says it has expanded its campaign against Saudi Arabia’s oil infrastructure in retaliation for Saudi dr…14:45ZSHAAMNETWOSham|| Theft in law.. When does it become a felony? ..Here are the details14:44ZSHAAMNETWOSham || The Drug Control Administration foils the smuggling of 850,000 narcotic pills coming from Lebanon in…14:44ZTASNIMNEWSThe crash of an unidentified drone in the north of Babil, Iraq🔹 Local sources reported the crash of an unide…14:43ZALALAMARABthe IDF: A bomb-laden drone fell in the Gaza Strip, and we are examining whether it was launched from the Str…
  • Europe ETF 0.78%
  • BTC 1.20%
  • ETH 3.90%
  • BNB 0.60%
Terminal ↗
← The MonexusGeopolitics

Iran fires ballistic missiles from Jam toward Bahrain in overnight strike

Telegram channels circulated footage of short-range ballistic missiles launched from the Iranian city of Jam toward Bahrain on 13 July 2026, with OSINT accounts flagging US facilities as the apparent target. Smoke was reported rising from the island kingdom within twenty minutes of launch.

Split image showing the blue and white IAEA logo on the left and a weathered yellow radioactive warning symbol painted on a dark textured surface on the right.
Split image showing the blue and white IAEA logo on the left and a weathered yellow radioactive warning symbol painted on a dark textured surface on the right. @bricsnews · Telegram

At 01:56 UTC on 13 July 2026, the Telegram channel Middle East Spectator posted video it described as footage of Iranian ballistic missiles being launched toward Bahrain. Within thirteen minutes, a second channel, wfwitness, had circulated its own clip identifying the launch point as the Iranian city of Jam, and by 02:01 UTC the OSINT-focused account Osinttechnical had framed the salvo as targeting US forces on the island, reposting to X. At 02:09 UTC wfwitness carried footage of projectiles in flight, and by 02:18 UTC the same channel was sharing what it labelled unconfirmed imagery of smoke rising from Bahraini territory following an alleged impact.

The pattern of the first two hours is familiar from past escalations between Tehran and the Gulf: rapid churn of low-resolution launch footage, an OSINT account naming the apparent target, then geolocated aftermath imagery circulated before any government has issued a confirmed read-out. The substantive questions (who fired, at what, and with what effect) are still ahead of the available evidence, but the geography alone is enough to put the Gulf on a fresh footing.

What the footage shows, and what it doesn't

The Middle East Spectator clip is a horizontal ground-to-air view of what appears to be a missile lifting off, consistent with a transporter erector launcher (TEL) posture. The wfwitness material, posted in two tranches, adds a second angle and labels the origin point as Jam, a small city in southern Iran near the Strait of Hormuz coast. Osinttechnical's repost, hosted on X, characterises the salvo as short-range ballistic missiles fired toward US forces in Bahrain. No official Iranian, Bahraini, US, or coalition statement had been recorded in the channels surveyed as of 02:18 UTC.

Read together, the materials establish three things and stop short of a fourth. They establish that missiles were launched from Iranian territory. They establish that the destination named by OSINT accounts was Bahrain. They establish that smoke was visible from Bahraini soil in the immediate aftermath. What they do not establish, at least within the window covered by the source material, is the precise target set, the weapon type, the number of launchers involved, or whether US Fifth Fleet facilities at Manama or the wider Naval Support Activity Bahrain complex were the intended aim point. Telegram attribution to "US forces" is, at this stage, an OSINT characterisation rather than a confirmed Pentagon or CENTCOM read-out.

Why Jam, and why Bahrain

Jam sits on the Gulf of Oman coast of Hormozgan province, a launch geography that has appeared in earlier Iranian drills and in strikes associated with the IRGC's naval and missile apparatus. The line of flight from Jam to Manama is roughly 400 kilometres across the water, well inside the operational envelope of Iran's short-range ballistic missile inventory. Bahrain hosts the US Navy's Fifth Fleet headquarters and the British Royal Navy's forward-deployed minehunter squadron, alongside a small contingent of allied forces; it is one of two Gulf states (the other being Qatar, home to Al Udeid) where the US maintains its most concentrated forward military presence in the region.

The targeting logic, if the OSINT framing holds, would mirror what Iranian planners have signalled in exercises for years: a counter-value option aimed not at Israeli or US mainland territory but at the hard infrastructure of the US presence in the Gulf, where the optics of a strike on a partner state carry both deterrent and political weight. The Iranian calculus, in plain terms, is that hitting facilities that host foreign forces on Arab soil raises the cost of any future escalation cycle for Washington without crossing the threshold that would trigger a US retaliatory doctrine aimed at the Iranian homeland.

What comes next, and what to watch for

Three signals will arrive before any of this resolves. First, a Bahraini government statement, almost certainly through the Ministry of Foreign Affairs, will set the domestic political frame and indicate whether Manama is treating the incident as an attack on its territory or as fallout affecting the US compounds inside it. Second, a CENTCOM read-out from Tampa, or a US Embassy Manama security message, will either confirm or downgrade the OSINT characterisation that US forces were the target. Third, Iranian state-aligned channels (Tasnim, PressTV, IRNA) will either claim the strike as a deliberate act or maintain the same ambiguity Tehran has used after past operations, allowing deniability while basking in regional coverage.

The structural pattern is what makes the geography matter. The Gulf is the corridor through which a significant share of seaborne energy moves, and the US presence in Bahrain and Qatar is the muscle that underwrites the security guarantee for that traffic. A strike on a single Gulf installation does not, on its own, change the calculus of the chokepoint. A strike that goes unanswered, or answered in a way that allows Tehran to claim deterrence success, does. The next 24 to 48 hours will tell which track the parties have chosen.

What remains uncertain

The source material does not specify casualties, damage assessments, the number of missiles launched, or whether any were intercepted. It does not record any claim of responsibility from Tehran, any confirmation of impact from Manama, or any US statement from Washington, Tampa, or the embassy. The "unconfirmed" caveat attached to the Bahraini smoke imagery by wfwitness is worth keeping in view; the OSINT layer is, by design, faster than the official one, and the official read-out is the one that will tell readers what, in fact, happened on the ground in the early hours of 13 July 2026.

This article was assembled from open-source Telegram and X posts circulating in real time; the desk will update the wire as official statements from Manama, Washington, and Tehran become available.

Wire provenance

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

  • https://t.me/Middle_East_Spectator
  • https://t.me/wfwitness
  • https://twitter.com/Osinttechnical/status/2076486091385851988
  • https://t.me/wfwitness
  • https://t.me/wfwitness
© 2026 Monexus Media · AI-native reporting from public-source material