Port of Seattle — Rhysida ransomware (August 2024)
August 2024 · Seattle, US. A public, sourced maritime cyber case.
At a glance: who, what, when, where, impact, type
Six facts, taken from the public sources below. Nothing here is inferred.
Who
What
When
Where
Impact
Type
Incident types in this case. Each button opens our threat page: what it is, how it spreads, how to recover.
What happens in this kind of case
When one authority runs a port and an airport, one intrusion has two blast radii. The ransomware lands on the shared corporate systems the week before a holiday; staff isolate what is critical, and travellers and cargo meet the same degraded screens, websites and phone lines for weeks.
Refusing to pay is the right stance, and it only holds with two things already in hand: offline backups that make the encryption survivable, and a breach-notification plan for the data the gang takes before encrypting. Months later, the authority is still writing to the people whose files left.
August 2024 in Seattle is the case that showed port authorities that the perimeter of an incident is the perimeter of the organisation, not of the quay, and that the no-pay decision is prepared, not improvised.

What to do, and what we recommend
Four measures that would have changed the autumn of 2024 for any port authority with more than one facility. Each one opens the page where we explain how.
There will always be problems. The question is whether you see them.
Weeks of degraded systems and 90,000 letters. A SIEM is what shortens the first and shrinks the second, by seeing the intrusion before the holiday weekend. Do you have yours?

Report an incident, in confidence
Ongoing or past, suspected or confirmed: a human reads it, and we call you back within 15 minutes during office hours when it is still running. Logs and screenshots can follow by email.

Sources, as published
We keep only what the sources say. Dates and sites are those of the original articles.

Port of Seattle · September 2024 (archive of official updates)
Port cyberattack archive: official statements from 24 August 2024 onwards
Every public incident on the map
18 public, sourced cyber incidents across global ports and carriers, 2011 to 2026. Open any card for the full story and its public source.
2011-2013 · Antwerp, BE · Criminal intrusion
June 2017 · Copenhagen (HQ) — worldwide, DK · Collateral malware
May 2020 · Bandar Abbas, IR · Nation-state intrusion
Jan + May 2020 · Melbourne, AU · Ransomware
July 2021 · Durban, ZA · Ransomware
Aug-Sep 2021 · Houston, US · Nation-state intrusion
February 2022 · Antwerp / Amsterdam-Rotterdam-Antwerp + German coast, BE · Ransomware
February 2022 · Nhava Sheva (Mumbai), IN · Ransomware
December 2022 · Lisbon, PT · Ransomware
April 2023 · Montreal, CA · Hacktivist DDoS
July 2023 · Nagoya, JP · Ransomware
November 2023 · Melbourne, AU · Criminal intrusion
August 2024 · Seattle, US · Ransomware
November 2026 · Copenhagen (HQ) — isolated subsidiary system, DK · Criminal intrusion
2022-2023 (public figures) · Los Angeles, US · Threat pressure (not a breach)
When one port sees a threat, every member is warned.
The Port Cyber Alliance turns one port’s incident into every member’s early warning. Join the alliance and share the signal.

