U.S. opens a new round on Iran, citing Hormuz and a Jordan attack

At 6 p.m. Eastern Time on 18 July 2026, U.S. Central Command announced that American forces had begun a new wave of airstrikes against Iran, ordered by the Commander in Chief and framed as retaliation both for an Islamic Revolutionary Guard Corps attack on U.S. service members in Jordan the previous night and for Tehran's continuing threat to commercial shipping in the Strait of Hormuz. CENTCOM's own statement, distributed at the top of the hour, says the strikes are "designed to further degrade Iran's ability to threaten commercial shipping in the Strait of Hormuz and swiftly punish Islamic Revolutionary Guard Corps forces who launched attacks against American service members in Jordan last night."

The headline is sequencing: a Jordan attack on U.S. troops, an announcement that two American service members have been killed in action, and then a fresh round against the regime the U.S. holds responsible. That order matters. It tells readers what the administration's lawyers will rely on to call this a defensive operation rather than an offensive escalation, and it tells Tehran what kind of pretext the next round will need. The first new strikes began while the Jordan casualties were still being formally tallied, a tempo that compresses the gap between incident and response.

What CENTCOM says, in its own words

The official text, published by U.S. Central Command on 18 July 2026 at 22:32 UTC and then recirculated by Open Source Intel, Disclose.tv and OSINTdefender, is short and deliberate. It opens by anchoring the strikes to the Commander in Chief's direction, then names two targets: Iranian capacity to threaten shipping in Hormuz, and IRGC units responsible for the Jordan attack. CENTCOM added that the operation is intended to "swiftly punish" the IRGC units identified as responsible.

A second piece of framing came from the Telegram channel BellumActa News, which reported that CENTCOM had announced the completion of a seventh wave of strikes inside Iran on the night before this announcement, with accompanying footage. If that account holds, the "new wave" announced at 6 p.m. ET is the eighth in roughly a day, with the seventh wrapped up overnight and this round opened before sunup in the Gulf.

That cadence is a story in itself. Earlier waves of the broader campaign have been paced out across days; clustering two waves within a 24-hour window, with one explicitly tied to American battlefield casualties, suggests the political appetite inside the administration is for visible, named retaliation rather than steady-state attrition.

The two pretexts the U.S. is relying on

The first pretext is shipping. Roughly a fifth of the world's seaborne oil moves through the Strait of Hormuz, and any sustained threat to tankers in that corridor feeds straight into global insurance premiums, freight rates, and ultimately the petrol pump. By naming "commercial shipping" first in the CENTCOM statement, Washington gives the operation a maritime-law character that travels well in allied capitals and at the United Nations.

The second pretext is the Jordan attack on U.S. service members. The two KIAs announced earlier this week are the political hinge: they convert what might otherwise read as an open-ended air campaign into a bounded retaliation under the logic of self-defence and the right of forces to defend themselves after a hostile act. That framing is harder for critics inside the United States to dispute on first principles, even if the underlying policy of striking Iran is contested.

The structural pattern here is familiar. A regional partner suffers an incident attributed to an Iranian-aligned force; the U.S. responds with strikes that are formally directed at the IRGC, formally limited in stated objective, and informally scaled by whatever target list the Pentagon has been quietly building. The announcement structure stays tight, the target list does the talking.

What Iran says, and why that matters

The thread material does not include a direct Iranian response to the 6 p.m. ET announcement. That absence is itself a data point: in past escalations Tehran has typically surfaced a framing of its own within minutes via state outlets such as IRNA, Tasnim, or Press TV, often leaning on language about legitimate defence of Iranian territory. None of those readouts appear in the source feed.

That silence can mean three things. It can mean the Iranian foreign-policy apparatus is still coordinating its line. It can mean Tehran is choosing, for now, to let the IRGC speak through action rather than communiqué. Or it can mean the source feed reflects a narrow, English-language slice of the conversation and the Persian-language response is being missed. Monexus treats all three as live hypotheses until an Iranian state statement lands.

The substantive question is whether Tehran treats these strikes as a continuation of the existing pattern, which it has so far absorbed in measured steps, or as a step-change that requires a different kind of answer. The reference in the CENTCOM statement to "swiftly punish" is calibrated language, designed to telegraph resolve without specifying a ceiling.

Why a new wave matters structurally

This round is being marketed as retaliation, not as a campaign enlargement, and that distinction will be tested inside the next 72 hours. Three signals will tell readers whether the framing holds.

First, target selection. Strikes on IRGC naval and missile infrastructure in the Hormuz littoral reinforce the shipping pretext. Strikes on Iranian air defences, command nodes, or facilities deep in the interior start to look like a different operation wearing the same press release. Second, allied posture. The extent to which Gulf states, Jordan, and European partners publicly endorse or quietly acquiesce will set the political ceiling for what comes next. Third, the response chain in the Levant. Iranian-aligned groups in Iraq, Syria, Lebanon, and Yemen have, in earlier phases, widened the battlefield when the homeland was hit. Any uptick there is the leading indicator that Tehran has decided this round crossed a line.

The wager inside the new wave is that the Jordan attack gives Washington enough political cover to keep striking without paying a domestic price at home, and enough of a maritime-law wrapper to keep allied capitals on board. The wager inside Tehran is that absorbing the blows, and signalling that absorption, costs the U.S. the narrative faster than the strikes degrade Iranian capacity.

What remains uncertain

Three points are genuinely unresolved in the reporting available so far. The exact target list for the 6 p.m. ET wave is not in the CENTCOM statement; only the framing objectives are. The operational geography of the Jordan attack that triggered the retaliation is not described in the source material beyond "last night," so the chain of attribution from incident to IRGC unit is asserted, not detailed. And the casualty picture on the Iranian side, from earlier waves as well as this one, is not in the thread. Read into that what you will: in an air campaign, silence on enemy casualties usually reflects operational security rather than restraint.

Readers should also note that the "seventh wave completed last night" framing in BellumActa News has not been independently corroborated by another outlet in this thread, and that the KIA figure of two is sourced to OSINTdefender's summary of CENTCOM rather than to a CENTCOM casualty release. Those are not contradictions; they are places where the lede outruns the documentation, and where later reporting will either tighten or loosen the picture.

This publication is treating the 6 p.m. ET CENTCOM statement as the wire of record for the start of the new wave, and is attributing casualty and target-set claims to CENTCOM's own language rather than to third-party paraphrases until independent confirmation lands.

Wire provenance

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

• https://t.me/s/UCC
• https://t.me/s/OpenSourceIntel
• https://t.me/s/osintdefender
• https://t.me/s/Disclosetv
• https://t.me/s/BellumActaNews
• https://t.me/s/rnintel
• https://t.me/s/disclosetv
• https://t.me/s/osintlive