Ransomware gang
Cactus
Claims on its leak site since 20 July 2023; none in the last 12 months
- Claims, 12 months
- 0
- Last 30 days
- 0
- All claims
- 248
- Last claim
- 21 March 2025
Where its claimed victims are
Sectors
Claims matched to an official notice
3 organisations Cactus claimed also filed a breach notice with a regulator, 2 of them after the claim. Matched by name: the notice does not say who the attacker was.
- Caltrol Inc.
Claimed 26 February 2025 · notice filed with the California Attorney General 7 May 2025 - Biagi Bros, Inc.
Claimed 21 March 2025 · notice filed with the California Attorney General 25 February 2025 - OmniVision Technologies, Inc.
Claimed 16 October 2023 · notice filed with the California Attorney General 17 May 2024
What a claim is, and is not
A claim is a ransomware gang naming an organisation on its leak site, usually to pressure it into paying. It is the gang’s word: some claims are false, recycled from older breaches or exaggerated, and a claim says nothing about whose personal data, if any, was taken. That is why we count claims but do not list the organisations, and why a breach goes on the tracker as confirmed only when the organisation or a regulator says so.
How this is counted
Claims as collected from the gangs’ leak sites by ransomware.live, which says itself that they are unverified. We read its list every day and keep only counts: by month, by the victim’s country and by sector (as ransomware.live classifies them). Matches with official notices are by the organisation’s name, from 30 days before the claim to a year after it, against California’s and Washington’s full breach registers and every official notice on the tracker. A match is not a confirmation rate: those registers only see breaches of their own residents, and names are written differently. We never link to or visit leak sites.
From the data breach tracker: official notices, breach databases and the news, every fact with its source. Open data (CC BY 4.0) · How the tracker works · Found a mistake? Tell us and we correct it.