A.P. Moller-Maersk has confirmed that a hacker stole data from a legacy IT system it inherited through an earlier acquisition, and an extortion group calling itself WhiteArmor is demanding $5 million in bitcoin to keep the data private, BleepingComputer reported Wednesday. The shipping and logistics company still expects no disruption for customers, but the case has moved from a possible theft to a confirmed one with a ransom deadline attached.

The Primary Wire reported earlier Wednesday, citing The Register, that Maersk was investigating possible data theft from the system.

What Happened

In its updated statement, as reported by BleepingComputer, Maersk said current evidence indicates that “no sensitive data has been disclosed” and that the incident is isolated to a local system. It found no sign of impact on other Maersk systems or on customer and partner systems that connect to it through APIs and EDI, the automated links trading partners use to exchange bookings and shipping documents.

RelatedU.S. Moves to Seize $1.2 Billion From Binance Theft and Disrupts North Korean Fake-Meeting Scheme

Maersk said customers can keep booking and managing shipments as usual and that it will notify them as more relevant information becomes available. It has not named the affected system, said what types of data were taken or disclosed when the intrusion happened. BleepingComputer said Maersk had not answered its follow-up questions by publication.

WhiteArmor claimed the attack over the weekend and listed Maersk on its data leak site, according to BleepingComputer. The group says it holds about 100 GB taken from the OCF/LF Logistics platform, originally developed by LF Logistics, the contract-logistics business Maersk bought from the Li & Fung Group in 2022. Maersk has not named the acquired business or confirmed WhiteArmor’s involvement.

The group claims the data includes nearly 30,000 driver records, plaintext passwords, 33 top-level administrator accounts, signed delivery receipts, purchase orders, advance shipping notices and 27,842 mobile device logs containing phone numbers, email addresses and handset identifiers. None of those claims has been independently verified. WhiteArmor gave Maersk 30 days from the listing to pay and justified the amount by likening it to roughly four hours of the logistics business’s earnings.

Why It Matters

The two accounts are far apart. Maersk says early evidence points to no sensitive data being disclosed; WhiteArmor describes credentials and personal contact details for drivers and device users. Until Maersk says what the system held, partners cannot judge their exposure. If personal data proves to be involved, notification duties to individuals and regulators could follow.

The most immediate risk for U.S. importers, brands and carriers that work with Maersk is fraud. Stolen contact lists and account details help criminals write convincing messages that pose as a trusted partner. Maersk itself urged customers to treat unexpected communications about the incident with caution and to verify them through their usual Maersk contact. Security teams should also watch for login attempts that reuse passwords from the affected platform, since the group claims some were stored without protection.

For boards and deal teams, the case underlines a familiar risk: systems from acquired companies that keep running outside the parent’s usual monitoring and access controls. Maersk’s account suggests that separation helped contain the intrusion, but it did not prevent data from leaving.

Context

Maersk has recovered from far worse. BleepingComputer recalled that the 2017 NotPetya attack forced the company to reinstall more than 4,000 servers and 45,000 workstations, left it without IT for 10 days and caused damages of up to $300 million.

What to Watch

  • Whether Maersk confirms which acquired business and what kinds of data were involved, and whether it notifies drivers, staff or regulators.
  • Whether WhiteArmor publishes data as its 30-day window, counted from the weekend listing, runs out in early December.
  • Any change to Maersk’s view that other systems and customer connections were untouched.