MonitoringHigh impactAI Refreshed
IMO condemns tanker attack near Strait of Hormuz; U.S. confirms strike
Occurred 10 Jun 2026·Detected 16 Jun 2026·
🇮🇷 Strait of Hormuz, between Iran and the Musandam Peninsula (Oman/UAE)55 reportsCAT RSHR
War & Armed ConflictMarinePolitical Violence & WarTrade DisruptionEnergy & InfrastructurePolitical RiskMarine HullMarine CargoEnergyTerrorism & Political ViolencePolitical RiskCasualty & LiabilityLife & HealthWar Risk
The International Maritime Organization has condemned an armed attack on a tanker carrying an Indian crew near the Strait of Hormuz, with U.S. confirmation of a military strike using precision munitions into the ship's engine room. Three Indian seafarers are reported killed and three further seafarers reported missing, while 21 Indian sailors were rescued. Fire is confirmed on board. The event lies within a Joint War Committee-listed war risk area at a critical energy chokepoint. Vessel identity, flag, cargo, full damage extent, and attribution remain unconfirmed.
AI-generated from linked source reports. See our correction policy.
Impact verdict
High impact. Named-vessel crew fatality incident in a JWC-listed war risk area with confirmed IMO condemnation, U.S. confirmation of a precision-munition strike on the engine room, fire on board, and reported missing seafarers. Source-grounded detail has materially upgraded severity: three crew confirmed killed (was previously 'missing'), 21 Indian crew rescued, and India-flag/crew link confirmed via Indian MEA engagement. Loss pathways span marine hull, marine cargo, war risk (additional premium triggers, JWC-listed area), and P&I / crew personal accident; secondary implications include Persian/Arabian Gulf reinsurance pricing pressure, energy-transit rerouting risk, and crew-of-Indian-nationality reputational considerations. Severity is currently capped at the upper-medium band until vessel identity, cargo type/value, and full damage extent are confirmed.
View assessment methodologyHow we grade what we know -- Known · Reported · Uncertain. Methodology →
Intelligence ledger
Each line expands in place to its underlying sourced claim.
Known26 lines
IMO condemned the tanker attack near the Strait of Hormuz▾
structured lineknown
No separate sourced-claim record is available for this line yet.
U.S. confirmed a military strike in the area▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Incident classified as a maritime incident in the Persian/Arabian Gulf region▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Three Indian crew members were killed in the attack, according to sourcing citing 3 seafarers who lost their lives.▾
crew_fatalities_three_indianloss confirmationvalid from 11 Jun 2026, 00:00Marine P&I
Market relevance: Confirmed crew fatalities elevate P&I crew personal accident and war-risk crew cover exposure; Indian-crew nationality is now documented.
“My thoughts are with the families of the three seafarers who lost their lives” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
IMO Secretary-General Arsenio Dominguez publicly condemned the attack on a tanker, stating any act endangering seafarers and international shipping is unacceptable and that the targeting of commercial shipping and civilian infrastructure must end.▾
imo_condemnation_of_tanker_attackpolitical signalvalid from 11 Jun 2026, 00:00Marine War
Market relevance: United Nations/IMO condemnation raises diplomatic pressure and signals expectation of international-law-compliant response; relevant to war-risk political-violence coverage assessments.
“UN maritime head condemns attack on tanker with India crew” — prokerala.com · 11 Jun 2026, 17:00 · mainstream media
“I strongly condemn any act from any party that endangers the lives of seafarers and the safety of international shipping” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
Incident is located near the Strait of Hormuz, with reporting also referencing waters near Sohar (Oman), Khorfakkan (UAE), and Iran/Yemen waters. All referenced locations lie within the broader Persian/Arabian Gulf JWC-listed war risk area.▾
incident_geography_strait_of_hormuzwar risk area activationvalid from 11 Jun 2026, 00:00Marine War
Market relevance: JWC-listed war risk area and critical energy chokepoint — directly elevates marine war additional premium triggers and transit rerouting considerations.
“Three Killed In Hormuz Strike, UN Warns Of Fallout” — miragenews.com · 11 Jun 2026, 18:15 · mainstream media
The Strait of Hormuz is a critical maritime chokepoint for global energy shipments.▾
energy_chokepointsystemic exposure contextvalid from 17 Jun 2026, 10:31Marine Cargo
Market relevance: Implicates secondary exposures for energy cargo, marine cargo war risk, and downstream reinsurance pricing on Gulf transit.
“one of the world's most critical maritime chokepoints” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
“critical chokepoint for global energy shipments” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The incident location is in a Joint War Committee-listed war risk area.▾
jwc_listed_war_risk_areapolicy trigger contextvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Establishes baseline war risk additional premium regime and notice-trigger conditions for hull and cargo policies transiting the area.
“already designated as a JWC listed war risk area” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
The attack occurred near the Strait of Hormuz, a critical maritime chokepoint within a JWC-listed war risk area.▾
vessel_attack_in_war_risk_zonewar risk zone attestationvalid from 17 Jun 2026, 03:19Marine War Risk
Market relevance: Confirms the loss pathway falls inside a designated war risk zone, supporting notice-of-cancellation and additional premium provisions in marine war policies.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
The United States confirmed a military strike in the area near the Strait of Hormuz.▾
us_confirms_military_strike_areawar risk premium triggervalid from 17 Jun 2026, 03:19Marine War Risk
Market relevance: U.S. kinetic action in a JWC-listed war risk zone materially elevates additional premium triggers and policy notification obligations for war risk underwriters.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The International Maritime Organization condemned an attack on a vessel near the Strait of Hormuz.▾
imo_condemns_tanker_attackregulatory and diplomatic signalvalid from 17 Jun 2026, 03:19Marine War Risk
Market relevance: Establishes official international body response, raising reputational and policy pressure on war risk underwriters operating in the Persian/Arabian Gulf.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
Supersession history: 1 prior/revised claim rows.
The incident occurred in waters near the Strait of Hormuz, between Iran and the Musandam Peninsula (Oman/UAE).▾
incident_location_strait_of_hormuzgeographic scopevalid from 17 Jun 2026, 03:19Marine War
Market relevance: Anchors treaty/slip geographic scope and applicable sanctions/regulatory overlays.
“attack on a vessel near the Strait of Hormuz” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
“attack on a vessel near the Strait of Hormuz” — hongkongherald.com · 11 Jun 2026, 04:30 · mainstream media
The incident occurred in the Strait of Hormuz area, designated as a JWC-listed war risk area.▾
incident_in_jwc_war_risk_areawar risk listed areavalid from 17 Jun 2026, 03:19Marine War
Market relevance: Direct trigger for marine war risk additional premium and notice provisions; affects underwriting and reinsurance pricing on Persian/Arabian Gulf transit.
The Strait of Hormuz is a JWC-listed war risk area, directly relevant to marine war risk underwriting and additional premium triggers in the Persian/Arabian Gulf.▾
strait_of_hormuz_war_risk_areawar risk premiumvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
The incident is located near the Strait of Hormuz, with source reporting associating the location with Omani waters, between Iran and the Musandam Peninsula.▾
location_oman_strait_of_hormuzcontextvalid from 16 Jun 2026, 16:10Marine
Market relevance: medium
The Strait of Hormuz is a critical oil shipping chokepoint that handles a substantial share of global oil shipments.▾
chokepoint_strategic_contextchokepoint risk scenariovalid from 11 Jun 2026, 00:00Marine War Risks
Market relevance: Disruption to this chokepoint is a high-materiality scenario for marine, war risk, energy, and offshore classes.
The incident occurred in waters near the Strait of Hormuz, in the Gulf of Oman / Persian Gulf area off Oman.▾
location_strait_of_hormuz_areageographic exposurevalid from 11 Jun 2026, 00:00Marine War Risks
Market relevance: Location within the Strait of Hormuz transit zone is the primary driver of systemic marine and energy market relevance.
A vessel was attacked in waters near the Strait of Hormuz, prompting IMO condemnation and the reported U.S. confirmation of a military strike in the area.▾
vessel_attacked_near_strait_of_hormuzloss exposurevalid from 16 Jun 2026, 16:10Marine
Market relevance: high
“IMO condemns ship attack near Strait of Hormuz” — utahindependent.com · 11 Jun 2026, 01:30 · mainstream media
The International Maritime Organization publicly condemned the attack on a vessel near the Strait of Hormuz.▾
imo_condemns_strait_of_hormuz_attackgeopolitical signalvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — utahindependent.com · 11 Jun 2026, 01:30 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — africaleader.com · 11 Jun 2026, 01:15 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — sandiegosun.com · 11 Jun 2026, 01:15 · mainstream media
Event remains in monitoring status pending confirmation of vessel identity, flag, cargo, damage extent, and attack attribution.▾
lifecycle_status_monitoringlifecycle statusvalid from 18 Jun 2026, 15:13Marine War
Market relevance: Monitoring status supports continuing situational awareness without claim-graph escalation to active-loss handling.
“lifecycle_status: monitoring” — RiskEvents structured intelligence · 18 Jun 2026, 16:57
The International Maritime Organization publicly condemned the armed attack on a vessel near the Strait of Hormuz.▾
imo_condemns_attackcoverage characterisationvalid from 17 Jun 2026, 04:31War Risk (Marine)
Market relevance: Establishes authoritative characterisation of the event as an unlawful armed attack, relevant to war risk coverage and notice wording.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The U.S. has confirmed a military strike in the area near the Strait of Hormuz.▾
us_confirms_military_strikeattribution signalvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Distinct from the IMO-condemned ship attack; relevant to attribution analysis, war risk triggers, and potential political-violence implications.
“The incident occurs in one of the world's most critical maritime chokepoints” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
Supersession history: 1 prior/revised claim rows.
The event is in monitoring status following auto-transition after six hours without updates.▾
lifecycle_monitoringworkflow signalvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Signals reduced update cadence; no new corroborating intelligence has arrived since the transition.
Event lifecycle transitioned from active to monitoring after approximately six hours without fresh sourced updates.▾
lifecycle_monitoring_no_update_6hoperational status signalvalid from 17 Jun 2026, 10:31Marine War Risk
Market relevance: Lifecycle status governs alerting and downstream book-watch sensitivity for the Persian/Arabian Gulf corridor.
Source · 17 Jun 2026, 14:43
The International Maritime Organization has publicly condemned an attack on a vessel near the Strait of Hormuz.▾
imo_condemns_vessel_attackwar risk underwriter attentionvalid from 17 Jun 2026, 03:19Marine War
Market relevance: Validates escalation in a JWC-listed war risk chokepoint; supports additional premium triggers and notice-of-cancellation posture.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — hongkongherald.com · 11 Jun 2026, 04:30 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — arabherald.com · 11 Jun 2026, 04:15 · mainstream media
The event is currently held at 'signal' lifecycle status, indicating initial detection pending confirmation of key details.▾
event_lifecycle_signalinternal workflowvalid from 16 Jun 2026, 05:34Marine War Risks
Market relevance: Lifecycle status governs how the event is propagated and gated in downstream insurance workflows.
Reported30 lines
Tanker was attacked in waters near the Strait of Hormuz▾
structured linereported
No separate sourced-claim record is available for this line yet.
Fire reported on the vessel (per GDELT themes)▾
structured linereported
No separate sourced-claim record is available for this line yet.
21 Indian sailors were rescued from the attacked vessel, per ianslive reporting.▾
crew_rescued_21_indiancasualty resolutionvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Rescue outcome is consistent with non-total-loss vessel scenario; relevant to salvage and general average considerations.
Three seafarers are reported missing following the fire on board; ianslive text references both three killed and three missing across the vessel.▾
crew_missing_threecasualty uncertaintyvalid from 11 Jun 2026, 00:00Marine P&I
Market relevance: Outstanding missing-person status affects P&I liability and family/next-of-kin exposure under crew personal accident covers.
Three seafarers are reported missing following the attack on the vessel near the Strait of Hormuz.▾
three_seafarers_missingcasualty exposurevalid from 17 Jun 2026, 04:31Marine Hull
Market relevance: Triggers protection & indemnity (P&I) and crew cover considerations; informs potential war risk liability quantum.
Supersession history: 1 prior/revised claim rows.
Article-level reporting indicates 24 Indian crew members were onboard the vessel, of whom 21 were reportedly rescued, leaving the three missing seafarers referenced in the headline.▾
indian_crew_24_onboard_21_rescuedcrew loss exposurevalid from 17 Jun 2026, 03:19Marine War
Market relevance: Refines crew P&I exposure and search-and-rescue status; supports humanitarian and life-policy claims.
“21 of the 24 Indian crew members onboard” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
Three seafarers were reported missing in the aftermath of the vessel attack near the Strait of Hormuz.▾
three_seafarers_reported_missingclaims exposurevalid from 16 Jun 2026, 16:10Marine
Market relevance: medium
Source-derived signals reference 3 seafarers reported missing in connection with the incident; this is not confirmed in the headline text.▾
seafarers_missing_signalp and i exposurevalid from 11 Jun 2026, 00:00Marine (P&I adjacent)
Market relevance: Missing crew figures feed protection & indemnity and crew liability exposure assessments.
The tanker is linked to India with an Indian crew; Indian Ministry of External Affairs and US Embassy have engaged on the incident.▾
vessel_crew_indian_nationalityclaim jurisdiction overlayvalid from 11 Jun 2026, 00:00Marine P&I
Market relevance: Indian-crew vessel attracts P&I club, Indian-Government, and diplomatic-engagement overlays on loss handling.
“UN maritime head condemns attack on tanker with India crew” — prokerala.com · 11 Jun 2026, 17:00 · mainstream media
“UN maritime head condemns attack on tanker with India crew” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
The UN (via the Secretary-General's office and Security Council statements) has warned of broader regional consequences flowing from the Hormuz strike.▾
un_warns_of_broader_falloutescalation signalvalid from 11 Jun 2026, 00:00Marine War
Market relevance: UN-level warning of regional escalation supports war-risk pricing pressure and political-violence scenario testing across Persian/Arabian Gulf books.
Indian Ministry of External Affairs and US Embassy engagement on the incident is referenced, with Indian Additional Secretary Nagaraj Naidu and US Embassy Chargé d'Affaires Jason Meeks cited in source material.▾
diplomatic_engagement_india_us_embassydiplomatic escalation signalvalid from 11 Jun 2026, 00:00Marine War
Market relevance: High-level diplomatic engagement raises profile of incident; relevant to political-risk and political-violence scenario testing for regional underwriters.
United Kingdom Maritime Trade Operations is referenced in source material in connection with the incident.▾
ukmto_involvement_referencedlondon market situational awarenessvalid from 11 Jun 2026, 00:00Marine War
Market relevance: UKMTO involvement is consistent with London Market war-risk situational awareness and underpins JWC-area advisory status.
The United States confirmed a military strike in the area near the Strait of Hormuz in the context of the vessel attack.▾
us_military_strike_near_strait_of_hormuzgeopolitical signalvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
“U.S. confirmed a military strike in the area” — utahindependent.com · 11 Jun 2026, 01:30 · mainstream media
Source reporting indicates the vessel carried 24 Indian crew members, of whom 21 were reported rescued and 3 remained missing.▾
24_indian_crew_onboardcontextvalid from 16 Jun 2026, 16:10Marine
Market relevance: low
IMO Secretary-General Arsenio Dominguez is named in the source as the principal IMO figure engaging on the incident.▾
imo_secretary_general_engagedinstitutional signalvalid from 11 Jun 2026, 00:00Marine War Risks
Market relevance: Named IMO leadership engagement signals official institutional concern, supporting market perception of severity.
Fire has been reported on board the attacked vessel following the strike on the engine room.▾
fire_on_board_confirmedloss severity upliftvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Fire on board materially raises hull total-loss and constructive-total-loss probability; relevant to marine hull and marine cargo underwriters.
“resulted in a fire on board and three seafarers reported missing” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
Fire has been reported on the attacked vessel in the waters near the Strait of Hormuz.▾
fire_on_vesseldamage indicatorvalid from 17 Jun 2026, 10:31Marine Hull
Market relevance: Direct indicator of marine hull damage and potential constructive total loss; drives salvage and general average considerations.
Fire was reported on the attacked vessel per GDELT-derived themes (DISASTER_FIRE).▾
fire_reported_on_vesselhull damage pathwayvalid from 17 Jun 2026, 03:19Marine Hull
Market relevance: A confirmed fire would shift exposure from navigation/peril-of-the-sea toward hull machinery and constructive total loss pathways under marine war and hull policies.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
A fire has been reported on the attacked vessel near the Strait of Hormuz.▾
fire_on_vessel_reportedhull damage indicatorvalid from 17 Jun 2026, 03:19Marine Hull
Market relevance: Suggests material physical damage; relevant to marine hull and general average considerations.
Fire was reported on the attacked vessel, per GDELT-derived themes in the source material.▾
fire_on_attacked_vesselloss exposurevalid from 16 Jun 2026, 16:10Marine
Market relevance: medium
A fire was reported on the attacked tanker, per GDELT-extracted themes (DISASTER_FIRE).▾
vessel_fire_reportedmarine hull loss potentialvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Fire on board a tanker is a direct driver of marine hull and pollution liability exposure.
U.S. sources cited precision munitions fired into the ship's engine room, resulting in fire on board and three seafarers reported missing; the U.S. has separately confirmed a military strike in the area.▾
us_precision_strike_on_vessel_engineloss aggregation riskvalid from 11 Jun 2026, 00:00Marine War
Market relevance: Confirmed military strike on a commercial vessel in a JWC-listed war risk area elevates expected war-risk loss frequency and political-violence aggregation concerns.
“Three Killed In Hormuz Strike, UN Warns Of Fallout” — miragenews.com · 11 Jun 2026, 18:15 · mainstream media
“fired precision munitions into the ship engine” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
Incident in the Strait of Hormuz — a critical chokepoint for global oil and LNG trade — raises the prospect of carrier rerouting and additional premium re-pricing for transit calls.▾
energy_chokepoint_rerouting_risktransit rerouting riskvalid from 11 Jun 2026, 00:00Marine Cargo
Market relevance: Chokepoint disruption risk supports energy transit war-risk re-pricing and may feed back into marine cargo and specie cover considerations.
“critical chokepoint — through which a significant portion of global oil and LNG trade transits” — miragenews.com · 11 Jun 2026, 18:15 · mainstream media
A named-vessel crew fatality in a JWC-listed war risk area is expected to feed through to additional premium triggers and broader Persian/Arabian Gulf reinsurance pricing pressure.▾
regional_reinsurance_pricing_pressurereinsurance pricing pressurevalid from 11 Jun 2026, 00:00Marine War
Market relevance: Direct reinsurance pricing impact on Persian/Arabian Gulf marine war and energy books; potential treaty loss-occurring aggregation concerns.
“raises immediate concerns for marine hull, marine cargo, war risk, and energy underwriters” — miragenews.com · 11 Jun 2026, 18:15 · mainstream media
The incident adds incremental pricing pressure on Persian/Arabian Gulf reinsurance treaties with marine war risk exposure.▾
persian_gulf_reinsurance_pricing_pressurereinsurance pricingvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Reinsurance treaty pricing and IULR considerations for Gulf marine war risk; secondary market signal only.
“war risk insurance pricing in the Persian Gulf” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
The attack in a JWC-listed war risk area is consistent with triggers for additional premium reviews and notice activation on marine war risk policies transiting the Strait of Hormuz.▾
war_risk_additional_premium_triggerpremium repricingvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Direct relevance to London Market war risk underwriters; supports additional premium repricing and notice wording review.
“raising concerns for commercial shipping, crew safety, and war risk insurance pricing in the Persian Gulf” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
“implications for war risk hull, marine cargo, and energy insurance pricing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The incident, located in a JWC-listed war risk area and coinciding with a U.S.-confirmed military strike, heightens the prospect of additional premium notifications, breach of warranty navigation limits, and pricing resets for Persian/Arabian Gulf war risk books.▾
war_risk_additional_premium_exposurewar risk pricing and capacityvalid from 17 Jun 2026, 10:31Marine War Risk
Market relevance: Direct exposure pathway for marine war, hull, and cargo underwriters; aggregate loss quantum cannot be estimated until vessel identity, cargo, and damage extent are confirmed.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — caribbeanherald.com · 11 Jun 2026, 05:00 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
The incident occurs in a chokepoint carrying a material share of global oil shipments, raising the potential for transit disruption, rerouting, and energy cargo insurance exposure.▾
energy_transit_disruption_risktransit disruptionvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
“critical chokepoint for global energy shipments” — sandiegosun.com · 11 Jun 2026, 01:15 · mainstream media
The attack in a JWC-listed war risk area creates direct exposure considerations for marine hull, marine cargo, and war risk underwriters, with potential upward pressure on additional war risk premiums for Persian/Arabian Gulf transits.▾
marine_hull_war_risk_exposurewar risk premiumvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
“direct implications for marine hull, marine cargo, and war risk underwriting” — utahindependent.com · 11 Jun 2026, 01:30 · mainstream media
Combined IMO condemnation, U.S. military strike, and a reported fire on a tanker in the Strait of Hormuz area are consistent with upward pressure on war risk premiums and additional premiums for Persian Gulf / Strait of Hormuz transits.▾
war_risk_premium_pressurewar risk premium repricingvalid from 11 Jun 2026, 00:00Marine War Risks
Market relevance: Directly relevant to war risk underwriters and to cargo / hull buyers of additional premiums.
“significant implications for marine hull, marine cargo, war risk, and energy transit insurance” — english.news.cn · 10 Jun 2026, 23:00 · mainstream media
Uncertain25 lines
Identity and flag of the attacked vessel▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Extent of physical damage and potential total loss▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether the vessel's cargo (type and value) is confirmed▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Attribution of the attack (Iranian-backed groups, other actors)▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Casualties among crew▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Impact on Strait of Hormuz transit and shipping rerouting▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Vessel name, flag state, ownership, and cargo type/value are not confirmed in available reporting; cargo is presumed to be oil-linked but unverified.▾
vessel_identity_flag_cargo_uncertainloss quantum uncertaintyvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Without vessel and cargo confirmation, insured severity banding cannot be tightened; marine hull/cargo loss quantum remains open.
“Details on location, extent of damage, and the attacking party remain unclear” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
Attribution of the attack is not independently confirmed; reporting references U.S. military action and broader regional actors but does not establish a single responsible party from open sources.▾
attack_attribution_uncertaincoverage trigger uncertaintyvalid from 11 Jun 2026, 00:00Marine War
Market relevance: Attribution drives whether the loss is treated as state-actor strike, terrorism, or political violence under marine war and P&I covers — material to coverage trigger and recoveries.
“Three Killed In Hormuz Strike, UN Warns Of Fallout” — miragenews.com · 11 Jun 2026, 18:15 · mainstream media
Supersession history: 1 prior/revised claim rows.
The impact on Strait of Hormuz transit and potential shipping rerouting has not been confirmed in the available sources.▾
transit_rerouting_impact_uncertaintransit disruption potentialvalid from 17 Jun 2026, 03:19Marine War
Market relevance: Drives marine war risk additional premium updates and potential energy/commodity cargo rate adjustments.
“Impact on Strait of Hormuz transit and shipping rerouting” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The type and value of cargo on board the attacked vessel are not confirmed.▾
cargo_type_uncertaincargo exposure pendingvalid from 11 Jun 2026, 00:00Marine Cargo
Market relevance: Cargo type determines whether marine cargo, energy cargo, or chemical cargo policies are triggered.
Full damage extent to the vessel is not yet established; engine-room strike and on-board fire raise constructive-total-loss probability but total loss is not confirmed.▾
damage_extent_total_loss_uncertainloss severity upliftvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Engine-room strike plus fire is a high-severity damage pattern for marine hull; constructive-total-loss declaration is plausible pending survey.
“fired precision munitions into the ship engine... resulted in a fire on board” — ianslive.in · 11 Jun 2026, 16:15 · mainstream media
The extent of physical damage to the vessel and potential for total loss has not been confirmed.▾
damage_extent_unknowninformation gapvalid from 17 Jun 2026, 10:31Marine Hull
Market relevance: Gating item for marine hull constructive total loss assessment and salvage/general average activation.
The extent of physical damage to the vessel, including potential constructive total loss, has not been confirmed.▾
physical_damage_extent_uncertainhull loss quantum gapvalid from 17 Jun 2026, 03:19Marine Hull
Market relevance: Damage extent is the primary driver of hull recoverable loss; uncertainty delays quantum assessment and any general average declaration.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The extent of physical damage to the vessel, including potential total loss, has not been confirmed in the available sources.▾
damage_extent_uncertainhull loss uncertaintyvalid from 17 Jun 2026, 03:19Marine Hull
Market relevance: Determines hull loss quantum and recovery prospects; key driver of insured loss band.
“Extent of physical damage and potential total loss” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The extent of physical damage to the attacked vessel and whether a constructive or actual total loss is possible has not been confirmed in available sources.▾
vessel_damage_extent_unconfirmedloss exposurevalid from 16 Jun 2026, 16:10Marine
Market relevance: high
Attribution of the attack (state actor, proxy, or other) has not been confirmed in available reporting.▾
attack_attribution_unknowninformation gapvalid from 17 Jun 2026, 10:31War Risk (Marine)
Market relevance: Influences war risk policy attribution clauses and potential political-violence or terrorism carve-ins.
The vessel's cargo (type and value) has not been confirmed in available reporting.▾
cargo_unknowninformation gapvalid from 17 Jun 2026, 10:31Marine Cargo
Market relevance: Prevents insured loss quantum estimation for marine cargo; material gating input for hull and cargo loss estimates.
“No details on vessel name, flag, ownership, or cargo have been disclosed.” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The vessel's name, flag, ownership, and type have not been disclosed in available reporting.▾
vessel_identity_unknowninformation gapvalid from 17 Jun 2026, 10:31Marine Hull
Market relevance: Prohibits specific named-vessel loss estimates and identification of assured interests; a key gating item for underwriter exposure mapping.
“No details on vessel name, flag, ownership, or cargo have been disclosed.” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The type and value of the vessel's cargo have not been confirmed in the available sources.▾
cargo_type_value_uncertaincargo loss uncertaintyvalid from 17 Jun 2026, 03:19Marine Cargo
Market relevance: Critical gap for marine cargo loss estimation; impacts underwriting and aggregate exposure assessment.
“details on vessel ownership, flag, and cargo are not confirmed” — hongkongherald.com · 11 Jun 2026, 04:30 · mainstream media
Whether the vessel was carrying cargo, the type of cargo, and its insured value have not been confirmed.▾
cargo_type_and_value_uncertaincargo loss pathwayvalid from 17 Jun 2026, 03:19Marine Cargo
Market relevance: Cargo type and value drive marine cargo loss estimation and recoverable exposure under Institute Cargo Clauses (War).
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
The impact on Strait of Hormuz transit volumes, rerouting around the cape, and tonnage diversion has not been confirmed.▾
transit_rerouting_uncertaintransit disruption and reroutingvalid from 17 Jun 2026, 03:19Marine Cargo
Market relevance: Any sustained rerouting around the Cape of Good Hope would expand voyage risk exposure, marine cargo loss-of-hire claims, and P&I diversion cost recovery for Persian/Arabian Gulf trade.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — srilankasource.com · 11 Jun 2026, 04:45 · mainstream media
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
If transit safety is questioned, shippers and operators may reroute or delay transits, with knock-on effects on freight, charter rates, and reinsurance pricing for Persian Gulf exposure.▾
transit_rerouting_risktransit disruptionvalid from 11 Jun 2026, 00:00Marine Hull
Market relevance: Rerouting affects freight rates, charter markets, and aggregate exposure to the chokepoint.
The name, flag, ownership, and IMO number of the attacked vessel have not been publicly confirmed.▾
vessel_identity_uncertainattachment and screening gapvalid from 17 Jun 2026, 03:19Marine Hull
Market relevance: Vessel identification is a prerequisite for confirming policy attachment, sanctions screening, and underwriter exposure lookup.
“IMO condemns ship attack near Strait of Hormuz, three seafarers reported missing” — newyorktelegraph.com · 11 Jun 2026, 04:45 · mainstream media
Supersession history: 1 prior/revised claim rows.
Attribution of the attack to any specific actor or group has not been confirmed in available sources.▾
attack_attribution_unconfirmedgeopolitical signalvalid from 16 Jun 2026, 16:10Marine
Market relevance: high
The name, flag state, ownership, and cargo type of the attacked vessel have not been confirmed in available reporting.▾
vessel_identity_and_flag_unconfirmedloss exposurevalid from 16 Jun 2026, 16:10Marine
Market relevance: medium
“Identity and flag of the attacked vessel uncertain” — utahindependent.com · 11 Jun 2026, 01:30 · mainstream media
Geographic Zone Matches
7 active matches
- Oman (12nm coastal buffer)Rule-basedConfidence 100%
- OFAC Sanctioned CountriesRule-basedConfidence 100%
- United Arab Emirates (12nm coastal buffer)Rule-basedConfidence 100%
- JWC Listed AreasRule-basedConfidence 100%
- EU Sanctions ListRule-basedConfidence 100%
- Iran (12nm coastal buffer)Rule-basedConfidence 100%
- Persian/Arabian Gulf, Gulf of Oman, Indian Ocean, Gulf of Aden and Southern Red SeaRule-basedConfidence 100%
Geographic zone matches are RiskEvents spatial/analytical indicators, not coverage determinations or Lloyd's official classifications.
Affected countries
🇦🇪 United Arab Emirates🇮🇳 India🇮🇷 Iran🇴🇲 Oman🇸🇦 Saudi Arabia🇺🇸 United States🇾🇪 Yemen
Latest developments
- IMO has publicly condemned the attack on the tanker, calling it unacceptable and demanding an end to attacks on commercial shipping. — ianslive.in
- Reports indicate precision munitions struck the ship's engine room, causing fire on board; the U.S. has confirmed a separate military strike in the area. — ianslive.in
- Fire has been reported on board the vessel following the strike on the engine room. — ianslive.in
- Three Indian crew members were confirmed killed in the attack, per subsequent reporting. — ianslive.in
- Three seafarers remain reported missing in addition to the three confirmed killed. — ianslive.in
- 21 Indian sailors were rescued from the vessel. — ianslive.in
- The attacked tanker carried an Indian crew, with Indian Ministry of External Affairs engagement on the incident. — ianslive.in
- The incident lies near the Strait of Hormuz in a JWC-listed war risk area and a critical energy chokepoint. — miragenews.com
Timeline
Intelligence Refresh18 Jun 2026, 16:57
Status Change17 Jun 2026, 10:31
Status changed to monitoring
Auto-transitioned: no updates for 6 hours
active -> monitoring
Corroboration17 Jun 2026, 04:31
The International Maritime Organization has condemned an armed attack on a vessel near the Strait of Hormuz, with three seafarers reported missing. The incident occurs in one of the world's most critical maritime chokepoints, raising concerns for commercial shipping, crew safety, and war risk insurance pricing in the Persian Gulf.
Source: caribbeanherald.com (Mainstream Media) · View source
Corroboration17 Jun 2026, 03:26
The International Maritime Organization has condemned an attack on a vessel near the Strait of Hormuz, with three seafarers reported missing. The incident occurs in a critical maritime chokepoint already designated as a JWC listed war risk area, with direct implications for marine hull, marine cargo, and war risk insurance books.
Source: srilankasource.com (Mainstream Media) · View source
Intelligence Refresh17 Jun 2026, 03:24
Status Change16 Jun 2026, 20:14
Status changed to active
evidence_trigger: developing_promotion
developing -> active
Intelligence Refresh16 Jun 2026, 16:23
Lloyd's classifications
Tracking this kind of risk? Get an email when War & Armed Conflict events escalate.
Get alerts