A.P. Moller–Maersk has confirmed that an unauthorized actor accessed and extracted data from a local legacy system inherited through a previous acquisition.

The company disclosed the incident on November 11, 2026. It said its cyber security team launched a full investigation immediately and secured the affected system.

Maersk stated that findings so far strongly suggest no sensitive data has been disclosed, and that the incident is isolated to a local system. The disclosure follows a claim by the WhiteArmor ransomware group, which listed Maersk on its Tor-based data leak site over the weekend.

Shipping Giant Maersk Confirms Cyberattack

The group demanded USD 5,000,000 in Bitcoin and set a 30-day deadline to contact them and pay. WhiteArmor claims to hold roughly 100 GB of data from the OCF/LF Logistics platform, which LF Logistics acquired from the Li & Fung Group in 2022.

Maersk has not linked the incident to WhiteArmor or confirmed any ransom demand. According to the attackers, the stolen dataset includes nearly 30,000 driver records, plaintext credentials, 33 SUPER_ADMIN accounts, signed delivery receipts, inventory rows, purchase orders and advance shipping notices (ASNs).

The group also claims 27,842 mobile device logs containing phone numbers, email addresses and IMEI identifiers. Other reports cite more than 16,000 driver passwords.

None of these claims have been independently verified, and Maersk’s statement does not confirm them. Maersk has not disclosed the intrusion date, the initial access vector, or the volume and type of exfiltrated data.

The presence of plaintext credentials and SUPER_ADMIN accounts would matter operationally. Such privileged identities could allow an adversary to manipulate tenant data, create or delete orders, and pivot through trusted integrations.

Attackers often chain credential harvesting with password spraying and bulk database extraction, as seen when attackers staged ZIP archives of 18,566 records containing plaintext passwords on a compromised government WordPress site.

Legacy platforms inherited through mergers frequently lack modern identity controls, centralized logging and network segmentation, which extends dwell time before detection.

Maersk says it found no indication of impact on other Maersk systems or on customer and partner systems connected through APIs and EDI. That assurance is central, because EDI and API trust relationships can serve as lateral movement paths between logistics providers and their clients.

Containment of the legacy environment therefore requires credential rotation, session token revocation, and review of service accounts and API keys that bridge the acquired platform and the core network. The incident also reflects the broader shift toward extortion built on data theft rather than encryption.

Operators increasingly replace commodity utilities with proprietary tooling, as when Trigona affiliates deployed a custom uploader with parallel streams and connection rotation to evade network monitoring.

Others abuse trusted cloud utilities, and AzCopy has been used to move stolen data to Azure Storage over HTTPS, blending exfiltration traffic with legitimate business activity. Defenders in logistics and supply-chain environments should treat acquired platforms as high-risk assets.

Priorities include enforcing phishing-resistant multi-factor authentication on administrative identities, eliminating plaintext credential storage, restricting outbound traffic from legacy hosts, and hunting for anomalous bulk reads and archive staging.

Organizations can also monitor for unauthorized remote access tools and unusual kernel driver installations that precede data theft.

Maersk has advised customers to treat unexpected communications about the incident with caution and to verify them through their usual Maersk contact, since extortion campaigns often escalate into targeted phishing against partners.

Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team