MCLAREN HEALTH CARE CORPORATION
bd_6326acdfc9de458a · schema v1 · pii pii-v1
Full breach record for MCLAREN HEALTH CARE CORPORATION →4 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat 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
DESCRIPTION
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 4, 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 Sitealphvbd_c4b2c0198b70501e2023-09-29 · +5dVerified
Regulatory filings (8) · sorted by filing gap
- HHS OCRbd_18c5455f0815045b2023-10-20 · +15dVerified
- California State AGbd_8d2f2b3098afeb792023-11-09 · +35dVerified by operator
- Montana State AGbd_bd9b0633195a292f2023-11-09 · +35dVerified by operator
- Maine State AGbd_c24689bd6cff46e02023-11-09 · +35dVerified
Show 4 more filings ↓Show fewer ↑up to 35d gap
- Massachusetts State AGbd_ddb258a8d643b7952023-11-09 · +35dVerified by operator
- New Hampshire State AGbd_e2978f252f8567182023-11-09 · +35dVerified by operator
- Idaho State AGbd_e37f582cfe47b0242023-11-09 · +35dVerified by operator
- Vermont State AGbd_ed0fb31e367c93232023-11-09 · +35dVerified by operator
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Oct 4, last Nov 9 (VT) — a 35-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.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs