Maersk said on 11 November that an attacker gained unauthorised access to one of its local legacy systems, inherited through a previous acquisition, and extracted data from it. A ransomware group calling itself WhiteArmor had already claimed the attack and is demanding $5 million.
Those are two different kinds of statement, kept apart below. What matters for anyone who runs software is where it happened: in a system that arrived with a purchase.
What Maersk has confirmed
The confirmed facts come from a short notice on Maersk's website. Beyond the intrusion itself, Maersk says:
- Its cyber security team found the issue and moved to secure the system, and the investigation continues.
- Its findings so far "strongly suggest no sensitive data has been disclosed".
- The incident is isolated to that one local system, with no sign of impact on other Maersk systems or on the customer and partner systems connected through APIs and EDI (electronic data interchange).
- It does not currently expect disruption for customers.
- Customers should be wary of unexpected messages about the incident and verify them through their usual Maersk contact.
The verb there is disclosed, not taken: the notice confirms extraction and does not say what was extracted. GovInfoSecurity's report renders the line as no sensitive data having been stolen, which is not quite what Maersk wrote.
The notice names neither the acquired company nor the system, and it mentions no group and no demand for money. SecurityWeek points out that Maersk has not said when the intrusion happened or how the attackers got in.
What is only the group's claim
Everything else is unverified and traces back to WhiteArmor, which GovInfoSecurity describes as a newly emerged group, active since 21 October. It listed Maersk on its leak site over the weekend before the notice; SecurityWeek gives the date as 7 November. By BleepingComputer's account, it says it holds about 100 GB of data and gives Maersk 30 days to pay $5 million in bitcoin before it publishes.
The group attributes the data to a platform labelled OCF/LF Logistics, BleepingComputer and Security Affairs report. Maersk did buy LF Logistics, a Hong Kong-based contract logistics company: its own press release dates the completion to 31 August 2022. Whether that is the acquisition the notice means, Maersk has not said, and Security Affairs notes that the link is unconfirmed.
The listing is reported to describe driver records, staff accounts, delivery paperwork and mobile device logs, and to claim that some passwords were stored in plain text. SecurityWeek and Security Affairs both state that none of this has been independently verified. Neither Maersk nor the outlets describe encrypted systems or an outage, only data theft followed by a demand for money.
The two accounts differ on how sensitive the data is, and outsiders cannot yet tell which is closer. Maersk says it will update customers and inform affected parties if its findings call for it.
Why inherited systems deserve suspicion
Nothing in Maersk's notice says when its system was entered. An older case shows why that matters. The UK Information Commissioner's Office (ICO) fined Marriott £18.4 million in October 2020 over an attack on the Starwood systems it had acquired. The penalty notice records that Starwood was compromised in 2014, that Marriott bought it in September 2016 and kept using those systems, and that the attack went undetected until September 2018. Marriott said it had managed only limited due diligence during the takeover, and the regulator made no finding on that. What it penalised came afterwards, including insufficient monitoring of privileged accounts and databases.
Marriott also argued that the system was about to be retired. The regulator rejected that: the shutdown planned for early 2018 had slipped to the end of the year, and monitoring and alerting could have been added relatively quickly in the meantime.
That is the trap as we see it. A bought system is always about to be replaced, so spending on it feels wasted. This is not a finding about Maersk, only what we would assume of any inherited system.
What we would check first
This is our advice, not Maersk's, and it applies whether you are buying a company or taking over a client's old server.
- Write the register. List every system that came with the deal and the data it holds. Give each a named owner and a date by which it meets your standard or is switched off.
- Look for an intruder before you connect anything. Review the acquired side's logs and admin accounts for signs that someone is already inside. Starwood shows the attacker can come with the purchase.
- Reset every credential that predates the deal. API keys and shared admin logins count too. Check how passwords are stored, and put sign-in behind your own identity system with multi-factor authentication.
- Keep it fenced off until it meets your standard. Maersk's most reassuring line is that the incident stayed in one local system. The ICO notice records the same of Starwood, whose systems stayed segregated from the wider Marriott network.
- Send its logs to your own monitoring from the first day. That is how you find out what was taken.
If there is time for only one, we would start with the register. A system nobody owns is a system nobody is watching.