- Date
- August 2026
- Location
- United States + 2 more
- Industry
- Transportation
- Access vector
- Unknown
- OT targeting
- Unknown
- Primary peril
- None
- Impact duration
- 1.25 days
VL Prosperity crude tanker cyber compromise, 2026

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. In August 2026, the very large crude carrier VL Prosperity, carrying nearly 2 million barrels of Saudi crude from Egypt to Texas, reportedly lost communications for more than 30 hours in the Strait of Gibraltar[1][2]. When she reached the Gulf of Mexico, the US Coast Guard and FBI boarded her for four days, found “malicious cyber activity” and, her manager says, cleared her for normal operations[3][4][2].
Why it matters. The concern US officials describe is the link between a ship’s IT systems and the systems that control propulsion and navigation[3][4]. In October, unnamed US officials said hackers had temporary access to the propulsion system; what they could control is not known[5].
About this analysis. This analysis sets out what is known, stage by stage. The agencies have released no technical findings, and the most dramatic claims about the engine come only from Iranian state media. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- The Coast Guard and FBI said they boarded the ship after indications that its network was compromised by “foreign cyber actors,” and reported no operational disruption, vessel instability, danger to crews or environmental impact[1][6].
- Iranian state media said attackers reduced the engine’s cooling flow, raised its speed and disabled the fuel and engine-oil tank. No US agency has said so[7][8].
- Unnamed US officials told Bloomberg in October that hackers had temporary access to the propulsion system, and that how the breach occurred and who did it were still being examined[5].
- No one has been named as the attacker, and no loss in money has been disclosed[1][5].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [confirmed]
- Threat actors: Not attributed [unknown | Unnamed foreign cyber actors]
- Access vector: Not established [unknown | No source says how]
- IT impact: System Outage [reported | Communications lost for 30+ hours]
- OT targeting: Unknown [unknown | Pathway not established]
- OT sophistication: Unknown [unknown | Targeting not established]
- OT impact: Manipulate Control [reported | T0831, Iranian state media claim]
- Perils: No Perils [confirmed | No physical event reported]
- Financial losses: Cyber Incident Response [confirmed | No amount]; Assets & Equipment [confirmed | Return-to-service inspection]; Cyber-Physical Incident Response [confirmed | Regulatory oversight]
What happened
VL Prosperity is a 333-meter, Liberian-flagged crude tanker built in 2015[9], managed by South Korea’s HMM Ocean Service[3][4]. She loaded nearly 2 million barrels of Saudi crude at Sidi Kerir, Egypt, in late July, according to ship-tracking data, and left on August 1 for Galveston, Texas[2][3][4]. In the Strait of Gibraltar she was hacked and lost communication for over 30 hours, according to unnamed sources[1]. On August 20, Iran’s Mehr News Agency published the first report, dating the outage to August 7 and describing interference in the engine room[7].
On August 21, with the ship in the Gulf of Mexico, a team of Coast Guard cyber personnel, law enforcement officers, a vessel inspector and FBI Cyber Action Team operators boarded her for four days[3][4]. Their joint statement said the boarding was meant “to ensure integrity of the vessel’s operational and information technology systems”[1][6]. Rear Adm. Amy Grable, commander of Coast Guard Cyber Command, said the team “did find malicious cyber activity”[3][4]. HMM Ocean Service told Bloomberg the tanker had been cleared by the Coast Guard for normal operations and that it was awaiting a final report from US authorities[2]. The story reached the US press on September 16. A second ship, boarded on August 24, has not been named by the US; the Wall Street Journal, as relayed by Cybernews, names it as the LPG carrier Kohaku[10][11].
In early October, Bloomberg reported, citing unnamed US officials, that investigators had found evidence that hackers accessed the ship’s propulsion system as she approached the Texas coast. “It wasn’t immediately clear how long the hackers had access and what they could’ve controlled aboard the ship with it,” Bloomberg wrote[5]. The Coast Guard declined to comment, and the FBI pointed to its earlier statement[12].
Intent: malicious
The Coast Guard’s own words are “malicious cyber activity,” and the joint statement speaks of “foreign cyber actors”[3][4][1]. That settles intent. What the attackers wanted does not follow from it. No source reports a ransom demand, encryption or a threat to leak data, so this does not look like the ransomware a reader might expect on a merchant ship. Mehr relayed commentary tying the attack to the confrontation between the US and Iran[7], but no official source states a purpose.
Threat actors: not attributed
No one has been named. US authorities are investigating whether Iran or another actor was responsible[1], and the Wall Street Journal says officials are considering “Iran or an Iran-aligned actor,” as relayed by Cybernews[10]. The Coast Guard has not publicly linked the attack to Iran[3][4]. Iranian state media reported the attack first, and TechRadar says Mehr hinted it was a “message from Iran’s Resistance Front”[13]. No group has claimed it. Attribution is classed as suspected, and no threat actor is highlighted on the map.
Access vector: not established
No source says how the attackers got in. In October, officials were still examining how the breach occurred[5]. Grable’s stated concern is IT systems “connected to other systems on the ship that control propulsion, navigation and other systems that are critical to the safety of that vessel”[3][4], but no source names the ship-to-shore link, or any other route, as the way in. The stage is marked unknown.
IT impact: a confirmed compromise, techniques unknown
The compromise itself is confirmed: the boarding team assessed “the information technology and the other systems on board the vessel” and found malicious activity[3][4]. No tool or technique has been named. Asked about the skill involved, Grable said “Not necessarily that sophisticated. There is malicious source code that people can get their hands on”[3][4].
The loss of communications is reported, not confirmed. Unnamed sources told ABC News it lasted over 30 hours[1]; Mehr also says 30 hours[7]; TechRadar, citing Cybernews and a crew member, says a day and a half[13]. No official statement gives the outage or its cause. It is shown as System Outage, reported.
OT targeting: not established
The pathway cannot be classified from the evidence. The official account supports a network compromise with no operational disruption, but the agencies reviewed the operational systems and have not said what they found there[1][6]. In September a CISA official said the hackers did not appear to have taken control of the targeted ships[8]. In October, unnamed officials said hackers had temporary access to the propulsion system[5], which points the other way but says nothing about what was done. The Iranian account, if true, would make this a direct OT compromise. This analysis does not choose between an agency’s silence and an interested party’s claim.
OT sophistication: unknown
Sophistication cannot be graded while the targeting is unknown. Grable’s remark that the activity was “not necessarily that sophisticated,” and that malicious source code is available to anyone, describes the compromise in general[3][4]. It does not say what, if anything, was done to the ship’s operational systems, which is where an OT grade would come from. The stage is marked unknown.
OT impact: an uncorroborated claim about the engine
The only account of action on the engine is Iranian state media’s. Citing an unnamed crew member and Russian-language outlets, Mehr said attackers “infiltrated the engine-room systems, reduced the engine’s cooling flow, increased the engine speed, and disabled the ship’s fuel and engine-oil tank”[7]. No US agency has said this. It is shown as Manipulate Control, reported, as an interested party’s claim rather than an observed technique.
Access is reported; action is not. Unnamed US officials say hackers had temporary access to the propulsion system, without saying what they did[5]. The loss of ship-to-shore communications was a loss of contact, and no source says the crew lost sight or control of anything aboard.
Perils: none
There was no physical event. The Coast Guard and FBI report no operational disruptions, vessel instability, physical danger to crews or environmental impacts[1][6]. SecurityWeek reports Grable saying nothing found during the inspection suggested the tanker was unsafe to operate[14]. With nearly 2 million barrels aboard, pollution was the obvious risk, and none is reported. No source reports overheating, breakdown or fire, so the map shows No Perils.
The risk the Coast Guard names is not the ship’s office network but what that network is connected to.
Financial losses: the cost of the response
No figure of any kind has been disclosed. What is confirmed is the response: a four-day boarding by the Coast Guard’s Cyber Protection Team and the FBI’s Cyber Action Team, with the owner’s shore staff cooperating, ending in clearance for normal operations[3][4][6][2]. Most of that work was done at public cost, and the owner’s share is not reported. Grable called it one of roughly 40 to 50 such missions in the past year[3][4], and the Coast Guard has asked for advance notice before any of the nearly 20 ships US agencies are tracking enters a US port[8].
Bloomberg reported the ship idling off the Texas coast in mid-September and still anchored offshore Galveston in early October[2][5]. No source ties that wait to the incident.
Loss evidence
- Confirmed: Network event response and recovery (the four-day boarding); Return-to-service validation (clearance for normal operations); Regulatory oversight (the same boarding, not additive)
- Not supported: Direct business interruption (no delay, off-hire or demurrage reported); Equipment repair or replacement; Spills and cleanup; Bodily injury; Ransom extortion
What this incident shows
This is a confirmed compromise with no confirmed consequence. What the record documents is the response: a regulator’s four-day inspection, with a vessel inspector aboard, ending in clearance before the ship went on with normal operations[3][4][2]. Even with no damage, a compromise of this kind costs time and oversight.
The open question is the one Grable put plainly: whether a ship’s IT systems are connected to the systems that control propulsion and navigation[3][4]. The October report of temporary access to the propulsion system makes that question sharper without answering it[5]. Until the Coast Guard, the FBI or the owner says what the crew actually saw, the engine claims remain an interested party’s account.
References
- Thomas, Pierre, Luke Barr, and Jack Date. “Coast Guard, FBI Investigating after 2 Oil Tankers Bound for US Hit with Cyberattacks: Sources.” ABC News, 16 Sept. 2026. abcnews.com/Politics/coast-guard-fbi-investigating-after-2-oil-tankers/story?id=136482324
- “USCG, FBI Conduct Cyberattack Probes on Oil Tankers.” Rigzone (Bloomberg wire), 16 Sept. 2026. rigzone.com/news/wire/uscg_fbi_conduct_cyberattack_probes_on_oil_tankers-16-sep-2026-184631-article/
- Sganga, Nicole. “Coast Guard, FBI Boarded Texas-Bound Oil Tanker after Ship’s Network Was Potentially Breached.” CBS News, 16 Sept. 2026. cbsnews.com/news/coast-guard-fbi-board-oil-tanker-texas/
- Sganga, Nicole. “Coast Guard and FBI Boarded 2 Energy Tankers Due to Cyberattacks. How Big Is the Risk?” CBS News, 16 Sept. 2026. cbsnews.com/news/coast-guard-fbi-boarded-energy-tankers-cyberattacks-amy-grable-iran/
- Bleiberg, Jake, and Ruth Liao. “Hackers Breached Propulsion System of US-Bound Oil Tanker.” The Star (Bloomberg), 5 Oct. 2026. thestar.com.my/tech/tech-news/2026/10/05/hackers-breached-propulsion-system-of-us-bound-oil-tanker
- Whittaker, Zack. “FBI, Coast Guard Boarded Hacked Oil Tankers Heading Toward US Coast.” TechCrunch, 18 Sept. 2026. techcrunch.com/2026/09/18/fbi-coast-guard-boarded-hacked-oil-tankers-heading-towards-us-coast/
- “US-Bound Oil Tanker Targeted in Cyberattack.” Mehr News Agency (Iranian state media), 20 Aug. 2026. en.mehrnews.com/news/247123/US-bound-oil-tanker-targeted-in-Cyberattack
- “U.S. Tracks Cyber Threats Against Nearly 20 Ships Worldwide.” gCaptain (Bloomberg), 16 Sept. 2026. gcaptain.com/u-s-tracks-cyber-threats-against-nearly-20-ships-worldwide/
- “VL PROSPERITY, Crude Oil Tanker, IMO 9683697.” VesselFinder. vesselfinder.com/vessels/details/9683697
- “Coast Guard, FBI Called In after Hackers Hit Two Texas-Bound Oil Tankers, Iran Link Probed.” Cybernews, 17 Sept. 2026. cybernews.com/news/iran-oil-tanker-cyberattack-fbi-texas/
- Murga, Arnel. “Three Tanker Cyber Incidents in a Month Put Shipboard Systems under Scrutiny.” Digital Ship, 21 Sept. 2026. thedigitalship.com/news/maritime-satellite-communications/three-tanker-cyber-incidents-in-a-month-put-shipboard-systems-under-scrutiny/
- “Hackers Breached Propulsion System of US-Bound Oil Tanker.” gCaptain (Bloomberg), 5 Oct. 2026. gcaptain.com/hackers-breached-propulsion-system-of-us-bound-oil-tanker/
- Fadilpašić, Sead. “FBI Confirms Two Texas-Bound Oil Tankers Hit by Hackers Who Disabled Coms and Put the Engines into Overdrive -- and Iran Is Possibly to Blame.” TechRadar, 18 Sept. 2026. techradar.com/pro/security/fbi-confirms-two-texas-bound-oil-tankers-hit-by-hackers-who-disabled-coms-and-put-the-engines-into-overdrive-and-iran-is-possibly-to-blame
- Kovacs, Eduard. “Cyberattacks on Two Oil Tankers Prompt Coast Guard, FBI to Board Vessels.” SecurityWeek, 17 Sept. 2026. securityweek.com/cyberattacks-on-two-oil-tankers-prompt-coast-guard-fbi-to-board-vessels/


