Port of Barcelona (September 2018)
September 2018 · Barcelona, ES. 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
A ransomware case in a port usually unfolds the same way. An initial access (phished credentials, an exposed remote service, a vendor connection) sits unnoticed for days. Then the encryption runs at night or at the start of a weekend, and the first thing operations see is a gate, a planning screen or a terminal operating system that no longer answers.
The port then has two problems at once: keep cargo moving with a manual mode that has (or has not) been rehearsed, and restore internal servers from backups that are (or are not) isolated from the network that was hit. The public statement comes within hours; the forensic answer comes weeks later, if ever.
Barcelona and San Diego being hit within days of each other in September 2018 is what makes this case useful: it reads as a sector-wide pattern, not bad luck.

What to do, and what we recommend
Four measures that would have changed the week of 20 September 2018 for any port. Each one opens the page where we explain how.
There will always be problems. The question is whether you see them.
A contingency plan keeps cargo moving. A SIEM tells you, hours earlier, that something is moving inside your network. 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.

INCIBE-CERT (Spanish national CERT) · September 2018
Port of Barcelona suffers a cyber attack: cybersecurity highlight

Security Affairs · 20 September 2018
Hackers target Port of Barcelona, maritime operations had not affected
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.
