Rea Magnet Wire
bd_3b373af2eee32cf6 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cactus on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Download link #1: https://***************.onion/REAWIRE/PROOF/Mirror: https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/REAWIRE/PROOF/DATA DESCRIPTIONS: Personal identifiable information, employees personal files, corporate agreements, projects, financial documents, personnel data, corporate correspondence, etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 6, 2023
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteplaybd_a09f335c88c32fdb2023-09-07 · +1dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Vermont State AGbd_017dd850c8798b1c2023-10-04 · +28dVerified
- Indiana State AGbd_e06ef1d6c90e9ac62023-10-04 · +28dVerified
- Massachusetts State AGbd_2af649b5af5b310f2023-10-31 · +55dVerified by operator
- Maine State AGbd_db0d27d8164babdb2023-10-31 · +55dVerified
Show 1 more filing ↓Show fewer ↑up to 61d gap
- New Hampshire State AGbd_c2f301c49259827e2023-11-06 · +61dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Sep 6, last Nov 6 (NH) — a 61-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
cactus
According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs