Skip to Content
Security

The System You Forgot You Owned: Securing Inherited IT After an Acquisition

Maersk says attackers took data from a system it inherited through an acquisition. Old, forgotten systems are a common way in. A checklist for finding and fixing them.

Nexgenex Labs ResearchArticles
PublishedReading time8 min read
The System You Forgot You Owned: Securing Inherited IT After an Acquisition

Photo: H. Zell · CC BY-SA 3.0 · Wikimedia Commons

What happened at Maersk

On 11 November 2026, shipping giant Maersk confirmed that hackers extracted data from one of its IT systems that was inherited through an earlier acquisition. Maersk said the incident was isolated to a local system, that its findings so far strongly suggest no sensitive data was disclosed, and that it does not expect disruption to customer operations. (Our news report has the details.)

The WhiteArmor ransomware group claims to have taken about 100 GB from a platform linked to LF Logistics, which Maersk acquired in 2022, and demanded $5 million. Those claims, including plaintext driver passwords and staff accounts, are not independently verified, and Maersk has not confirmed the group's involvement.

Whatever the final details, the pattern is familiar: the weak point was not the core platform but a system that came along with a deal.

Summary graphic: The System You Forgot You Owned: Securing Inherited IT After an Acquisition
In one image

Save it. Share it with your team.

The short version of this post, ready for your Instagram Story or feed.

Why inherited systems are risky

  • Nobody owns them. The original team has moved on, and the new parent hasn't fully taken charge.
  • They are off the map. They may not be in your asset inventory, monitoring or patch cycle.
  • Old security habits survive. Shared admin accounts, weak or plaintext passwords and unpatched software are common.
  • They are still connected. Integration work links them to newer systems, giving an attacker a path in.

The same is true without an acquisition: a pilot app nobody turned off, an old vendor portal, a test server. We saw it earlier this year in the Data Cymru 'Password1' case.

Checklist: before and after you acquire (or inherit) IT

  • During due diligence, get an inventory of every system, domain, cloud account and admin account in the target business.
  • Run an external attack-surface scan of the target's domains and IP ranges before closing.
  • On day one, reset all admin and shared credentials and turn on MFA everywhere.
  • Bring every inherited system into your monitoring, logging and patching within a fixed deadline, for example 90 days.
  • Assign a named owner for each system, with a decision: integrate, rebuild or retire.
  • Retire what you don't need. Archive the data you must keep, then switch the system off. A system that's off can't be breached.
  • Check for plaintext or weakly hashed passwords and fix storage before anything else.
  • Segment inherited systems from your core network until they meet your standards.

For smaller businesses too

You don't need to be Maersk for this to apply. If you've changed IT vendors, rebuilt your website or bought another business, there is probably an old admin panel, hosting account or database still running somewhere. An afternoon spent finding it is cheap insurance.

How Nexgenex Labs can help

We help businesses inventory, secure, migrate and retire legacy systems, and build modern replacements. Our logistics and supply chain work often starts exactly here. Get in touch for an attack-surface review.

Have a project like this in mind?

Talk To Our Team →
Research Digest

Join theDiscourse.

Become part of our global research community. Weekly technical deep-dives transmitted to your professional inbox.