Iran claims overnight strikes across Bahrain, Oman, Jordan and Kuwait: what is corroborated, what is not
Three Telegram channels report Iranian strikes on US-linked targets across four Gulf states overnight. Independent verification is thin, and the framing on each side serves a different audience.

At 05:18 UTC on 13 July 2026, the Telegram channel abualiexpress posted that Iran's Islamic Revolutionary Guard Corps had begun taking responsibility, on an hourly cadence, for attacks on American targets inside Jordan, Kuwait and Bahrain, framed as retaliation for overnight US strikes.
Within two hours, a second account, rnintel, added geographic specificity: Iran was claiming hits on US military assets in Juffair, the main US Navy base in Bahrain, and on radar sites in Oman, while both Jordan and Kuwait had separately confirmed Iranian attacks overnight. By 07:15 UTC, a third channel, englishabuali, reported that the IRGC had formally claimed responsibility for the strike on US radar systems in Oman and for this morning's attacks in Jordan.
The shape of the morning is consistent across three accounts: an Iranian retaliatory barrage spanning four host states of US Central Command, claimed on a rolling basis by Tehran. The corroboration underneath that picture is much thinner than the headline suggests.
The corridor, not the incident
Juffair hosts the US Naval Forces Central Command and the Fifth Fleet, the principal maritime hub for operations across the Gulf and the Strait of Hormuz. Radar sites in Oman sit on the southern flank of the same chokepoint, providing early warning for ballistic-missile defence and maritime surveillance. Jordan and Kuwait extend the theatre west and north, putting air bases used by US and coalition air operations within reach of Iran's ballistic and cruise-missile inventory.
Read together, the four reported target sets describe not four separate incidents but a single, layered strike package: a maritime headquarters in Bahrain, an early-warning node in Oman, and two air bases along the arc that connects the Gulf to the Levant. That is the geometry of someone trying to degrade the integrated air-and-maritime picture, not someone picking fights. The Iranian framings circulated on Telegram cast the operation as retaliation for unspecified American attacks earlier the same night, an inversion that puts Washington on the back foot in the information war before the kinetic one has been fully assessed.
What is corroborated
The strongest claim in the cluster is the one from rnintel at 07:10 UTC: that Iran says it struck US military assets in Juffair and radar sites in Oman, and that Jordan and Kuwait have confirmed Iranian attacks on their territory overnight. The phrase "Jordan and Kuwait have both confirmed Iranian attacks overnight" is a direct assertion that two host governments, neither of them Iranian, are on the record acknowledging inbound fire. That kind of confirmation usually travels fast through wire services and through the targeted countries' own press offices; its presence on a second-channel Telegram post at 07:10 UTC suggests a basis that goes beyond Tehran's own communiques.
Beyond that, the picture is a chain of attributions. abualiexpress frames the cadence as "hourly responsibility," a phrase that implies the IRGC is putting out claims in tranches rather than a single statement. englishabuali, two hours later, repeats the same claim structure: the IRGC has claimed responsibility, first for the Oman radar strike, then for the Jordan attacks. Neither post reproduces an IRGC press release, a Telegram statement from Sepah News, or a direct link to an official channel; both paraphrase, in idiomatic but unsourced English, what "the Guards" have allegedly said.
What is not corroborated
Independent reporting from Reuters, the BBC, Al Jazeera, the wires that cover this beat by profession, has not been published in the thread context at the time of these posts. The claims are exclusively Iranian-attributed and Iranian-channel-mediated. That matters because in a fast-moving overnight exchange the first wave of reporting almost always arrives through state-affiliated or sympathetic channels, and the second wave, the one that arrives in the public domain twelve to twenty-four hours later, is what tells you what actually happened.
Two specific gaps stand out. First, no casualty figures, on either the US or the Iranian side, have appeared in any of the three posts. Second, no defence ministry in Jordan, Kuwait, Bahrain or Oman has been quoted in the thread context. The "Jordan and Kuwait have confirmed" line in rnintel is a single-source claim on a Telegram channel; until the Jordanian or Kuwaiti armed forces publish their own statements, it sits in the same evidentiary category as the Iranian claims.
What we verified, and what we could not
Verified by the threads themselves: that an Iranian-attributed claim of strikes against US-linked targets in Jordan, Kuwait, Bahrain and Oman was circulating across at least three Telegram accounts between 05:18 and 07:15 UTC on 13 July 2026. Verified: that the geographic description names real, identifiable US facilities (Juffair, radar sites in Oman, presumably Muwaffaq al-Salti or a similar known installation). Verified: that the framing, retaliation for overnight US action, inverts the standard sequencing in which US strikes precede Iranian retaliation by hours, not minutes.
Not verified: the strike inventory itself, including which sites were actually hit, by what munitions, and with what effects. Not verified: any casualty count, on either side. Not verified: the Jordanian or Kuwaiti official confirmation referenced by rnintel. Not verified: that the IRGC itself put out the claims attributed to it, rather than a parallel channel speaking for it. Not verified: the underlying premise that the United States struck Iranian targets overnight, the event the Iranian channels cite as the trigger.
The sources do not specify whether the IRGC publicised its claims through Sepah News, through state media, or only through Telegram intermediaries. They do not specify whether the strikes were simultaneous or sequential. They do not specify whether Oman, which has historically avoided being drawn into US-Iran confrontations, is the subject of a confirmed strike or a reported one.
The framing question
Iranian state-aligned messaging, even when routed through Telegram rather than PressTV or Tasnim, has its own grammar. Claims of "hourly responsibility" tell the domestic audience that the operation is large and ongoing; listing four host states tells the regional audience that no US posture is out of reach; inverting the sequence to claim the United States struck first tells an international audience the war was started by Washington. The same facts, if they are facts, can be made to carry very different loads.
An alternative reading, that the Iranian channels are amplifying partial reporting before independent verification, cannot be ruled out by the source material. It is the default reading of any set of claims that originate entirely from one side of a conflict and have not yet been touched by a non-aligned wire.
What to watch before next publish
The proof points will not be on Telegram. They will be CENTCOM briefings, statements from the Bahraini, Omani, Jordanian and Kuwaiti defence ministries, satellite imagery of the named sites in the twelve to twenty-four hours after the strikes, and casualty or damage reports from medical and military sources on each side. Until then, the picture is one of an Iranian-attributed, multi-state, geographically coherent strike package, claimed but not corroborated. It is not nothing. It is also not enough.
Desk note: Monexus is treating the cluster of Telegram posts as a single, low-confidence originating event rather than three independent reports. The framing on Iranian-aligned channels tends toward maximalist attribution; the framing on US and Gulf state channels, when it arrives, will compress and qualify. Both are real pressures on the same record, and the editorial job is to keep them separate until the wire catches up.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/abualiexpress
- https://t.me/rnintel
- https://t.me/englishabuali