Maersk said data was extracted from a legacy system
A.P. Moller – Maersk said it has identified an information-security incident involving unauthorized access and data extraction from a local legacy system inherited from a previous acquisition. The company's advisory is dated November 11, 2026, and the page's publication timestamp is 10:25 a.m. UTC, which is 5:25 AM ET. This article summarizes that official notice and contemporaneous reporting. It is not an independent forensic review of Maersk systems.
Real, reported: based on the public sources cited below. Nothing added or dramatized. Sources checked November 12, 2026, at 7:18 AM ET (EST). Descriptions of scope and impact remain Maersk's published account. Claims attributed to the group SecurityWeek identifies as WhiteArmor are alleged and have not been confirmed by Maersk in the notice we cite.
What Maersk has confirmed
In the November 11 advisory, Maersk wrote: "A.P. Moller – Maersk has identified an IT security incident involving unauthorised access and data extraction from one of our local legacy systems from a previous acquisition." It said that once its cyber-security team discovered the issue, "a full investigation was immediately launched and remains ongoing, with swift action being taken to secure the affected system."
On what was taken, Maersk was more limited. It said: "Our findings so far strongly suggest no sensitive data has been disclosed." It also said: "The incident is isolated to a local system, and we have found no indication that there has been any impact on other Maersk systems or customer and partner systems that connect to Maersk through integrations such as APIs and EDI." The company said it does not anticipate disruption to customer operations at this time, and that customers can continue to use Maersk platforms to book and manage shipments as usual.
Maersk did not name the acquired business, the affected platform, the types of records involved, when the intrusion began, or how access was obtained. It said it will keep customers updated as more relevant information becomes available, and that it will inform affected parties if further findings require it. The advisory also warned people to "treat any unexpected communications claiming to relate to this matter with caution and verify them through your usual Maersk contact."
How other outlets have described the same notice
A Reuters dispatch posted at 5:48 AM ET on November 11, which we opened on Yahoo Finance, reported from Copenhagen that the Danish shipping company said it was investigating an IT security incident involving unauthorized access and data extraction from one of its local legacy systems. Reuters likewise reported Maersk's statement that findings so far strongly suggested no sensitive data had been disclosed, that the incident was isolated to a local system, and that the company did not anticipate disruption to customer operations.
The Reuters item we opened is a short bulletin. It is datelined Copenhagen, November 11, and lists Louise Rasmussen as the reporter, with editing credited to Terje Solsvik and Stine Jacobsen. It does not discuss any ransomware group, ransom demand, or named logistics platform. Those details appear only in later coverage, such as SecurityWeek, and should not be read back into the Reuters bulletin or into Maersk's own advisory.
Maersk closed the advisory by stressing that cyber security "remains a constant, ongoing priority" and that it has "rigorous processes in place to identify and prevent incidents and minimise customer impact." That is the company's description of its program, not an audited finding. The investigation, Maersk said, "remains ongoing." The advisory ends: "Thank you for your patience as we continue to investigate the incident." Until the company publishes a further notice, there is no official public list of affected people, no official confirmation of the data types involved, and no official attribution to a named threat group.
SecurityWeek, in an article by Eduard Kovacs time-stamped 3:38 AM ET on November 12, also summarized the November 11 statement, including Maersk's line that findings so far "strongly suggest no sensitive data has been disclosed." SecurityWeek wrote that Maersk has not identified the acquired business, the types of data taken, when the intrusion occurred, or how attackers gained access.
Alleged extortion claims that Maersk has not confirmed
SecurityWeek reported that the disclosure followed a claim by the WhiteArmor ransomware group, which it said listed Maersk on a leak site on November 7 and threatened to publish stolen information unless a $5 million ransom is paid. According to SecurityWeek, WhiteArmor claims to have obtained about 100GB of data from a platform associated with LF Logistics, a logistics company SecurityWeek said Maersk acquired in 2022. SecurityWeek wrote that the alleged haul includes roughly 29,000 driver records, of which 16,093 contain plaintext passwords, and 16,123 staff accounts, including 33 with superadministrator privileges, plus information on delivery recipients, signed delivery receipts, inventory records, purchase orders and shipping notices, and more than 27,000 mobile-device logs. Those figures and categories come from the group's alleged claims as reported by SecurityWeek. They have not been independently verified here, and Maersk's advisory does not confirm the group's involvement, the platform name, or those data types.
SecurityWeek also quoted the group's alleged extortion message as saying: "You have 30 days to contact us and pay USD 5,000,000 in bitcoin." A ransom demand, a bitcoin payment, or a deadline is not a reason to pay. Maersk has not, in the advisory we opened, confirmed that demand or told customers to pay anyone.
SecurityWeek stated that the group's claims have not been independently verified, and that Maersk has not confirmed WhiteArmor's involvement. We use the same limit: the only confirmed facts in Maersk's own notice are unauthorized access and data extraction from one local legacy system, an ongoing investigation, and the company's present assessment that the incident appears isolated and that no sensitive data has been disclosed.
Our advice (general guidance)
If you are a Maersk customer, partner, driver, or contractor, rely on the company's official advisory and on messages you can check through a contact method you already use, not on unexpected emails, texts, or payment demands that mention this incident. Maersk itself asked people to treat unexpected communications about the matter with caution. Do not send money, cryptocurrency, or additional personal data to anyone who claims to represent Maersk or to be able to "unlock" records.
A company statement that findings "strongly suggest" no sensitive data has been disclosed is not the same as a finished investigation. Watch official updates. If you later receive a notice that your information was involved, use the instructions in that notice and, for U.S. readers, review the steps on IdentityTheft.gov and the FTC's scam guidance. Readers in other countries can use their local consumer or data-protection agency. You can also contact us if you want to share a suspicious message for educational review.
These are editorial precautions, not individualized legal, financial or security advice.
Sources
- A.P. Moller – Maersk: IT security incident (published Nov 11, 2026, 5:25 AM ET)
- Reuters, via Yahoo Finance: Shipping firm Maersk investigates IT security incident (Nov 11, 2026, 5:48 AM ET)
- SecurityWeek: Maersk Confirms Data Theft Amid $5 Million Extortion Attempt (Nov 12, 2026, 3:38 AM ET)
- FTC IdentityTheft.gov (U.S. recovery resource)
Published November 12, 2026 by FraudMeNot Team. Label: Real, reported.