Join our Newsletter — 33% off our NHI Course
Home› Guides› Cybercrime Law Enforcement Takedowns Guide: Cronos, Endgame and…
Guide Threat Intelligence & Threat Actors

Cybercrime Law Enforcement Takedowns Guide: Cronos, Endgame and What Changes for Defenders

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

A law enforcement takedown can remove a botnet from your network overnight, hand you a decryption key, or tell you that you were compromised months ago, and most organisations have no process for any of those outcomes. Since 2021, coordinated operations led by the FBI, the UK National Crime Agency (NCA), Europol, Eurojust and national police forces have disrupted Emotet, Hive, QakBot, LockBit, Lumma Stealer, PlugX and a long list of droppers under Operation Endgame. This guide explains the techniques these operations use, what each kind of action does and does not fix on victim systems, how decryptors and victim notifications reach organisations, and how to turn a takedown announcement into concrete defensive work. It is written for incident responders, threat intelligence teams and security leaders. The Cybercrime Ecosystem Guide covers the criminal market itself; this page is about the response to its disruption.

Key takeaways

  • Takedowns disrupt, they rarely clean. DOJ stated the 2021 Emotet file and the 2023 QakBot uninstaller did not remove other malware already installed, so every notified organisation still needs its own investigation.
  • Seized infrastructure produces keys and victim lists. The NCA obtained more than 1,000 LockBit decryption keys in Operation Cronos, and the FBI gave more than 1,300 Hive keys to victims, which is why reporting incidents to law enforcement can pay back directly.
  • Notifications arrive through many channels. Operation Endgame used Have I Been Pwned, DOJ cited Shadowserver and Microsoft's Digital Crimes Unit, and the NCA contacted UK victims directly. Make sure each channel reaches someone who will act.
  • Markets regroup. Operation Endgame's own later phases target successor groups that re-emerged after the May 2024 action, and the QakBot leader allegedly moved to spam bomb attacks after 2023. Plan for the successor, not the end.
  • Payment does not buy deletion. The NCA found data on LockBit systems belonging to victims who had already paid, which is evidence for boards weighing ransom decisions.

The takedown toolkit

Operations combine legal and technical actions. Each one has a different effect on victim organisations.

ActionWhat happensExampleWhat it means for your systems
Server and domain seizureInfrastructure taken offline or redirected to law enforcement sinkholesLumma: about 2,300 domains actioned, over 1,300 seized by or transferred to Microsoft and redirected to sinkholes (Microsoft, May 2025)Infected machines lose their C2, and sinkhole logs reveal who is infected.
Botnet uninstall or neutralisationLaw enforcement uses the botnet's own update or command path to push a removal or blocking fileQakBot 2023: FBI-redirected traffic delivered an uninstaller to infected computers (DOJ); Emotet 2021: replacement file cut communication (DOJ)The named malware stops, other malware remains.
Court-authorised deletion commandMalware's built-in self-delete command sent to infectionsPlugX, January 2025: about 4,258 US computers, nine warrants, French partners and Sekoia.io (DOJ)The implant is removed; the access route and any other tools remain.
Covert infiltration and key captureInvestigators sit inside the criminal infrastructure and collect keys before actingHive: FBI inside from late July 2022, over 1,300 keys provided, over 130 million US dollars in ransom demands averted (DOJ)Victims may receive keys before or after the public announcement.
Platform takeoverAdmin panel and leak site seized and used to message affiliates and the publicOperation Cronos: NCA took over LockBit's administration environment and leak site, obtained source code and more than 1,000 keys (NCA, February 2024)Leak listings may be replaced by law enforcement notices; victim data may be in evidence.
Arrests, indictments and sanctionsCharges, warrants and financial sanctions against individualsQakBot leader indicted May 2025 (DOJ); OFAC designated two LockBit actors (DOJ, February 2024)Sanctions affect whether ransom payments to named people are lawful. See the Ransomware Payments and Sanctions Guide.
Cryptocurrency seizureProceeds frozen or forfeitedQakBot: about 8.6 million US dollars in 2023 and over 24 million US dollars covered by the 2025 forfeiture complaint (DOJ); Cronos: over 200 crypto accounts frozen (NCA)Rarely returned to individual victims quickly; do not plan recovery around it.
Credential recovery and notificationStolen credentials recovered from seized servers and passed to victimsEndgame June 2026: 27 million stolen credentials recovered, notification through Have I Been PwnedCheck exposure services and reset affected accounts and sessions.

Major operations at a glance

