Operation Endgame took StealC down again

Law enforcement took down the infrastructure behind StealC for the second time this year. Learn why takedowns don’t remove the exposure, and what security leaders should check this week.

Key takeaways

  • A takedown stops new infections. It doesn’t take back what was already stolen.
  • StealC was disrupted in June and rebuilt. Expect the same pattern again.
  • Stolen credentials and session cookies keep their value until someone revokes them.
  • The useful question isn’t whether the malware is gone. It’s whether your organization’s access is sitting in a log somewhere.
Law enforcement took down the infrastructure behind StealC for the second time this year.

Between 9 and 11 November, Europol and partners from nine countries took down the infrastructure behind three malware operations: Gootloader, CastleRAT and StealC. They seized 235 servers and 257 domains. They also recovered around 6.4 million stolen credentials from more than 40,000 victims.

For security leaders, the takedown raises a narrower and more useful question. Not whether these malware families are gone, but whether any of those 6.4 million credentials belong to your employees, contractors or customers. And what else was taken from the same machines before the servers went dark.

Takedowns disrupt the supply, not the stock

Operation Endgame has been effective. It has hit loaders, botnets and infostealers repeatedly since 2024, and each action raises the cost of running a criminal service.

StealC shows the limit of that approach. In June, the same operation took down 326 servers and 142 domains tied to StealC and Amadey, and recovered around 27 million credentials. According to Germany’s BKA, the operators then rebuilt their infrastructure. Five months later, investigators took it down again.

That pattern matters more than any single takedown. Infostealer operators sell a service. When the infrastructure falls, customers move to the next provider or wait for the rebuild.

The logs they already collected don’t disappear either. By the time servers are seized, most of that data has been sold, shared or copied into other collections. A credential stolen in September is just as usable in December if no one has rotated it.

The takedown ends one supply line. The exposure it created is still yours to manage.

Three tools, one attack chain

The three operations targeted in November aren’t separate threats. They’re stages of the same process, and each one feeds the next.

ToolWhat it does in the attackWhat it leaves behind after a takedown
GootloaderGets the first foothold, often through fake legal documents in search results.Compromised machines that may already have been handed to other operators.
StealCSteals passwords, session cookies, crypto wallets and other data from infected devices.Logs of credentials and cookies that are still being sold and reused.
CastleRATGives attackers persistent remote control of a machine.Access that may already have been used to move deeper into a network.

The infostealer sits in the middle of that chain. It turns one infected laptop into a set of working logins: email, VPN, SaaS tools, cloud consoles. In the wrong hands, that is often where ransomware begins.

That’s why the credential count is the number to watch. The servers are offline. The access they collected may not be.

The right questions are about exposure, not malware

Most organizations will never know whether one of their devices was infected by StealC. Many of those devices aren’t theirs to begin with: personal laptops, contractor machines, a partner’s shared workstation.

What they can find out is whether their access is circulating. That moves the conversation away from the headline and toward the questions that change risk:

  • Are any corporate email addresses or domains in recent infostealer logs?
  • Do those logs include session cookies that could bypass MFA?
  • Which applications do the exposed credentials open: VPN, SSO, cloud consoles, code repositories?
  • Are the affected users employees, contractors or third-party suppliers?
  • How quickly can we revoke sessions and force a reset once exposure is confirmed?
  • Would we know if the same credentials showed up again next month?

These questions don’t depend on which malware family did the stealing. They depend on visibility outside the perimeter, and on how fast the team can act once something appears.

A takedown is a moment, not a fix

Operation Endgame deserves credit. Coordinated action across nine countries makes cybercrime slower, more expensive and riskier for the people running it. But a takedown is something that happens to criminals. It doesn’t happen to the stolen data, and it doesn’t revoke a single session.

Be prepared by reaching out to our team.

Über den Autor