BreachesZero TrustM&A

Maersk's Breach Came In Through a System It Inherited. Every Acquisition Ships With One.

November 12, 2026 · Brian Deitch

This is my security story of the day, and it's not really about shipping. It's about the system nobody remembers owning.

On November 11, Maersk confirmed that an attacker got into one of its IT systems and pulled data out of it. The detail that jumped out at me: Maersk says the system "was inherited through an earlier acquisition." Not the core booking platform. Not the network that runs the ships. A legacy box that came along with a company it bought.

I've spent a lot of time on M&A integration (I've even done videos on it), and this is the scenario that keeps integration teams up at night.

What Maersk Confirmed

Per Maersk's statement, as quoted by SecurityWeek, SecureWorld and Cybernews:

  • Data was extracted from a legacy system that came with a previous acquisition. Maersk hasn't named which business.
  • Its own security team found it, started investigating and secured the system.
  • Scope, so far: "The incident is isolated to a local system," with no sign of impact on other Maersk systems or on customer and partner systems connected through APIs and EDI.
  • Data, so far: "Our findings so far strongly suggest no sensitive data has been disclosed." Maersk hasn't said what was taken or how much.
  • Operations: no expected disruption. Booking and shipment management are up.
  • Not disclosed yet: when the intrusion happened, how the attacker got in, or whether WhiteArmor is actually behind it. The investigation is ongoing and Maersk says affected parties will be notified if necessary.

What the Attackers Claim

A group calling itself WhiteArmor listed Maersk on its leak site around November 7 and is demanding a ransom. Everything in this section is the attacker's claim. None of it has been independently verified, and Maersk hasn't confirmed it.

  • About 100GB taken from a platform tied to LF Logistics, the contract logistics company Maersk acquired in 2022. SecureWorld and Cybernews also connect it to LF Logistics. Maersk hasn't.
  • Roughly 29,000 driver records, with more than 16,000 plaintext passwords.
  • Over 16,000 staff accounts, 33 of them super-admins.
  • Delivery receipts, inventory records, purchase orders, shipping notices, and mobile device logs with phone numbers, emails and IMEIs.

If even part of that is true, "no sensitive data" and "16,000 plaintext passwords" are going to have an awkward conversation. But I'll wait for the investigation rather than pick a side.

The Real Story: Inherited Risk

Here's how this usually goes. You buy a company. Day one, you connect the networks so people can work. The acquired company's apps, servers and admin accounts come along for the ride. Integration has a two-year plan to migrate everything, and in year two, half the plan quietly becomes "we'll decommission it later."

Four years later, that platform is still running. It still has local accounts. Maybe it still stores passwords in plaintext, because it was built before anyone made it stop. Nobody on the current security team built it, nobody fully owns it, and it might not be in the asset inventory at all.

Credit to Maersk where it's due: by its own account it found the intrusion, contained it, and says it was isolated to a local system. If that holds, it's segmentation doing its job, and that's a much better outcome than the alternative. SecureWorld is careful to call that an informed reading rather than a confirmed fact, and so am I.

I work at Zscaler, so here's my bias in plain view: this is exactly why I push for connecting acquired users to specific applications instead of merging networks. If the acquired platform can't route to the rest of the company, a breach of it stays a breach of it. You get day-one access without inheriting day-one exposure.

What To Do If You're Acquiring (Or Already Did)

  • Inventory everything you bought. Apps, servers, SaaS tenants, admin accounts, API keys. If it's not on a list, it's not getting patched.
  • Don't flatten the networks. Give acquired users access to the apps they need, not a route to everything.
  • Set a kill date for every legacy system, with an owner, and actually check it.
  • Review integration-era credentials. Service accounts and shared admin logins created "temporarily" during the migration are still there. They always are.
  • Hunt for plaintext password storage in anything you didn't build.

What To Do If You're a Maersk Customer, Partner or Driver

  • Treat unexpected messages about the incident with suspicion. Maersk has told customers to verify through their usual Maersk contacts. Breaches are phishing fuel.
  • If you reused a password on any LF Logistics or Maersk-related platform, change it everywhere else you used it. Credential stuffing comes next.
  • Watch for fake delivery and invoice emails. Attackers who claim to have purchase orders and shipping notices can write very convincing ones.

Bottom Line

The breach that gets you is rarely the system you watch every day. It's the one you inherited, meant to retire, and forgot. Every acquisition ships with one. Find yours before someone else does.

Sources: SecurityWeek, SecureWorld, Cybernews, Maersk statement

maerskwhitearmorransomwaredata-breachmergers-and-acquisitionslegacy-systemstechnical-debtcredential-stuffingphishing
All postsDiscuss on LinkedIn