Secretus logo
newsoperation-endgamecastleratstealc

Operation Endgame: Stolen Passwords Still Need Replacing After a Takedown

Police disrupted Gootloader, CastleRAT and StealC. Recover accounts from a clean device, verify breach notices and keep replacement secrets out of old channels.

·6 min read·Secretus Editorial

A police takedown can interrupt the malware infrastructure. It cannot make every copied password stop working. On 12 November, Dutch police announced an international Operation Endgame action against Gootloader, CastleRAT and StealC. They reported securing more than 6.4 million stolen personal data items and sharing victim information with notification partners. That is a count of recovered data, not 6.4 million unique people or confirmed valid passwords.

The useful next step for a person or business receiving a warning is account recovery from a trusted device. A replacement password entered on a machine that still steals credentials can become another stolen password.

What the operation confirms

The Dutch announcement confirms action against all three malware operations. The US Department of Justice separately announced removal of Gootloader from more than 100 servers, including compromised WordPress sites. SecurityWeek, The Hacker News and The Record provide independent reporting on the disruption and victim-notification work.

Have I Been Pwned's CastleRAT record, added on 13 November, says Europol supplied addresses associated with infections. Its metadata lists 179,745 accounts and the data classes email addresses and passwords. This is one dataset within the wider action. The entry does not establish that each address represents a different person or that every recovered password remains valid.

Dutch police explicitly warn that criminals may retain stolen login data after seizure. Their FAQ also explains that malware left on a computer may capture a changed password. Neither the announcement nor a breach-check result establishes that a particular device is now clean.

Check a notification without handing over another secret

The Dutch police offer Check your hackfor checking an email address against seized datasets. Type the official address into your browser yourself. The service requests an email address, not an account password. After you initiate a check, a positive match produces an email; no email means the address was not found in the checked data, rather than a general assurance that it was never exposed.

The police FAQ warns about fraudulent messages asking recipients to check the dataset through a link. Do not send a support agent your password, MFA code or recovery material to prove you own an affected account. For a work address, ask your security team to coordinate the response through its established process. A colleague forwarding a screenshot of a warning is a reason to investigate, not a reason to distribute credentials to everyone copied on the message.

Recover access in an order that protects the replacements

The following is a practical response sequence, rather than a claim about what happened on every infected computer. Adapt it to the accounts and devices actually involved.

  1. Use a trusted device. Stop using a suspected machine for password changes or credential transfers. For a business device, let the response team preserve evidence and decide how to investigate or rebuild it.
  2. Secure the recovery mailbox. From the trusted device, review its sessions, recovery contacts and unexpected forwarding or delegated access. Replace exposed credentials and remove access you do not recognize through the provider's supported controls.
  3. Work through the accounts reachable from that device. Start with identity, password-manager, financial and administrator access. Include work tokens, SSH keys and service credentials if the device held them; do not assume a personal email warning defines the whole exposure.
  4. Handle active access separately. Use each provider's options to sign out other sessions and revoke tokens. Check MFA enrollments and recovery methods. Ask what a password reset actually invalidates rather than assuming it closes every route.
  5. Verify recovery. Confirm the intended user can sign in, the retired credentials are rejected and recovery contacts are correct. Record the result, not the passwords or backup codes.

When a team has to exchange replacement access

An incident often turns into a rushed handover: an administrator issues temporary access, a contractor restores an integration, or a customer needs a new service credential. Establish who is receiving it and which device they will use before sending the value. A familiar email account may itself be part of the recovery, so verify an unexpected urgent request through a previously established contact route.

Send one recipient the access required for the task. Give temporary access an owner and an end time. Keep credentials out of screenshots and incident transcripts, and avoid sending an entire configuration export when only one field is needed. For a service account, rotate at the accepting service and update its legitimate consumers; changing the copy in a local file is not enough.

Use a one-time transfer after the endpoint is trusted

Secretus provides browser-side encryption for a text secret and a transfer link that becomes invalid after expiry or first successful access. It can help a verified administrator hand a replacement credential to the right person without leaving the value in the incident channel. The receiving device still has to be trusted. A one-time link cannot remove malware, revoke an account session or invalidate credentials copied before the takedown.

Sources