Rocky Mountain Gastroenterology
bd_b46575107c88e717 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Trinity 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
330Gb - Revenue: $60.3 Million - Publication date: 2024-10-16
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 15, 2024
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 (2)
- Leak Sitemeowbd_9fca488ade88c4ff2024-10-13 · +28dVerified by operator
- Leak Siteransomhubbd_67f4f5408beee7962024-09-28 · +13dVerified
Regulatory filings (4) · sorted by filing gap
- HHS OCRbd_d4038f0e9b58c13a2024-11-13 · +58dVerified
- Nebraska State AGbd_5fb0b0794e457ef02025-01-15 · +121dCandidate
- Indiana State AGbd_8ada4905789be4312025-01-15 · +121dVerified
- Montana State AGbd_e533d69040c252422025-01-15 · +121dVerified
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Sep 15, last Jan 15 (MT) — a 121-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.
trinity
According to ransomware.live, Trinity ransomware was first discovered in May 2024, believed to be a rebrand of the Venus/2023Lock variants, using ChaCha20 encryption and double-extortion via a Tor leak site; the US HHS flagged it as a specific threat to the healthcare sector after confirmed attacks on healthcare organizations.