DateOperation or targetLead and partners (as stated)Headline results
January 2021EmotetUS, Canada, France, Germany, the Netherlands, UK; Lithuania, Sweden and Ukraine assistingAbout 1.6 million infected computers identified; replacement file cut the botnet off; Dutch police email check service.
January 2023Hive ransomwareFBI with German and Dutch law enforcementOver 1,300 keys; over 130 million US dollars in demands averted; servers and sites seized.
August 2023QakBotFBI with France, Germany, the Netherlands, UK, Romania, Latvia, Eurojust and EuropolOver 700,000 infections identified; uninstaller pushed; about 8.6 million US dollars seized.
February 2024Operation Cronos (LockBit)NCA and FBI with partners from nine other countries, Europol and EurojustAdmin environment and leak site taken over; source code; over 1,000 keys; Stealbit seized in three countries; 28 affiliate servers down; two arrests; over 200 crypto accounts frozen.
May 2024Operation Endgame phase oneCoordinated from EuropolIcedID, SystemBC, Pikabot, Smokeloader, Bumblebee and Trickbot; over 100 servers down; four arrests.
January 2025PlugX deletionFBI and DOJ with French prosecutors, Gendarmerie C3N and Sekoia.ioAbout 4,258 US computers cleaned of one PlugX version.
May 2025Endgame phase and Lumma actionEuropol and Eurojust; Microsoft DCU with DOJ, EC3 and JC3About 300 servers and 650 domains, warrants for 20 targets, 3.5 million euros seized (Endgame); about 2,300 Lumma domains actioned.
November 2025EndgameEuropol1,025 servers down across Rhadamanthys, VenomRAT and Elysium; one arrest in Greece.
June 2026Endgame against SocGholish, Amadey and StealCDutch NHCTU, RCMP, FBI, BKA, Europol, Eurojust, Microsoft and partners326 servers and 142 domains; 14,971 infected websites remediated; 27 million credentials recovered.

Figures are as stated in each agency's announcement and cover different scopes, so do not add them together. For family background, see the Emotet Malware Guide, QakBot Malware Guide and LockBit Threat Actor Profile.

What changes for defenders after a takedown

Time after announcementWhat usually happensWhat to do
First 72 hoursIndicators, sinkhole data and advisories published; victim notifications startSweep logs for the published indicators back at least 90 days; check every notification channel; brief the SOC.
First weeksDecryption options appear for some victims; criminals message affiliates and customers; lookalike scam "recovery" offers circulateContact the official portal if encrypted (for LockBit, DOJ pointed victims to lockbitvictims.ic3.gov); ignore unofficial recovery offers.
MonthsCustomers move to other families; operators rebrand or regroupUpdate detections to the successor families named in vendor and ATT&CK reporting, for example Pikabot activity after QakBot (ATT&CK C0037).
Long termIndictments, sanctions and court documents add detailReview sanctions lists before any ransom decision and use court documents to improve threat models.

Victim notification and decryptors

  • Direct contact from agencies: the NCA said it would contact UK-based victims of LockBit, with the FBI and Europol supporting victims elsewhere. Verify any such contact through the agency's published channels before sharing information.
  • Exposure checking services: the Dutch police offered an Emotet email check service in 2021, and Operation Endgame used Have I Been Pwned for 2026 credential notifications.
  • Network owner notification: DOJ credits Shadowserver, Microsoft's Digital Crimes Unit and CISA with helping notify QakBot victims, and the FBI notified hosting providers and authorities in over 50 countries about Emotet servers. Subscribe to Shadowserver reports for your address space and make sure the abuse contact for your IP ranges and domains is monitored.
  • Decryption tools: No More Ransom, an initiative of the Dutch National High Tech Crime Unit, Europol's EC3, Kaspersky and McAfee, collects free decryption tools and advises victims not to pay. Check it and the relevant law enforcement portal before any payment decision. See the Ransomware Response and Recovery Guide.
  • Reporting: UK organisations are pointed to the government's Cyber Incident Signposting Site (NCA); in the US, the FBI's IC3. Reports feed the investigations that later produce keys.

Responding to a takedown notification

  1. Verify: confirm the notice came from the agency, CERT, ISP or provider it claims, using contact details from their official site.
  2. Locate: map the IP address, domain or account in the notice to an asset, owner and time window. Keep DHCP, NAT and VPN logs long enough to do this; 90 days is a practical minimum.
  3. Preserve: image or snapshot the affected hosts before reimaging, and keep EDR and proxy logs, in case law enforcement or insurers ask for them.
  4. Investigate as a live incident: the takedown removed one family at most. Hunt for follow-on tools, new accounts, remote management software and data staging.
  5. Reset identities: rotate passwords, revoke sessions and refresh tokens, and rotate API keys and service account secrets that were present on affected hosts. See the Infostealer Logs Monitoring and Response Guide.
  6. Decide on disclosure: assess regulatory notification duties (for example under GDPR or sector rules) based on what the investigation finds. See the Cyber Incident Reporting Requirements Map.
  7. Close the route: fix the initial access that let the malware in, then monitor the hosts and accounts for at least 30 days.

Re-emergence and successors

