The biggest threat to critical infrastructure isn’t sophisticated malware it’s the password you forgot to rotate.

This week I read Hudson Rock’s findings and had the same reaction I’ve had in too many incident war rooms: we keep preparing for the complex attack, and we keep getting hurt by the basic one.

A single actor operating as Zestix / Sentap accessed roughly 50 global enterprises across aviation, robotics, utilities, government infrastructure, telecoms, and defense. The data now sits on dark web forums.

No zero-days. No novel exploits.

Just valid usernames and passwords harvested by commodity infostealers and used against organizations that failed to enforce MFA, rotate credentials, or invalidate sessions.

Some of those credentials were years old.

They still worked.


This is not “a breach.” It’s a governance gap.

When a credential harvested in 2021 can still unlock a system in 2026, the failure isn’t your endpoint stack.

It’s governance.

Because someone, somewhere, made three silent decisions and never revisited them:

Attackers have adapted to the way we manage identity and suppliers:

They don’t need to be faster than us.

They just need us to forget and stay forgotten.


Article content

Who got hit and why it matters

These were not obscure startups. These were enterprises holding critical infrastructure artifacts the kind of material that turns cyber risk into physical risk.

Here’s the part leaders miss:

The target isn’t always the utility, airline, or rail operator.

The target is the ecosystem that holds the same crown jewels with weaker controls.


Article content

The playbook is painfully simple

I’ve seen this pattern repeat across regions and sectors because it exploits the same human and operational realities.

  1. A user gets hit with commodity malware (RedLine, Lumma, Vidar class).
  2. Credentials are pulled from browsers, cached sessions, password stores.
  3. Logs are aggregated and sold.
  4. Months sometimes years later, an actor uses still-valid access.
  5. Data leaves through the front door.

The tragedy isn’t sophistication.

It’s banality.


Article content

Why your perimeter no longer matters

Your “crown jewels” rarely live only inside your perimeter.

They live in:

So when a supplier is compromised, your SOC can be perfect and still irrelevant.

Because the data exits through a door you don’t control.

That’s not “third-party risk” in theory.

That’s operational dependence in practice.


Article content

The exposure is wider than this one actor

Hudson Rock’s broader dataset suggests credential exposure across thousands of organizations including major brands and government-linked entities.

That matters because Zestix behaves like an initial access broker: access is harvested, packaged, and sold to whoever wants to take the next step.

Which means today’s “minor credential leak” becomes tomorrow’s ransomware, espionage, or disruption campaign.


Article content

What I want boards and CISOs to demand now

Not a new framework. Not a new dashboard.

A few non-negotiables executed brutally well:

1) MFA everywhere, no exceptions. If a vendor can’t support MFA, they can’t hold your sensitive data.

2) Credential age is a risk metric. Know how old service accounts and contractor credentials are. Rotate aggressively.

3) Inventory where critical data actually lives. Engineering files, SCADA documentation, infrastructure maps which vendors hold what?

4) Monitor infostealer exposure. Assume your organization is already in stealer logs. Find out before adversaries do.

5) Invalidate sessions like you mean it. A credential harvested three years ago should not work today ever.


Article content

The takeaway I keep repeating

In 2026, attackers aren’t breaking down doors.

They’re walking through the ones we forgot to lock.

If your critical infrastructure data sits in a vendor’s cloud portal protected only by a password, you are one infostealer infection away from a headline.

Question for leaders: what third-party access points in your ecosystem would fail this test today?

Leave a Reply

Your email address will not be published. Required fields are marked *