Richmond Behavioral Health Authority
bd_625880881e1f603a · schema v1 · pii pii-v1
Full breach record for Richmond Behavioral Health Authority →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin 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
Richmond Behavioral Health Authority (RBHA) is a statewide organization dedicated to providing comprehensive mental health, mental retardation, substance abuse and prevention services to the residents of the City of Richmond. The organization ...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 15, 2025
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?Regulatory filings (6) · sorted by filing gap
- HHS OCRbd_eb9b4c55106ef3362025-11-28 · +44dVerified
- Nebraska State AGbd_202c1c93b75f1b8c2025-12-04 · +50dVerified
- Indiana State AGbd_e98cc50507d663142025-12-04 · +50dVerified
- Montana State AGbd_3fce0541fd942e3c2025-12-09 · +55dVerified
Show 2 more filings ↓Show fewer ↑up to 63d gap
- New Hampshire State AGbd_38e8c8a165ef20122025-12-16 · +62dVerified
- Massachusetts State AGbd_3f57bc47435431fe2025-12-17 · +63dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Oct 15, last Dec 17 (MA) — a 63-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.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.