Maersk, the Danish shipping and logistics group, said on Wednesday, November 11, 2026 that it is investigating an IT security incident involving unauthorized access to, and data extraction from, one of its local legacy systems. The company says the system came from a previous acquisition, the incident is isolated to it, and its “findings so far strongly suggest no sensitive data has been disclosed.” It does not expect any effect on operations.
A group calling itself WhiteArmor claims much more, including plaintext driver passwords and a $5 million ransom demand. Maersk has not confirmed those claims. Below is what each side has said, and what engineering teams can check in their own estates.
What Maersk has said
Maersk’s statement was reported by Reuters and The Register, which says it was published on Maersk’s news page. We could not retrieve the notice itself; the quotes below are as those outlets reported them. According to the statement:
- The incident involves unauthorized access and data extraction from one local legacy system, described as a system “from a previous acquisition.”
- Maersk started an investigation and secured the affected system.
- “Our findings so far strongly suggest no sensitive data has been disclosed.”
- The incident “is isolated to a local system,” with no indication of impact on other Maersk systems or on customer and partner systems connected through integrations such as APIs and EDI.
- Maersk does not expect operations to be affected; customers can keep booking and managing shipments as usual.
- It asks people to treat unexpected communications claiming to relate to the incident with caution and to verify them through their usual Maersk contact.
Maersk has not said when the intrusion happened, how it was detected, how the attackers got in, which system was affected or what data was taken.
Confirmed vs claimed
| Item | Status | Source |
|---|---|---|
| Unauthorized access and data extraction from one local legacy system | Confirmed by Maersk | Reuters, The Register |
| System came from a previous acquisition | Confirmed by Maersk | The Register |
| No indication of impact on other Maersk, customer or partner systems | Maersk’s statement | Reuters, The Register |
| No expected effect on operations | Maersk’s statement | Reuters, The Register |
| “No sensitive data has been disclosed” | Maersk’s preliminary finding (“so far”) | The Register |
| Affected system is the LF Logistics platform | Not confirmed; Maersk has not named the system | Security Affairs, Cybernews |
| About 100 GB stolen, incl. driver records and plaintext passwords | Claimed by WhiteArmor | Security Affairs |
| $5 million ransom in bitcoin, 30-day deadline | Claimed by WhiteArmor | Security Affairs |
| WhiteArmor is responsible | Not confirmed by Maersk | Security Affairs, Cybernews |
What is not confirmed
The claims come from the group’s leak-site listing as described by Security Affairs and Cybernews. We have not viewed the leak site and do not link to it.
- Data volume and types. Security Affairs reports that the group claims about 100 GB from the “OCF/LF Logistics platform”, including “nearly 30,000 driver records, plaintext passwords, 33 super admin accounts”, signed delivery receipts, inventory records, purchase orders, advance shipping notices and 27,842 mobile device logs. Cybernews reports a claim of more than 16,000 plaintext driver passwords. The two reports give different figures, and neither is verified.
- The LF Logistics link. Both outlets note that Maersk bought LF Logistics in 2022 and that this could fit the “previous acquisition” wording. Security Affairs states that “the company has not confirmed this connection.”
- The ransom. Security Affairs reports a $5 million demand in bitcoin with 30 days to pay. This is the group’s claim.
- The name. Security Affairs spells the group “WhiteArmor”; Cybernews uses “WhiteArmour”.
If Maersk’s investigation changes any of this, we will add a dated update at the top of this article.
Why the “legacy system from an acquisition” detail matters
Maersk’s own description is the useful part for engineers. Acquired platforms tend to arrive with their own identity store, admin accounts, password storage, logging and partner integrations, and they keep running until a migration finishes. Maersk says the affected system was isolated and that it sees no impact on systems connected through APIs and EDI; the open question for any company in the same position is whether that isolation was designed or simply the result of the system never being fully integrated.
For context: Maersk is no stranger to large incidents. In 2017 the NotPetya wiper took down its IT; The Register recalls that Maersk said at the time it expected a bill of around $300 million. Nothing reported links the two events, and the 2026 incident, as Maersk describes it, is far narrower.
What to check in your own environment
These follow from the confirmed facts (an acquired legacy system, data extraction, partner integrations, phishing risk) and are not a reconstruction of the Maersk attack, whose method has not been disclosed.
- Inventory acquired systems as their own estate. List every platform that came with an acquisition, who owns it today, whether it has its own internet exposure, and its retirement date. Systems without a named owner rarely get patched.
- Check how they store passwords. If an inherited application stores driver, supplier or customer passwords reversibly or in plaintext, that is the first thing to fix. Our Argon2id vs bcrypt vs scrypt guide covers what to migrate to and how to rehash on next login.
- Review super-admin accounts. Count administrative accounts on inherited platforms, remove unused ones and put the rest behind your central identity provider with MFA.
- Map and scope the integrations. For each API and EDI connection between the legacy system and the rest of the business, record the credentials it uses, what they can reach and when they were last rotated. Rotate them after any suspected compromise, even if the vendor says there is no indication of impact.
- Prepare for follow-on phishing. Maersk’s warning about unexpected communications applies to anyone whose contact details may be in stolen logistics data. Our third-party SaaS vetting guide covers questions to ask suppliers about how they hold your data.
Sources and verification
| Important claim | Source | Status |
|---|---|---|
| Maersk statement: unauthorized access and data extraction, local legacy system, no expected operational impact | Reuters via 102.7 WBOW | Verified (two outlets) |
| Statement quotes; system “from a previous acquisition”; API/EDI wording; phishing caution; NotPetya $300M context | The Register | Verified (Maersk notice not retrieved directly) |
| WhiteArmor claims: ~100 GB, data types, $5M, 30 days; Maersk has not confirmed LF Logistics link | Security Affairs | Qualified (claims, unverified) |
| Claim of 16,000+ plaintext driver passwords; LF Logistics acquired 2022 | Cybernews | Qualified (claims, unverified) |
Frequently asked questions
Was Maersk hacked in November 2026?
Maersk said on November 11, 2026 that it is investigating an IT security incident involving unauthorized access to, and data extraction from, a local legacy system from a previous acquisition. It says the incident is isolated to that system.
Are Maersk shipping operations affected?
Maersk says it does not expect the incident to affect operations and that customers can continue to use its platforms to book and manage shipments as usual.
Who is behind the Maersk attack?
A group calling itself WhiteArmor listed Maersk on its leak site and claims to have stolen data, according to Security Affairs and Cybernews. Maersk has not confirmed any link between the group and the incident.
Is this related to the 2017 NotPetya attack on Maersk?
Nothing reported links the two. NotPetya in 2017 was a destructive wiper that shut down Maersk's IT; the 2026 incident, as Maersk describes it, is data extraction from one isolated legacy system.
Hacking NewsMaerskData BreachRansomwareMergers and AcquisitionsLegacy SystemsSupply Chain
