← Breach analysis by the Dual Vulnerabilities framework

McLaren Health Care ransomware attack (INC Ransom, 2024)

2024 · United States · Q - Human health and social work activities · Ransomware attack with data theft and IT disruption

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft and IT disruption

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 3/6 stages, weight 20/60

Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) McLaren Health Care is a $6.6bn non-profit system operating 13 hospitals and Karmanos, holding HIPAA-regulated records, under regulatory notification duties to individuals and state regulators and - after notifying 2.19 million people in November 2023 over the ALPHV/BlackCat attack - under post-incident remediation expectations of its own making. (2) Operationally, INC Ransom affiliates held unauthorized access from 17 July to 3 August 2024 undetected for nearly a month, stole personal and health information of 743,131 people and encrypted clinical systems; McLaren detected the incident on 5 August 2024 via suspicious activity and a printed ransom note, restored everything by 27 August ahead of its own schedule, but began written notification to affected individuals only on 20 June 2025, describing the attack as a 'cybersecurity attack by an international ransomware group' without ever naming INC Ransom or acknowledging the encryption and ransom demand that its own ransom note had documented from day one. (3) The classification rests on the response/disclosure stage: the unmet expectation is doctrinal (notification duties and the organization's public account), and the chain broke at leadership - the timing and completeness of disclosure were decision-level conduct that diverged from the documented reality, a gap within the doctrinal column (Strategy to Leadership). The detection and egress gaps (17+ days undetected dwell; unnoticed bulk exfiltration) form a secondary Expertise to Execution pattern, but their mechanisms are only inferred from the access-window dates, so under the origin-x-break rules they cannot carry the case. The entry vector is undisclosed and the group's credential/RDP/MegaSync TTPs are pattern-only and not load-bearing. (4) RM21 (Strategy to Leadership lens): a second ransomware intrusion within twelve months of the 2023 BlackCat attack that McLaren itself had investigated and notified, together with a class-action settlement requiring McLaren to enhance its security program, shows attention, funding and accountability were not sustained after the prior incident (causal role: Perpetuating or Learning-blocking). RM34 (Strategy to Leadership lens): nearly a month of unauthorized access ending in discovery by the attacker's printed ransom note rather than McLaren's own alerting shows leadership oversight did not ensure detection objectives and readiness were meaningful and acted upon (causal role: Obscuring). RM39 (Strategy to Leadership lens): disclosure behaviour diverged from legal expectations and documented facts - 10.5 months from awareness to written notice, a notification that never named the group and never acknowledged encryption or extortion - leaving 743,131 individuals with an incomplete account of what happened to their data (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row dates the disruption from 6 August 2024 and describes detection that day; the victim's own notification letters date unauthorized access 17 July - 3 August 2024 with awareness on or about 5 August 2024 - victim dates used, Year is 2024 either way. Related row 1732 (ALPHV/BlackCat ransomware at McLaren) has no case file in cases-run500, so it could not be read as instructed; the recurrence evidence comes from public reporting and McLaren's 2023 notification as quoted in the sources above. McLaren told ISMG the 2024 incident is 'unrelated to last year's attack'; the consolidated class action alleged failure to learn from the 2023 attack, which McLaren disputed, and the $14M settlement (final hearing April 2026) is not an admission. Whether McLaren paid INC Ransom was never disclosed; INC Ransom did not list McLaren/Karmanos on its leak site and did not leak the data (DataBreaches.net reporting) - the row's description that stolen data 'will be published' reflects the ransom note's threat, which did not materialize. No regulatory penalties followed either attack (The Register) and no regulator examined the controls, so neither the no-failings rule nor RM03 fine reasoning applies. Entry vector undisclosed; group-level TTPs pattern-only. The Check Point threat report listed in the row's source_url was not needed for any claim. Link check: healthcaredive.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: mm.nh.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: hipaajournal.com blocks automated access (HTTP 403); the page was opened and read during research. Every claim citing those pages rests on that read.