ClosedLow impactAI Generated

MSC Sariska V Containership Struck by USV Attack Off Iraq

Occurred 28 Feb 2026·Detected 1 Jun 2026·
🇮🇶 Approximately 40 nautical miles southeast of Umm Qasr, Iraq, northern Arabian Gulf6 reportsCAT 26AAEnded 2 Jun 2026
MarinePolitical Violence & WarPolitical RiskMarine HullMarine CargoEnergyTerrorism & Political ViolencePolitical RiskReinsuranceWar Risk

The Panama-flagged MSC containership MSC Sariska V sustained significant hull damage from an apparent uncrewed surface vessel (USV) attack approximately 40 nautical miles southeast of Umm Qasr, Iraq, in the northern Arabian Gulf. The vessel, operated by MSC within a regional feeder network after deep-sea services were disrupted by the U.S.-Iran conflict, suffered two impacts causing fire damage above the waterline on its starboard side. This is the third reported attack in Iraqi territorial waters since the conflict began in late February, with direct implications for Marine Hull, War Risk, and cargo war risk books.

AI-generated from linked source reports. See our correction policy.

Impact verdict

Low impact. LOW: Downgraded by deterministic London Market impact gate. The source does not evidence a concrete London Market loss pathway such as named insured asset damage, port/waterway/airspace closure, vessel/cargo loss, sanctions asset action, claims/loss estimate, or market pricing impact.

View assessment methodology

How we grade what we know -- Known · Reported · Uncertain. Methodology →

Intelligence ledger

Each line expands in place to its underlying sourced claim.

Known8 lines

UKMTO confirmed receipt of incident report involving a cargo vessel approximately 40 nautical miles southeast of Umm Qasr, Iraq
structured lineknown
No separate sourced-claim record is available for this line yet.
Vessel struck on starboard side by unknown projectile causing large explosion
structured lineknown
No separate sourced-claim record is available for this line yet.
A second impact caused a fire, which has since been extinguished
structured lineknown
No separate sourced-claim record is available for this line yet.
No crew injuries reported
structured lineknown
No separate sourced-claim record is available for this line yet.
Vessel identified as MSC Sariska V, Panama-flagged containership
structured lineknown
No separate sourced-claim record is available for this line yet.
This is the third reported attack in Iraqi territorial waters since conflict began February 28
structured lineknown
No separate sourced-claim record is available for this line yet.
Prior attacks occurred on March 4 (tanker near Kuwait) and March 11 (two tankers near Al Basrah)
structured lineknown
No separate sourced-claim record is available for this line yet.
EOS Risk Group analyst attributed attack to Iranian-linked USV, citing MSC's Israeli affiliation as motivation
structured lineknown
No separate sourced-claim record is available for this line yet.

Reported5 lines

Social media video appears to show significant damage to the starboard side amidships
structured linereported
No separate sourced-claim record is available for this line yet.
Vessel had completed unloading at Umm Qasr port before the attack
structured linereported
No separate sourced-claim record is available for this line yet.
Damage pattern inconsistent with mine strike; likely USV attack based on analyst assessment
structured linereported
No separate sourced-claim record is available for this line yet.
MSC Sariska V has been trapped in the Persian Gulf since February 28 and operating regional feeder routes
structured linereported
No separate sourced-claim record is available for this line yet.
Many containers aboard were reportedly empty based on draft analysis
structured linereported
No separate sourced-claim record is available for this line yet.

Uncertain6 lines

Extent of structural hull damage and whether vessel is seaworthy
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether cargo loss or damage has occurred
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Total insured loss value of vessel and cargo
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether war risk additional premium notices will be issued or JWC listed area clauses triggered for the northern Gulf
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether MSC will make a hull or war risk claim
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Attacker identity not officially confirmed
structured lineuncertain
No separate sourced-claim record is available for this line yet.

Geographic Zone Matches

8 active matches

  • OFAC Sanctioned Countries
    Rule-basedConfidence 100%
  • Iraq (12nm coastal buffer)
    Rule-basedConfidence 100%
  • United Arab Emirates (12nm coastal buffer)
    Rule-basedConfidence 100%
  • JWC Listed Areas
    Rule-basedConfidence 100%
  • EU Sanctions List
    Rule-basedConfidence 100%
  • Iran (12nm coastal buffer)
    Rule-basedConfidence 100%
  • Saudi Arabia (12nm coastal buffer)
    Rule-basedConfidence 100%
  • Persian/Arabian Gulf, Gulf of Oman, Indian Ocean, Gulf of Aden and Southern Red Sea
    Rule-basedConfidence 100%

