Security
Maersk confirms data extraction from a legacy system inherited through an acquisition, while the WhiteArmor group claims 100 GB and demands $5 million
Maersk confirms unauthorized data extraction from a legacy system. WhiteArmor claims 100 GB and demands $5 million; Maersk says no sensitive data was disclosed.
Maersk confirmed on November 11 an IT incident with unauthorized access and data extraction from one of its local legacy systems, inherited from a previous acquisition. The claims of 100 GB and a $5 million ransom come from the WhiteArmor group, not from Maersk. Maersk says its findings so far strongly suggest no sensitive data has been disclosed and that the incident is isolated to that one system.
The essentials
- Maersk’s statement: unauthorized access and data extraction from a local legacy system acquired earlier. It did not name the system, the data type or the date of the intrusion. It found no sign of impact on other systems or on customer and partner systems.
- WhiteArmor’s claim: a newly emerged extortion group says it took about 100 GB from a logistics and supply-chain platform. It wants $5 million in bitcoin within 30 days or it will publish the files.
- Which system: Cybernews researchers link the breach to LF Logistics, a supply-chain business Maersk bought in 2022. Maersk has not confirmed that.
- Operations: reports say shipments continue and the incident has been contained.
What is confirmed and what is claimed
Confirmed by Maersk: a security incident, unauthorized access, data extraction from a legacy system. Claimed by WhiteArmor: the size of the theft, the ransom amount and the deadline. WhiteArmor also told one outlet that Maersk had not contacted it to negotiate.
Why “legacy system” matters
Acquired companies often keep their own IT for years. An old, separate system can be a weaker point than the main network, which is why Maersk stresses that the incident is isolated.
What is not established
- What data was taken, and whether any is personal: not disclosed.
- When the intrusion began: not stated.
- The 100 GB figure: WhiteArmor’s claim, not verified.
- Whether Maersk will pay or negotiate: not reported.
- Whether the system is LF Logistics’: a researchers’ link, not confirmed by Maersk.
Summary table
| Point | What is stated as of November 17, 2026 | Source |
|---|---|---|
| Maersk statement | November 11, 2026; legacy system from an acquisition | Security Affairs |
| Maersk assessment | No sensitive data disclosed, per findings so far | Reuters via WMBD |
| WhiteArmor claim | About 100 GB | BleepingComputer |
| Ransom demand | $5 million in bitcoin within 30 days | GovInfoSecurity |
| Possible source | LF Logistics, bought in 2022 (researchers’ link) | Cybernews |
FAQ
Did Maersk confirm the theft?
It confirmed unauthorized access and data extraction from a legacy system, and said it found no sign that sensitive data was disclosed.
Is the $5 million demand confirmed?
It is WhiteArmor’s demand, reported by several outlets. Maersk has not commented on it.
Are shipments affected?
Reports say shipments are not interrupted and the incident is contained.
Method and limits
Checked on November 17, 2026. We read BleepingComputer, Security Affairs, GovInfoSecurity, Cybernews and the Reuters text through search excerpts. We did not read Maersk’s notice itself. The request said Maersk confirmed a theft on a legacy system and that WhiteArmor claims 100 GB and $5 million; the first part matches Maersk’s wording, the second is the group’s claim.
Sources
- BleepingComputer: Maersk confirms data breach as WhiteArmor ransomware demands $5 million (verified 2026-11-17)
- Security Affairs: WhiteArmor Demands $5 Million from Maersk, Claims Theft of 100GB of Data (verified 2026-11-17)
- GovInfoSecurity: Maersk Probes Ransomware Claim Tied to Legacy System (verified 2026-11-17)
- Cybernews: Maersk confirms cyberattack after hackers access old IT system (verified 2026-11-17)
- Reuters via WMBD: Maersk investigating IT security incident at legacy system (verified 2026-11-17)
Spotted an error in this article? Report it · Our corrections policy