3JUN

Drone hits ship in the safe corridor

2 min read

09:04UTC

An IRGC drone hit the Singapore-flagged container ship Ever Lovely on 25 June, 7.5 nautical miles off Oman, inside the very lane the IMO had opened for safe passage.

← Back to Washington signs a sanction, not a strike Jump to analysis ↓

ConflictDeveloping

Key takeaway

Iran struck a Taiwanese-operated ship while waving the Korea-China crude convoy through the same corridor.

An Islamic Revolutionary Guard Corps (IRGC) drone struck the Singapore-flagged container ship M/V Ever Lovely on its starboard side at 14:10 UTC on 25 June, 7.5 nautical miles south-east of Dahit, Oman. The ship was inside the safe-passage lane the International Maritime Organization (IMO), the UN's shipping regulator, had opened days earlier. The IRGC, Iran's elite military force, had formally rejected that corridor hours before the attack . ¹

Iran fired four one-way attack drones. US forces shot down three; the fourth hit the Evergreen Marine vessel and caused no casualties. The Ever Lovely sailed on.

Five South Korean ships had transited the strait untouched that day . Iran struck a Taiwanese-operated box ship and waved the Korea-China crude convoy through, asserting control of the strait without closing it to the cargo that pays the Iranian state's bills. The attack came at the corridor's highest-traffic moment since the crisis began, when the lane looked as though it was working.

Deep Analysis

In plain English

Iran's Islamic Revolutionary Guard Corps, the country's ideological military force, fired four attack drones at a container ship called the Ever Lovely in the Persian Gulf on 25 June. The ship was sailing inside a special corridor that the United Nations' maritime body had set up so vessels could leave the region safely. US forces shot down three of the four drones, but one hit the ship on its side. The 25-member crew aboard escaped injury and the Ever Lovely resumed its voyage. Earlier the same morning, Iran's Guards had announced they considered the safety corridor 'unacceptable'. Five South Korean cargo ships crossed the same corridor the same day without being attacked, suggesting the Guards were deliberately choosing which ships to target rather than closing the corridor to everyone.

Deep Analysis

Root Causes

The IMO corridor was negotiated between Oman, the IMO and the US without any IRGC sign-off. The Guards rejected it publicly on 25 June as 'unacceptable and dangerous'. A transit corridor whose authority the waterway's de facto gatekeeper does not recognise carries a structural legitimacy gap: the Ever Lovely was in a corridor that existed on paper but not in IRGC doctrine.

The IRGC's Decentralised Mosaic Defence doctrine, activated after the February 2026 strikes, devolved launch authority to 31 autonomous provincial units to prevent command decapitation. A doctrine designed to survive decapitation creates a structural problem for central control: selective-enforcement orders from Tehran cannot be reliably translated into selective-enforcement actions on the water.

Escalation

Striking inside an internationally sanctioned safe-passage corridor raises the escalatory threshold significantly above previous Hormuz attacks on vessels outside designated lanes. The fact the IRGC allowed South Korean vessels through the same day signals calibrated, not uncontrolled, escalation, but the act of breaching a humanitarian corridor sets a precedent with no obvious self-limiting logic.

What could happen next?

Meaning
The IRGC's decision to strike inside the IMO corridor rather than outside it transforms the corridor from a neutral safe-passage route into a target environment, making future IMO-brokered evacuation or transit arrangements structurally uninsurable.
Immediate · Assessed
Risk
Registry-selective enforcement, attacking Taiwanese-operated vessels while passing Korean ones, creates a precedent for economic coercion through maritime force: countries that have sanctioned Iran face a direct cost to their shipping, which may fragment international coalition solidarity.
Short term · Reported
Consequence
The attack at peak throughput, the same day Hormuz moved a record 20 million barrels, demonstrates the IRGC can enforce corridor control at any traffic volume, removing the assumption that high throughput deters attacks.
Short term · Assessed

Source Landscape

This story draws on mixed-leaning sources from Qatar

Qatar

Primary parallel: During the 1986-1988 Tanker War, both Iraq and Iran targeted vessels by cargo origin and customer nationality rather than flag state alone, creating a selective trade blockade while avoiding wholesale closure. The Ever Lovely strike fits that template precisely: the IRGC passed Korean-flagged crude carriers and struck a Taiwanese-operated container ship, asserting discriminatory transit control over a nominally international waterway.

Counter-parallel: In July 2019, the IRGC seized the British-flagged tanker Stena Impero inside the strait of Hormuz and held it for two months to extract diplomatic concessions. The 2026 attacks are kinetic and destructive rather than detentive, suggesting the IRGC has shifted from coercive leverage to punitive enforcement, a tactical change that removes the negotiating chip that seizures provided.

