
On 11 November 2026, A.P. Moller-Maersk confirmed that it was investigating unauthorised access to one of its local legacy systems, with data extracted from it. The company's early findings, as reported by the maritime press, are reassuring on the essentials: no sensitive data appears to have been disclosed, the incident is isolated to that one system, and the links that matter to the rest of the chain — APIs, EDI, container operations — are untouched. An extortion group calling itself WhiteArmor has claimed the attack and asked for a ransom; none of its claims has been independently verified.
We are not going to comment on Maersk's choices. Teams at that scale handle incidents every week, with people and tools most ports will never have. What is worth a few minutes of your time is the shape of the incident, because it is the most common shape we see in ports of every size.
What is actually known
Sources: Splash247, Container News, Cybernews, OODA Loop. The picture may change as the investigation continues.
Where
Impact
Attacker claims
Why "legacy and local" is the pattern that matters
In a port or a terminal, the terminal operating system gets the attention: it is patched, monitored, segmented. Next to it live the systems nobody owns any more — the EDI translator installed with a carrier in 2009, the gate camera server that still runs an old Windows, the customs interface a contractor built and left, the reporting database that was "temporary" five years ago. They are local, they are old, and they are connected to everything, because they were built to be.
That is where attackers go, not because they are clever but because it is easier. A legacy system rarely has multi-factor authentication, rarely logs to a central place, and rarely has an owner who would notice a new administrator account. Data sits there in copies: manifests, bookings, driver lists, invoices. You do not need to stop a crane to hurt a port; you need to copy a database.
Three things a port team can do this week
None of this requires a budget line. It requires an afternoon, a spreadsheet and the honesty to write "unknown" where it applies.
Write the list
Cut what does not need to be connected
Make it visible
If you have the same cases
Most ports do, and that is fine — you are grown-ups, you can handle it. If you want a quick, private way to see where you stand, we built two self-assessments that take about two minutes and stay in your browser until you decide otherwise: one for engineers, one for the people who lead the team. If something in your result worries you, talk to us in confidence. And when one port sees a threat, every member of the Alliance is told: that is the whole point.
Want a second pair of eyes on your site?
Every member gets cyber advice and two site visits a year. Start with a two-minute self-assessment.



