A.P. Moller-Maersk said on 11 November that it had identified an IT security incident involving unauthorised access and data extraction from one of its local legacy systems from a previous acquisition. The shipping group says the incident is isolated to that system.

According to Maersk’s statement, its cyber security team launched a full investigation once it discovered the issue, and that investigation is still running. “Our findings so far strongly suggest no sensitive data has been disclosed,” the company said. Maersk says it has found no indication of impact on other Maersk systems or on customer and partner systems that connect to it through integrations such as APIs and EDI, and it does not expect disruption to bookings. It asks customers to treat unexpected communications about the incident with caution and to verify them through their usual Maersk contact. The statement does not name the legacy system, the acquired business, the attacker or how much data was taken.

In our reading, other security leaders should look at where this happened, in a system inherited through an acquisition that was still running and still holding data. Ask for a list of every legacy system that came with an acquired business, what data each one holds, and who watches its logs today. Partners of any company in this position should expect phishing that cites the incident, which is why Maersk’s advice to verify through a known contact is worth passing to finance and logistics teams now. The pattern resembles Crédit Mutuel Arkéa’s account of attackers reaching it through a service provider’s platform, and our argument to treat any environment holding real data as production applies to inherited systems too.

Source: Maersk: IT security incident, 11 November 2026