War Reaches Sri Lanka's Shores: U.S. Submarine Sinks Iranian Frigate Near Galle — the First Such Torpedo Strike Since WWII
Washington says a U.S. submarine torpedoed and sank Iran's frigate IRIS Dena off Sri Lanka—an escalation so rare it's being described as the first U.S. torpedo sinking of an enemy vessel since World War II. Sri Lanka's navy pulled survivors from oil-slicked waters and rushed 32 wounded to Karapitiya Hospital as casualty estimates climbed and a new question emerged: why is a Middle East war killing people off Galle?
The Middle East war has just generated a headline that lands like a thunderclap in the Indian Ocean: a U.S. submarine sank an Iranian warship off Sri Lanka's southern coast, according to U.S. Defense Secretary Pete Hegseth. (Reuters)
If confirmed as described by U.S. officials, it is not just another escalation—it is an almost historical one. Multiple outlets report Hegseth framed the strike as the first U.S. submarine torpedo sinking of an enemy vessel since World War II. (The Guardian) And given the reported death toll, it may also be the deadliest U.S. submarine torpedo action of this type in the entire post-1945 era—not because the U.S. has been quietly doing this for decades, but because it hasn't. (Reuters)
The vessel is widely identified as the Iranian frigate IRIS Dena, reportedly transiting home after participating in the MILAN naval exercise hosted by India in the Bay of Bengal (Feb. 18–25). (Reuters) In other words: this was not a ship hovering near the Strait of Hormuz. It was in the Indian Ocean—near one of South Asia's busiest commercial corridors—when it went down.
Sri Lanka's rescue operation: Karapitiya becomes a war hospital, overnight
Sri Lanka's role began with a distress call and rapidly turned into an urgent rescue mission. Reuters reported Sri Lanka launched a search-and-rescue operation after receiving a distress call, with 32 people rescued and treated in the southern port city of Galle. (Reuters) The Associated Press described Sri Lankan navy ships arriving to find the warship already sunk, with oil patches, life rafts, bodies, and survivors in the water. (AP News)
Local reporting adds the human detail that international wires can't. Newswire.lk reported 32 wounded were admitted to Karapitiya Teaching Hospital, with the hospital director stating one was in critical condition, seven had moderate injuries, and the remainder had minor injuries—cuts, burns, and fractures consistent with blast-and-sinking trauma. (StreetInsider.com)
On fatalities, the numbers are still moving—and politically loaded. Reuters cited Sri Lanka's deputy foreign minister saying at least 80 were killed. (Reuters) AP later reported Sri Lanka's navy had recovered 87 bodies from the sea.
Where exactly did this happen—and why does that detail matter?
Sri Lankan officials have stressed the sinking occurred outside Sri Lanka's territorial waters, even as the rescue falls within Sri Lanka's responsibilities under maritime conventions and its search-and-rescue remit. (Reuters) The Financial Times reported the incident occurred about 40 nautical miles off Galle. (Financial Times)
This distinction is not legal trivia. It's Colombo's diplomatic shield: Sri Lanka can say it acted as a responsible coastal state—rescued survivors, treated the wounded—without endorsing any belligerent's account of what happened.
Washington's version: "We sank it." Colombo's version: "We rescued whoever we could."
In Washington, the story is blunt. Reuters and the FT both report that Hegseth said a U.S. submarine torpedoed the ship in international waters. (Reuters) The FT added the U.S. described using a Mark 48 torpedo and framed the strike as part of a broader campaign to dismantle Iran's naval capabilities. (Financial Times)
Sri Lanka's public posture is different by necessity. It is not Sri Lanka's job to validate U.S. targeting claims; it is Sri Lanka's job to prevent bodies washing onto its beaches and a maritime panic rippling through shipping lanes. A Sri Lankan official quoted by international media put the point in humanitarian terms: rescuing distressed mariners is an obligation "irrespective of the reason." (Deccan Herald)
So: will Sri Lanka "say anything" to the U.S.? Colombo's most likely path is measured: confirm rescue facts, avoid attribution, quietly seek assurances that Sri Lankan waters won't become a repeat arena, and manage the political optics with India, Iran, and the U.S. simultaneously. The tighter the Sri Lankan statement, the more it signals one thing: do not turn our coastline into your battlefield.
The question nobody can ignore: how did a Middle East war end up off Galle?
Two explanations can be true at the same time: the frigate had a legitimate transit route home from South Asia, and the war is now being fought across a larger map than most publics assumed. Reuters notes the ship had recently been involved in MILAN, and was returning when it was struck. (Reuters)
The Guardian and other outlets point to wider U.S. naval reach in the Indian Ocean, with speculation about operational footprints in the broader region. (The Guardian) But even without guessing basing or submarine patrol routes, the strategic takeaway is stark: if combatants treat Indian Ocean transit as targetable space, the war has moved from regional to quasi-global in effect—because it touches the arteries that connect Asia, the Middle East, and Europe.
And that raises the most unsettling implication for smaller coastal states: you don't need to be "in the war" to become part of its consequences.
The "Karapitiya effect": how a distant war hits a local economy
In a South Sri Lanka hospitality group chat, one member (Gabo) wrote: "looks like a submarine attack on Iranian vessel close to Galle," while another (Krishni) replied: "This is not good for us. Last thing we need in the middle of the season & with stranded tourists."
Those aren't official statements; they're field-level sentiment—and sentiment is often what tourism runs on.
Even before this incident, the war has been disrupting aviation routes and raising travel friction across regions. Now the island has a new reputational risk: global headlines placing "Sri Lanka" next to "warship sunk" and "torpedo." Travelers rarely parse EEZ boundaries; they react to atmosphere.
Shipping and insurance are even more sensitive. A strike near Sri Lanka—however "outside territorial waters"—can still raise perceived regional risk, influence underwriting decisions, and accelerate a story that the Indian Ocean is no longer a neutral corridor.
What to watch next
Casualty convergence: Reuters' "80+" and AP's "87 bodies recovered" may reconcile into an official total, but wartime numbers often shift as search patterns expand. (Reuters)
Hospital updates: Karapitiya's status reports are one of the clearest real-world indicators of the event's immediate human impact. (Yahoo News UK)
Diplomatic phrasing from Colombo: if Sri Lanka starts emphasizing "non-involvement," "sovereignty," or "no hostile use of nearby waters," that's a signal it fears recurrence.
Maritime risk spillover: if navies begin targeting further out in the Indian Ocean, this will not stay a Middle East story—even if the core war aims remain Middle Eastern.
Sri Lanka did what coastal states are expected to do under maritime norms: it saved lives. (AP News) The uncomfortable question now is whether this was a one-off tragedy—or the moment a regional war started showing up on Sri Lanka's doorstep, with consequences that could reach far beyond a single sinking.