100percentfedup.com
BREAKING: Cargo Ship Hit By “Unknown Projective” In The Strait of Hormuz, Story Developing.
A cargo vessel has been struck near the Strait of Hormuz, and the world’s busiest oil chokepoint is on edge again.
The hit came right where Iran has been warning ships to turn back.
Here is what we know, and what is still unconfirmed.
UK Maritime Trade Operations issued Warning 074-26 on June 25, 2026, reporting an incident 7.5 nautical miles southeast of Dahit, Oman.
A cargo vessel was hit on the starboard side by what UKMTO called an unknown projectile. The strike damaged the vessel’s bridge.
The master reported no casualties and no environmental impact. Authorities are investigating.
The UKMTO Warning 074-26 is the cleanest official source on the incident and keeps the facts narrow.
The report date is June 25, with a 1410 UTC report time, and the source is listed as the vessel’s master. UKMTO places the incident 7.5 nautical miles southeast of Dahit, Oman, on the Omani side of the Hormuz/Gulf of Oman transit area.
The warning says a cargo vessel was hit on the starboard side by an unknown projectile, causing damage to the bridge. The master reported no casualties and no environmental impact, which is the first piece of good news in an otherwise dangerous report.
UKMTO also said authorities are investigating and advised vessels to transit with caution while reporting suspicious activity. UKMTO did not name the vessel and did not assign blame.
UKMTO WARNING 074-26 – ATTACK
Click here to view the full warning. https://t.co/0hDEAb7xO9#MaritimeSecurity #MarSec pic.twitter.com/HlPzQDLBja
— UKMTO Operations Centre (@UK_MTO) June 25, 2026
The fallout hit fast on the humanitarian side.
The International Maritime Organization announced it was pausing its evacuation plan after being told of an attack in the Gulf of Oman on a vessel that had passed through the Strait of Hormuz.
The IMO statement said the struck vessel did not transit under the IMO’s evacuation framework, which matters because the agency had just begun trying to move stranded ships and crews out safely.
Secretary-General Arsenio Dominguez said several vessels had already been successfully evacuated under the plan before the pause. He said the pause is meant to reconfirm that safety guarantees remain in place for ships on the evacuation list and for all vessels in the region.
The timing is brutal because the IMO statement also notes the evacuation issue on the Day of the Seafarer. Thousands of sailors remain stuck in the wider Gulf crisis, and one strike was enough to force the U.N. maritime agency to stop and reassess.
In plain terms, this is no longer only a shipping-lane story. It is a seafarer-safety story, an energy-security story, and a test of whether anyone can guarantee safe passage through Hormuz right now.
IMO pauses evacuation plan."I have been informed of an attack today in the Gulf of Oman. Seafarer safety remains paramount. To ensure coordinated approach & navigational safety, the IMO evacuation plan will be paused until further clarity."– @IMOSecGenhttps://t.co/UtvKjTtG5N pic.twitter.com/29m2lMkt1V
— International Maritime Organization (@IMOHQ) June 25, 2026
Now to the question everyone wants answered: who fired?
Officially, the projectile remains unidentified. That is important, because early Hormuz reporting is moving fast.
The Associated Press reported it was unclear who launched the projectile or what type of vessel was targeted.
AP also reported the strike came after Iran threatened vessels using a new route through the strait without Tehran’s permission. That route runs near Oman, was promoted by the U.N. maritime agency, and had been used as a way to get ships moving again.
Iran’s Persian Gulf Strait Authority said transit outside its designated routes would not be covered by its safe-passage guarantee. AP reported that traffic through the strait had risen recently but remained below prewar levels.
That context is what makes the projectile report so serious. A single strike can undo days of confidence-building, scare off commercial traffic, and hand Tehran leverage over ships that are supposed to have freedom of navigation.
The New York Post went further, reporting that a Singapore cargo ship was struck by Iran’s IRGC after Iranian orders for vessels to turn back from the new lane near Oman.
The Post described bridge damage with no casualties and identified the fight over the Omani route as a central flashpoint in the shipping dispute. It also reported that traffic remains far below normal despite the recent effort to reopen movement through the strait.
So keep the distinction clean: UKMTO says unknown projectile. Other reporting points at Iran and the IRGC, and some outlets identify the vessel as the Singapore-flagged Ever Lovely, though UKMTO itself did not name a vessel.
A cargo vessel was struck by an unknown projectile off the coast of Oman on Thursday, causing damage to its bridge but leaving no reported casualties or environmental impact, the UK Maritime Trade Operations said.
The British maritime security agency said the incident occurred… pic.twitter.com/fgXcafCDlK
— Iran International English (@IranIntl_En) June 25, 2026
The timing is the story behind the story.
This strike lands directly inside President Trump’s 60-day Iran/Hormuz framework, the deal meant to keep ships moving through the strait safely while talks continue.
Secretary of State Marco Rubio recently made the American line clear: no tolls, no fees, no payments for safe passage.
That is the leverage Iran is testing. A projectile into a cargo bridge, on a route Iran told ships to avoid, is a message aimed at the deal itself.
For now, the official status remains an unknown projectile pending investigation. But the bigger picture is already clear: Hormuz is not calm, the evacuation plan is paused, and the world is watching to see whether Tehran backs down or pushes this fight even further.
This is a Guest Post from our friends over at WLTReport. View the original article here.
The post BREAKING: Cargo Ship Hit By “Unknown Projective” In The Strait of Hormuz, Story Developing. appeared first on 100PercentFedUp.com.