# WhiteArmor demands $5 million from Maersk and its security is called into question

> The extortion group says it holds 100 GB from the OCF/LF Logistics platform. Maersk confirms access to a legacy system and denies any impact on APIs and EDI.
> By José Maldonado · Cybersecurity · 2026-11-13

The well-known shipping company Maersk has admitted that someone accessed one of its systems without permission and extracted data. The Danish shipping line maintains that the affected machine is a local system inherited from an earlier acquisition and that the incident is isolated, with no signs of impact on the rest of its infrastructure or on the API and EDI connections used by customers and partners. It gave no dates, did not identify the system and did not confirm who is behind it.

On the same day, a group called WhiteArmor was keeping the company on its leak site with a demand for $5 million in bitcoin and a 30-day deadline. Its version is far more specific and far less verifiable: some 100 GB extracted from the OCF/LF Logistics platform, with 29,000 driver records, passwords stored in plain text and system staff accounts, as well as signed delivery notes and mobile device records with phone number and IMEI. The group even calculates the ransom based on the revenue of the contract logistics business.

One third confirmed fact and two thirds unverified accusation is the real split in this story. The part Maersk acknowledges fits into three sentences; the part describing the group fills an entire catalogue with uncomfortably precise numbers.

## A legacy system and a figure in the shop window

The group listed Maersk on its leak site on November 7, 2026, before the company spoke publicly. Its [demand for $5 million in bitcoin](https://www.bleepingcomputer.com/news/security/maersk-confirms-data-breach-as-whitearmor-ransomware-demands-5-million/) it grants 30 days to respond and claims to know the specific business it is attacking, a detail that Maersk has not translated into any public confirmation.

The system in question is the OCF/LF Logistics platform, which supports contract logistics and compliance for consumer brands. The [purchase of LF Logistics from Li & Fung in 2022](https://securityaffairs.com/202869/data-breach/whitearmor-demands-5-million-from-maersk-claims-theft-of-100gb-of-data.html) fits the statement's reference to an old system brought in from a previous acquisition, although the shipping company has not wanted to confirm the link and the coincidence remains a reasonable hypothesis.

The figures the group details are uncomfortably precise: 29,000 driver records, of which 16,093 would have passwords in plain text, 16,123 staff accounts, of which 33 would have superadministrator privileges, and 27,842 device records with phone number and hardware identifier. That is the [inventory attributed to the group](https://www.infosecurity-magazine.com/news/maersk-data-breach-extortion-group/)and no party has validated it with a sample of files.

Claim

Who backs it

State

Unauthorized access and data extraction in a legacy local system

Maersk, November 11

Confirmed by the victim

Isolated incident, with no impact on its own systems or on customers' APIs and EDI

Maersk

Maintained without public evidence

100 GB from the OCF/LF Logistics platform

WhiteArmor

Unverified

29,000 driver records with 16,093 passwords in plaintext

WhiteArmor

Unverified

16,123 staff accounts and 33 superadministrators

WhiteArmor

Unverified

27,842 device records with phone, email and IMEI

WhiteArmor

Unverified

Encryptor ready to operate

WhiteArmor claims it is almost finished

No documented use

The table forces the two versions to be read separately. Maersk confirms the what and the where, while the group boasts of figures that no one has counted. Neither party has published a sample of the files.

## What the company is not saying

On the other hand, Maersk's [press release of 11 November](https://www.securityweek.com/maersk-confirms-data-theft-amid-5-million-extortion-attempt/) leaves out three things anyone affected would want to know: when the access occurred, how long it lasted and what exact data was taken. The company says its findings suggest that no sensitive information has been disclosed, a formula that describes what it knows today and not what it may know in three weeks.

That gap has practical consequences. A driver or a haulier who worked for the platform cannot know whether their password is circulating, because the company has not detailed what type of record was compromised. The shipping line also warns that any unexpected communication on this matter should be verified through the usual channel, a warning that points to the classic second wave of these extortion attempts.

The nuance of APIs and EDI deserves its own paragraph. They are the channels through which a customer checks where its container is and through which customs documents are exchanged, and if the incident had touched that layer the notice would be a service-disruption report, not a transparency note.

The logic of the ransom is not that of a run-of-the-mill ransomware attack either. The message on the leak page calculates the price against the contract logistics business and compares it with a revenue bracket. It is a negotiation over reputation, not over the key to decrypt anything, and that difference completely changes who holds the upper hand.

The clock has been running since 7 November, so the 30-day deadline expires in the first week of December. If no one pays and the group carries out its threat, the publication will turn a transparency note into a data protection matter with identifiable headlines.

## WhiteArmor promises an encryptor that does not yet exist

The group presents itself as a specialist in data-theft extortion and admits that its encryptor is almost finished, meaning it does not yet operate as classic ransomware. Without encryption there is no operational pressure on the supply chain, only the threat of publishing files.

Its track record over the past month points to a newcomer with an appetite. The demands attributed to it range from $140,000 to $20 million, and several target the same sector, with names such as J.B. Hunt, Ryder and Echo Global Logistics on the list. A group that attacks logistics again and again does not improvise: it is testing which victim pays first.

WhiteArmor attacks platforms that concentrate third-party data, drivers and hauliers included in the package. The shipping line can rotate its own passwords, but not the identity document of a subcontracted driver, and there the damage becomes expensive to repair.

## The lesson is the inventory, not the ransom

The pattern repeats in every corporate transaction. The acquiring company integrates the billing and email of the acquired team, and leaves the system that manages delivery notes in a corner with its own password, its own patch schedule and a connection to the rest of the network inherited from the integration. No one looks at it again until it appears on a leak page.

At Maersk the episode has a precedent. NotPetya forced the company to reinstall more than 4,000 servers and 45,000 workstations in 2017, with ten days without systems and losses that the company itself put at up to $300 million. That blow rewrote the parent company's security; what is failing now is the edge, the small system that fell outside the corporate radar.

The detail of plaintext passwords is not new either. The [Gnosis Pay breach](https://observatorioblockchain.com/en/cybersecurity/brecha-gnosis-pay-expone-datos-titulares-tarjetas/) exposed cardholders' data through failures in handling sensitive information. The [Iris Ohyama record with 7.7 million people](https://observatorioblockchain.com/en/cybersecurity/brecha-iris-ohyama-7-7-millones-clientes/) shows the same underlying problem in old databases.

The [school's response with 37 machines encrypted](https://observatorioblockchain.com/en/cybersecurity/3am-ransomware-colegio-37-equipos-ayuda-ia/) by the 3AM group adds the other half of the picture, the one that occurs when the incident is already inside and decisions have to be made within hours.

The question that remains is not whether WhiteArmor will publish the data, but how many other legacy platforms are still inside the same network. No company can audit from memory what it bought four years ago, and that gap is exactly the one an extortion group without an encryptor exploits with a 30-day deadline and a round figure. Maersk has four years of integrations to review and a list of customers who will be asking about their data this very week.
