Reports of US strikes inside Iran surface across Iranian state media
Iranian state outlets carried unverified reports of explosions in two southern provinces on 12 July 2026, framing the incidents as US strikes. No US or independent confirmation has appeared.
At 22:05 UTC on 12 July 2026, Press TV, the Iranian state broadcaster's English-language feed, posted a breaking alert: "Reports of several blasts in Iran's southern province of Sistan and Baluchestan after US strikes." Within eleven minutes, the same channel had added a second claim, heavy explosions in the southeastern city of Ahvaz, attributed by an "Ahvaz provincial official" to US action against two locations. By 22:28 UTC, the channel had folded both reports into a single thread attributing strikes to Ahvaz and, separately, circulating footage it described as the aftermath of a strike in Bandar Abbas, on the Persian Gulf coast.
What this publication can verify is narrow. As of 22:28 UTC on 12 July 2026, the only sources carrying the strikes are Press TV, the official Iranian outlet, and a Telegram aggregator ("wfwitness") that republishes Press TV's reporting in real time. No US military command release, no Pentagon briefing transcript, no statement from Central Command, and no wire-service confirmation from Reuters, the Associated Press, or Agence France-Presse appears in the visible record. The geography itself is unusual: Ahvaz sits in Khuzestan, on the Iranian side of the Shatt al-Arab waterway, more than 1,000 kilometres from Sistan and Baluchestan, which runs along Iran's southeastern border with Pakistan. A simultaneous strike package across both provinces would be an operationally distinct pair of missions, not a single engagement. The sources do not reconcile the two reports.
What the Iranian framing looks like
Press TV is not a neutral wire. It is the English-language voice of the Islamic Republic of Iran, funded through state broadcasting and operating under the supervision of the government. Reporting it carries reflects the editorial line of the Iranian state at the moment of broadcast: in a fast-moving kinetic situation, that means amplifying claims of enemy action, naming a US perpetrator, and pinning attribution to a named provincial official before independent verification is possible. The channel's use of the red "🔴" breaking badge across three posts in twenty-three minutes, and its citation of an "Ahvaz provincial official" by title only, fits a familiar pattern in Iranian state-media handling of internal security incidents: name a US or Israeli perpetrator first, let allies and intermediaries amplify, and allow any later correction to be quietly buried.
The republication chain matters. "wfwitness," the Telegram account that reposted both Press TV alerts and added the Ahvaz Airport detail, is an aggregator with a track record of amplifying Iranian state-media content without adding independent reporting. The footage described as showing aftermath in Bandar Abbas, a major Iranian naval base on the Strait of Hormuz, was "circulating," not sourced to a named camera operator, outlet, or geolocation. None of the items have been matched, as of this writing, to a verifiable image database.
Why the geography is harder than it looks
Iran's southern arc is not a single battlespace. Sistan and Baluchestan is a restive, largely Sunni, underdeveloped province that borders Pakistan and Afghanistan; it is the site of past cross-border incidents involving Pakistan's air force and of recurring unrest involving the Jaish al-Adl separatist group. Ahvaz is the capital of Khuzestan, an Arab-majority oil-producing province that Iraq's armed forces bombed repeatedly during the 1980-88 war. Bandar Abbas houses a major IRGC naval presence and a commercial port handling much of Iran's containerised trade. Strikes attributed to the United States against any of these sites would carry sharply different strategic implications, and the sources do not say which, if any, is genuine.
The corollary matters too. If the United States had conducted strikes on Iranian soil on 12 July 2026, the operational logic would normally produce a US acknowledgement, an Iranian Foreign Ministry summons of a US interest section, and immediate flight-notice revisions across the Gulf. None of those downstream signals appear in the source record at the time of writing. That absence is not proof the strikes did not occur, but it is consistent with the alternative reading that the Iranian state is seeding a narrative before the kinetic facts are established.
What remains unverified
Three things are unresolved. First, the chain of attribution: Press TV cites an "Ahvaz provincial official" by role only, not by name, and offers no detail on whether the official spoke to Press TV directly or whether the claim travelled through intermediaries. Second, the relationship between the Sistan and Baluchestan blasts, the Ahvaz explosions, and the Bandar Abbas footage: the thread bundles them but does not demonstrate they are a single strike package or even that they occurred on the same operational timeline. Third, the nature of the alleged targets. Ahvaz Airport is mentioned once, by "wfwitness" and only as a "preliminary report"; Press TV does not confirm it. A strike on a civilian airport and a strike on a military installation are not interchangeable claims.
The structural context is worth naming without overstating it. Iranian state media has, in past cycles of US-Iran tension, run unverified strike-attribution claims that were later walked back or quietly dropped. The 2024 episode in which Iranian outlets reported Israeli strikes inside Isfahan is the closest analogue: initial reporting carried confident attribution, follow-up reporting narrowed the scope, and a definitive independent account took days to emerge. The reasonable posture on 12 July 2026 is that something kinetic may have occurred in at least one Iranian city, that Iranian state media has named the United States as the perpetrator, and that no independent confirmation exists yet. That gap will close one of two ways: either US or independent reporting corroborates the strikes and the question becomes which targets and why, or the Iranian state pulls back the attribution once the operational picture stabilises. The wire should not lead either way until then.
The next twelve hours
The market-relevant question is whether Gulf shipping and aviation will move on these claims before they are verified. Iran's strait geography gives even an unverified strike narrative real weight: insurance markets for Strait of Hormuz transits, regional airline routing, and Brent crude all price the possibility of US-Iran escalation more sharply than almost any other Middle East event. If Press TV's reporting holds up through overnight US acknowledgement, the Iran file reopens on a kinetic footing for the first time since the most recent round of exchanges. If it does not hold up, this thread becomes a useful case study in how quickly an unverified Iranian state-media attribution can travel across aggregators and reach an Anglophone audience within minutes. Either outcome is a story; the reporting discipline required is the same in both cases: name what is sourced, name what is not, and do not let the speed of Telegram break the chain of attribution.
Desk note: Monexus is publishing the Iranian state-media framing in full because it is the available record, while flagging explicitly that no US, Western-wire, or independent Iranian opposition source has corroborated the strikes as of 22:28 UTC on 12 July 2026. Where wire reporting treats attribution as settled, this publication treats it as a claim under test.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/presstv
- https://t.me/presstv
- https://t.me/presstv
- https://t.me/wfwitness
- https://t.me/wfwitness