Shipping and logistics company A.P. Moller-Maersk is investigating an IT security incident involving the possible theft of data from a legacy system it inherited through an earlier acquisition, The Register reported Wednesday. Maersk says it expects no impact on operations, but the case shows how systems carried over from acquired businesses can remain a point of exposure long after a deal closes.

What Happened

In a statement dated Wednesday and quoted by The Register, Maersk said it was investigating "an IT security incident" involving potential data theft from a single local system that came "from a previous acquisition." The company said it opened an investigation immediately and secured the affected system. The statement, as reported, did not name the acquired business or describe what kind of data the system held.

Maersk said its early findings "strongly suggest no sensitive data has been disclosed." It said it sees no indication that the incident reached other Maersk systems or the customer and partner systems connected to it through APIs and EDI. APIs, or application programming interfaces, are software links that let companies' systems exchange data automatically; electronic data interchange (EDI) is a long-standing standard for sending bookings, invoices and shipping documents between trading partners.

RelatedMaersk Confirms Data Theft From Inherited System as WhiteArmor Gang Demands $5 Million

The company said it does not expect any operational impact and that customers can keep using its platforms to manage shipments as usual, with updates to follow. It urged customers to treat with caution any unexpected messages that claim to relate to the incident and to verify them through their usual Maersk contact.

The Register's report did not mention any claim of responsibility or any notification to regulators. Maersk has not said who was behind the incident.

Why It Matters

For U.S. importers, exporters and freight forwarders that book through Maersk, the company's account points to limited direct disruption. The more immediate risk is fraud. Maersk's own warning about unexpected messages reflects a common pattern after a publicized incident, when criminals pose as the affected company to request payments or credentials. Finance and logistics teams should confirm any change to payment details or document requests through a known contact rather than through the message itself.

For boards and deal teams, the bigger lesson is about mergers and acquisitions. Bought companies often arrive with their own servers, software and user accounts, and folding them into the parent's systems can take years. Until then, such systems may sit outside the parent's routine monitoring, patching and access controls. Maersk's description of the affected system as local and isolated suggests its separation from the main network helped contain the problem, if the company's early findings hold.

Security due diligence before a deal, and a clear inventory afterward of every inherited system with an owner and a retirement date, are the controls that address this risk. The concern is not limited to companies: The Primary Wire reported in October that the chair of a British parliamentary watchdog warned that aging government IT carries significant cyber risk.

Context: The NotPetya Precedent

Maersk has been through a far worse attack. In 2017 it was hit by NotPetya, destructive "wiper" malware that erased data while posing as ransomware. Western intelligence agencies attributed the attack to Russia's Sandworm group, which is believed to be part of the GRU, Russia's military intelligence service, The Register noted.

Maersk said at the time it expected the attack to cost about $300 million. Its then-chair, Jim Hagemann Snabe, told the World Economic Forum in 2018 that the rebuild involved 4,000 new servers, 45,000 new PCs and 2,500 applications and was finished in 10 days, according to The Register. By Maersk's account so far, this week's incident is far narrower.

What to Watch

Maersk has promised updates. The open questions are what data the legacy system held and whether any was actually taken, which acquired business it came from, and who was responsible. Watch also for any claim by a criminal group, for notices to customers or data-protection regulators if personal data proves to be involved, and for any revision of Maersk's view that operations and connected customer systems were untouched.