GATEWAY REHABILITATION CENTER
bd_f6493c4126c29b05 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Blackbyte 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
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 6, 2022
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Montana State AGbd_e1861cbb398ac64d2022-11-17 · +134dVerified by operator
- HHS OCRbd_05ee2fe15ab138202022-11-18 · +135dCandidate
- Indiana State AGbd_2f03d76418ec490d2022-11-18 · +135dVerified
- New Hampshire State AGbd_9fb984e36d34b4a72022-11-18 · +135dVerified
Show 1 more filing ↓Show fewer ↑up to 135d gap
- Maine State AGbd_b6bd6c502fbaca932022-11-18 · +135dVerified by operator
Filing propagation · 5 filings · 5 states
View merged incident ↗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.
blackbyte
According to ransomware.live, Ransomware. Uses dropper written in JavaScript to deploy a .NET payload.