Consensus view: Carnegie Endowment's Sina Azodi and Behnam Ben Taleblu at the Foundation for Defense of Democracies both assess the IRGC's selective targeting as deliberate national-registry enforcement: the Guards struck an Evergreen Marine vessel while waving five South Korean tankers through the same corridor the same day, testing whether they can penalise Taiwan-linked operators without triggering a unified Western military response.

Counter-view: Analysts at China's People's Liberation Army National Defence University argue the attack was a sovereignty-assertion rather than an escalation, since the IRGC had explicitly declared the Oman-IMO corridor 'unacceptable' hours earlier , making the strike a defensive response to what Beijing characterises as an externally imposed transit regime that bypassed Iran's consent.

Key tension: Whether the IRGC's registry-selective attack pattern represents coordinated strategic enforcement from Tehran or autonomous action by one of the 31 provincial units operating under the Decentralised Mosaic Defence doctrine, because the answer determines whether diplomatic engagement can actually switch the attacks off.

First Reported In

Update #140 · US bombs Iran, and the oil market shrugs

Al Jazeera· 28 Jun 2026

Read original →

Causes and effects

Caused by

IRGC rejects the Oman Hormuz route

The IRGC's 25 June rejection of the Oman-IMO corridor escalated into a kinetic drone strike on M/V Ever Lovely inside that same corridor hours later.

Occurred 25 Jun 2026

Read story →

Korean ships sail past the IRGC order

The IRGC struck M/V Ever Lovely on the same day five Korean vessels transited Hormuz unmolested, asserting selective corridor control at the moment of peak throughput.

Occurred 25 Jun 2026

Read story →

Hormuz clears a record 20m barrels

The IRGC struck M/V Ever Lovely at the exact moment Hormuz recorded its crisis-period throughput record of 20 million barrels, asserting corridor control at peak recovery volume.

Occurred 25 Jun 2026

Read story →

This Event

Drone hits ship in the safe corridor

The strike turned the IRGC's rejection of the safe corridor into a kinetic fact, inside the lane meant to guarantee passage.

Led to

US bombs Qeshm, first strike since deal

CENTCOM struck Qeshm Island and Sirik radar on 26 June directly in response to the IRGC drone attack on M/V Ever Lovely inside the IMO corridor on 25 June.

Occurred 26 Jun 2026

Read story →

11,000 trapped as exit corridor shut

The IRGC drone strike on M/V Ever Lovely triggered the PGSA's suspension of the IMO evacuation corridor and set the operational pattern for the Kiku strike on 27 June.

Occurred 25 Jun 2026

Read story →

IRGC missiles hit a Qatari gas tanker

Continues the pattern begun by the 25 June IRGC drone strike on the Ever Lovely inside the IMO corridor.

Occurred 6 Jul 2026

Read story →

Different Perspectives

Jordan

Jordan has not addressed the IRGC's claim that Jordanian civilians and soldiers supplied targeting intelligence for the 20 July Aqaba strike, even as its deputy prime minister received a condemnation call over Iran's earlier missile fire. The base has now produced the war's first confirmed American deaths on Jordanian soil.

CENTCOM

CENTCOM confirmed a third American service member died in northern Iraq on 19 July clearing unexploded ordnance from a downed Iranian drone, and recovered unidentified remains at Muwaffaq Salti Air Base in Jordan. The Pentagon has framed its Khuzestan strikes as degrading IRGC capacity, a rationale that stretches to explain a reactor foundation with no nuclear material in it.

Kuwait

Kuwait's military said it was confronting Iranian attacks after the Shuaiba power and desalination complex burned for the second time in two days on 19 July, following an earlier ministry request that households ration water. Roughly 90 per cent of Kuwait's drinking water depends on the same generating units Iran keeps hitting.

IRGC

The IRGC claimed a 21st wave of Operation Nasr-2 struck Aqaba Airport and Azraq on 20 July, destroying hangars and aircraft, and thanked Jordanians for supplying intelligence. No US, Jordanian or Kuwaiti source has confirmed any part of the claim, which Press TV alone carried.

IAEA

The IAEA said it is looking into reports of a 19 July strike on the Darkhovin nuclear plant construction site, confirming inspectors found no nuclear material there on their last visit. Grossi again called for restraint near nuclear sites, a faster response than the four months of silence that followed the disputed Bushehr strike.

Shipping and war-risk insurers

War-risk premiums for Hormuz transits reached 3 to 10 per cent of hull value on 17 July, against 0.25 per cent before the war, as Brent cleared $87 and daily transits fell to eight vessels. Underwriters are pricing the confirmed UKMTO mine near the Traffic Separation Scheme, not the IRGC's unconfirmed 18 July mining claim, which CENTCOM called false.