Geographic zone matches are RiskEvents spatial/analytical indicators, not coverage determinations or Lloyd's official classifications.

Affected countries

🇦🇪 United Arab Emirates🇮🇳 India🇮🇶 Iraq🇮🇷 Iran🇰🇼 Kuwait🇴🇲 Oman🇶🇦 Qatar🇸🇦 Saudi Arabia

+1 more

Timeline

Corroboration10 Jun 2026, 04:04

Day 100 of Strait of Hormuz disruption with traffic at roughly 5% of normal levels. MSC Sariska V was struck by two projectiles near Umm Qasr, Iraq on June 1, shifting the risk profile from Hormuz to the broader Gulf corridor. Drewry WCI freight rates are up 23% to $3,433/FEU with Asia-US rates up 109% since February 28, prompting peak season surcharges from major carriers and significant war-risk insurance implications.

Source: r/exportersindia (Social / Community) · View source

Closure4 Jun 2026, 22:30

Event Closed

auto_closed_monitoring_timeout

Status Change4 Jun 2026, 22:30

Lifecycle changed

monitoring → closed

Status Change2 Jun 2026, 21:30

Status changed to monitoring

Auto-transitioned: no updates for 6 hours

active → monitoring

Corroboration2 Jun 2026, 14:54

MSC's containership MSC Sariska V was struck by two projectiles while departing Iraq's Port of Umm Qasr, confirming a serious armed attack on a named commercial vessel in a JWC-listed area. The incident represents a concrete war-risk and marine hull loss pathway, with potential hull damage claims, war-risk premium implications, and possible cargo loss or damage. This is one of the most significant vessel attack incidents in the Persian Gulf/Iraq region in recent memory.

Source: gCaptain (Trade Media) · View source

Corroboration2 Jun 2026, 11:54

MSC's container vessel Sariska 5 was struck by two projectiles while berthed at Umm Qasr port in Iraq on 2 June 2026, with Iran's Islamic Revolutionary Guard Corps (IRGC) claiming responsibility. MSC confirmed all crew are safe but condemned the attack as an unjustified strike on a neutral commercial vessel with no US or Israeli connections. This constitutes a named vessel casualty with confirmed physical damage at a commercial port, creating direct Marine Hull, War Risk, and P&I exposure.

Source: Asharq Al-Awsat (Arabic) (Mainstream Media) · View source

Status Change2 Jun 2026, 09:18

Status changed to active

evidence_trigger: developing_promotion

developing → active

Corroboration2 Jun 2026, 09:18

Iran's Islamic Revolutionary Guard Corps targeted the container vessel MSC Sariska with a cruise missile in the Sea of Oman, reportedly in retaliation for a prior US strike on the Iranian vessel 'Lian Star'. The vessel was en route from Iraq to Qatar at the time of the attack. This constitutes a named vessel casualty in a JWC-listed area with direct implications for Marine Hull, War Risk, and cargo underwriters.

Source: Al Jazeera Arabic (Mainstream Media) · View source

Status Change1 Jun 2026, 20:14

Status changed to developing

evidence_trigger: corroboration >= 2

signal → developing

Corroboration1 Jun 2026, 20:14

Two explosions occurred aboard a cargo vessel in Gulf waters near the Iraqi port of Umm Qasr, amid heightened security tensions in regional waterways. The incident represents a credible marine hull and war risk loss pathway, given the vessel is named as a cargo ship in a JWC-listed area. Details on vessel identity, damage extent, and cause remain unconfirmed.

Source: Al Jazeera Arabic (Mainstream Media) · View source

Initial Detection1 Jun 2026, 18:54

Initial Detection

The Panama-flagged MSC containership MSC Sariska V sustained significant hull damage from an apparent uncrewed surface vessel (USV) attack approximately 40 nautical miles southeast of Umm Qasr, Iraq, in the northern Arabian Gulf. The vessel, operated by MSC within a regional feeder network after deep-sea services were disrupted by the U.S.-Iran conflict, suffered two impacts causing fire damage above the waterline on its starboard side. This is the third reported attack in Iraqi territorial waters since the conflict began in late February, with direct implications for Marine Hull, War Risk, and cargo war risk books.

MSC SARISKY V was struck with what is likely a USV in Iraqi territorial waters after it had completed unloading its cargo at the port of Umm Qasr in southern Iraq. MSC remains a target for Iran owing to Israeli affiliation.

Source: gCaptain (Trade Media) · View source

Lloyd's classifications

Tracking this kind of risk? Get an email when Marine events escalate.

Get alerts