Cyber Threat Intelligence
CTI Academy Sponsor CTI Academy
CL
Ransomware Victim Manufacturing

Cleaver-Brooks

Ransomware attack by Anubis · Disclosed August 10, 2026 · 🇺🇸 United States

cleaverbrooks.com

Date Disclosed
Aug 10, 2026
2026
Threat Group
Anubis
106 total victims
Country
🇺🇸 United States
Industry
Manufacturing

ThreatAI Analysis

Compiled from this incident record and the threat intelligence profile for Anubis. Figures and technique mappings are quoted from the source data, not inferred.

Anubis listed Cleaver-Brooks on its dark web leak site on 10 August 2026. The manufacturing firm is based in the United States.

About the Anubis group

Anubis is a ransomware-as-a-service group active since December 2024 that targets healthcare, engineering, construction, and professional services sectors, offering affiliates a flexible revenue split model and an optional destructive "wipe mode" alongside standard encryption. Anubis has listed 101 victims since February 2025.

Incident Analysis

Cleaver-Brooks was targeted by Anubis ransomware, one of the most active ransomware groups in our database with 106 confirmed victims globally. The attack was disclosed on August 10, 2026, when Cleaver-Brooks appeared on the group's dark web leak site.

Cleaver-Brooks is based in United States , operating in the Manufacturing sector. United States ranks #1 globally for ransomware attacks, with 9,182 victims in our database.

Sector context: Manufacturing companies are frequently targeted because production downtime directly translates to financial loss. Ransomware operators exploit this time-sensitivity to demand higher ransoms and faster payment.

Anubis typically employs a double extortion model: first exfiltrating sensitive data from the victim's systems, then deploying ransomware to encrypt files. Victims face two simultaneous threats — paying to restore access and paying to prevent publication of stolen data. The group's leak site publishes victim names and exfiltrated data as leverage.

Data source: This incident record is sourced from public ransomware group leak site disclosures aggregated via the ransomware.live API. Disclosure date reflects when the victim was published on the leak site, which may differ from the initial date of compromise. This platform does not publish or link to stolen data. Last data update: Aug 15, 2026 18:00 UTC.

Frequently Asked Questions

Was Cleaver-Brooks attacked by ransomware?

Yes. Cleaver-Brooks was listed as a victim of the Anubis ransomware group on August 10, 2026. The organisation is based in United States and operates in the Manufacturing sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked Cleaver-Brooks?

Cleaver-Brooks was attacked by Anubis ransomware. Anubis is one of the most active ransomware groups, having claimed 106 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the Cleaver-Brooks ransomware attack occur?

The ransomware attack on Cleaver-Brooks was disclosed on August 10, 2026. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the Cleaver-Brooks ransomware attack?

The specific data stolen from Cleaver-Brooks has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. As a Manufacturing organisation, Cleaver-Brooks likely held sensitive business data, client information, and operational records.

How can organisations protect against Anubis attacks?

To defend against Anubis and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.