2017 A.P. Moller–Maersk — NotPetya destructive worm; bookings & terminals offline; ~$300M+ impact cited
Data compromised
Operational and transactional availability loss dominated reporting—track-data theft was not the dominant frame versus physical shipping paralysis
Technical writeup
The June 2017 NotPetya propagation originating from poisoned M.E.Doc update paths in Ukraine spilled into A.P. Moller–Maersk A/S’s tightly coupled global Windows/Active Directory footprint—paralyzing Maersk Line bookings, APM Terminals operations, and internal collaboration until systems could be rebuilt. Investor IR posts and enterprise security long-reads (e.g., WIRED’s systemic postmortem) treated Maersk as the marquee maritime casualty of the worm, with insured financial impact figures widely discussed in the hundreds of millions of dollars. This row keys the `a-p-moller-maersk` directory slug to that group-wide catastrophe (parallel rows already exist for `maersk` / `maersk-line` branding).
Root cause
Destructive self-spreading malware introduced via trusted software supply paths and lateral movement across under-segmented enterprise IT