Takedowns raise criminal costs but rarely end a market. The sources show three patterns.

  • Return of the same family: Emotet activity resumed later in 2021 after the January disruption, and QakBot's operators allegedly continued with other methods until at least January 2025 (DOJ).
  • Customers switch suppliers: ATT&CK records Pikabot distribution after the QakBot takedown with technical overlaps, linked to Black Basta deployment.
  • Successor groups: Europol describes the May 2025 Endgame phase as targeting new malware variants and successor groups that re-emerged after the previous year's takedowns.

Use takedown announcements as a prompt to test detections against the behaviours the disrupted family shared with its likely successors, rather than retiring rules for the disrupted family. See the Ransomware Family Lineage and Rebrands Guide.

Decision guidance for leaders

  • Reporting to law enforcement: reporting costs little and can return keys, indicators and victim support. The Hive and LockBit cases show keys reaching victims who had engaged.
  • Paying a ransom: the NCA's finding of retained data from paying LockBit victims is direct evidence that deletion promises are unreliable. Check sanctions designations, which can make a payment unlawful.
  • Small organisations: rely on your ISP, managed service provider and national CERT for notification; make sure your MSP contract says they will pass on takedown notices and act on them.
  • Insurers and advisers: tell your cyber insurer and incident response retainer how you will handle a takedown notice, since evidence preservation and law enforcement contact are often policy conditions. See the Cyber Insurance Guide.
  • Threat intelligence value: indictments and court filings often describe intrusion methods in more detail than vendor reports; the QakBot indictment, for example, documents the move to spam bomb attacks. Feed these into threat models and awareness content.
  • Large organisations: assign a named owner for external notifications, subscribe to sinkhole and exposure feeds, and add takedown response to incident playbooks.

Detection and measurement

  • Watch for sinkhole contact: outbound connections to known law enforcement sinkholes or seized domains indicate an infected host even after the malware is neutralised.
  • Retro-hunt published indicators: takedown advisories often include indicators that let you find past infections; search historical DNS, proxy and EDR data.
  • Correlate with your own notices: when a notice names an IP address, check whether the same host also triggered lower-severity alerts that were closed; that gap is a tuning opportunity.
  • Track successor families: update detection coverage when vendors name the replacement loaders and stealers.

Metrics:

  • Time from takedown announcement to completed retro-hunt (target: under five working days).
  • Percentage of external notifications (CERT, ISP, Shadowserver, agency) acknowledged within one working day.
  • Log retention for DNS, proxy and DHCP or NAT data, in days (target: at least 90).
  • Number of hosts found through takedown indicators that existing detections had missed, and the rules added as a result.

Framework mapping

ActivityNIST CSF 2.0NIST SP 800-53 Rev. 5
Receive and act on threat intelligence and external notificationsID.RA-02, ID.RA-03PM-16, SI-5
Incident handling after a notificationRS.MA-01IR-4, IR-6
Coordinate with law enforcement and external partiesRS.CO-03IR-6, IR-7
Retro-hunting and continuous monitoringDE.CM-01, DE.CM-09SI-4, AU-6
Log retention to support investigationsPR.PS-04AU-11

Common failure patterns

  • Treating the uninstaller as remediation: both the Emotet and QakBot operations explicitly left other malware in place.
  • Unmonitored abuse mailboxes: ISP, hosting and CERT notices go to an abuse or registrant address nobody reads.
  • Short log retention: notices often cite activity from weeks or months earlier; without DHCP, NAT and DNS logs the host cannot be identified.
  • Falling for recovery scams: after big takedowns, fake "decryption services" approach victims. Use only official portals and No More Ransom.
  • Retiring detections too early: families return and successors reuse behaviour; keep rules and test them.
  • Assuming you were not affected: victim lists reach organisations through providers and CERTs with delays; absence of a notice is not evidence of absence, so run the retro-hunt anyway.
  • Ignoring identity clean-up: stolen credentials and sessions recovered by law enforcement still work until you reset and revoke them.

Practitioner checklist

  • Name an owner for takedown and law enforcement notifications and publish an internal contact route.
  • Monitor abuse contacts for your IP ranges and domains, and subscribe to Shadowserver or your national CERT's reports.
  • Retain DNS, proxy, DHCP and NAT logs for at least 90 days.
  • Add a takedown response section to your incident playbooks: verify, locate, preserve, investigate, reset identities, decide on disclosure.
  • Run a retro-hunt within five working days of every major takedown announcement.
  • Check No More Ransom and official portals before any ransom decision, and check sanctions lists.
  • Report incidents to law enforcement so you are in the victim pool when keys are recovered.
  • Update detection coverage to successor families each quarter.

Standards and references

Related NHI Mgmt Group resources: Cybercrime Ecosystem Guide · Malware-as-a-Service Economy Guide · Ransomware Response and Recovery Guide · LockBit Threat Actor Profile

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.