Port Cyber Alliance
November 2026

A legacy-system breach at a global carrier (November 2026)

November 2026 · Copenhagen (HQ) — isolated subsidiary system, DK. 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
A.P. Moller-Maersk (global carrier group), on one local legacy system inherited through a prior acquisition.
What
The group confirmed it was investigating unauthorised access to that one system, with data extracted; a group calling itself WhiteArmor claimed the attack and demanded a ransom.
When
Confirmed on 11 November 2026.
Where
Copenhagen (headquarters); the affected system is an isolated subsidiary system.
Impact
No operational impact on vessels or terminals: early findings strongly suggest no sensitive-data disclosure, the incident isolated to that one system, APIs, EDI and container operations untouched.
Type
Criminal intrusion with data extraction and an extortion claim; the group's claims were not independently verified.

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

The most common pattern in ports of every size is the old, local, unowned system next to the well-guarded core. It came with an acquisition, it still runs, nobody remembers who owns it, and it is still connected. The attacker does not need the core: the legacy corner has accounts, files and a network path, and nobody reads its logs.

The core holds, the operations keep running, and the first question the group cannot answer the same day is « when did it start? », because the logs of that system were never sent anywhere central.

November 2026 is the case that shows the shape, not the scale: legacy corners are where most port incidents start, and an inventory with an owner, a vendor and a last-patch date for every system still switched on is the first measure.

Isometric illustration: server tower

There will always be problems. The question is whether you see them.

The core was watched; the legacy corner was not. A SIEM that reads every system still switched on is what turns « when did it start? » into a date. Do you have yours?

Isometric illustration: magnifier finding a bug in a folder

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.

Isometric illustration: alert on a mobile screen

Sources, as published

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

Idle container terminal, illustration (the source blocks preview fetching)

Splash247 · November 2026

Maersk hit by fresh cyber breach

Source preview image (Container News, November 2026)

Container News · November 2026

Maersk confirms security breach amid hacker claims of major data theft

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

July 2018 · Long Beach, US · Ransomware

September 2018 · San Diego, US · Ransomware

September 2018 · Barcelona, ES · Ransomware

May 2020 · Bandar Abbas, IR · Nation-state intrusion

Jan + May 2020 · Melbourne, AU · 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

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.

Forward this page to a colleague

Contact the alliance

Use our contact form: every message is read by the team.

Report an incident

Port operators can report a cyber incident to the alliance at any time.