Huron Regional Medical Center
bd_842ffccecd8ab066 · schema v1 · pii pii-v1
Full breach record for Huron Regional Medical Center →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Beast 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
HRMC is a private, not-for-profit organization. When the ownership of Huron's hospital passed from the Fransciscan Sisters to a locally-owned, private corporation (Huron Regional Medical Center, Inc.) in 1978, those involved in the purchase wanted to ensure Huron's community hospital would be governed by a board of directors reflecting a broad-base of the community. The volunteer board consists of three members recommended by the medical staff, one recommended by the City of Huron and one recommended by the Beadle County Commission. The other board members are elected at-large. Each board member is elected for a three-year term and can serve up to three consecutive terms. The property, funds, affairs and business of HRMC are managed by the board of directors, which is vested with the powers and authority conferred by the laws of South Dakota.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 31, 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 (5) · sorted by filing gap
- HHS OCRbd_765748f8067991912025-06-06 · +6dVerified
- Illinois State AGbd_65c1c1f2a817e0102025-09-01 · +93dVerified by operator
- Nebraska State AGbd_3ea19d5c9ef017182025-09-09 · +101dVerified by operator
- Montana State AGbd_66d03a5c496bc2bc2025-09-09 · +101dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 101d gap
- Indiana State AGbd_e800de1151eea1cf2025-09-09 · +101dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing May 31, last Sep 9 (IN) — a 101-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.
beast
According to ransomware.live, Beast is a Ransomware-as-a-service (RaaS) product which provides functionality such as SMB scanning, file encryption, service and process starting and stopping, and geographic identification to avoid encryption in CIS countries.