← Breach analysis by the Dual Vulnerabilities framework

Change Healthcare ransomware attack and data breach (BlackCat/ALPHV, 2024)

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

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with mass data theft and nationwide operational disruption

Dual vulnerability type

Strategy to Execution

Evidence coverage: 5/6 stages, weight 29/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) Strategic expectation: after acquiring Change Healthcare in 2022, UnitedHealth Group operated the formal artefacts a processor of roughly 15 billion annual healthcare transactions is expected to have - MFA as a company-wide requirement, a programme to upgrade Change's older technology to UnitedHealth standards, designed continuity redundancies, and notification obligations to regulators and individuals. (2) In practice: an attacker logged into the nation's largest claims clearinghouse on 12 February 2024 with a stolen password on a Citrix portal that did not have multi-factor authentication; nine days of lateral movement and exfiltration passed unnoticed; the redundancies meant to absorb the attack were themselves compromised by the age of the technology; the $22 million ransom paid around 1 March was confirmed only weeks later and individual notices reached roughly 100 million people by October 2024. (3) The classification rests on the entry stage, corroborated by recovery: this is a doctrinal-to-execution gap - the requirement existed at policy level and leadership had decided the upgrade programme, but the policy never became the configured control on the very remote-access estate holding crown-jewel data, and continuity doctrine never became working redundancy in the inherited architecture; the company itself could not say why the server was uncovered. It is not Expertise to Execution (the remedy was not merely known to specialists but required by the organisation's own policy) and not proven Strategy to Leadership (no primary source shows leadership revoking or deferring the requirement itself; alleged pre-breach neglect rests only on later investor-suit claims, flagged in Notes). The response/disclosure gap is a secondary Strategy to Leadership pattern, contributing rather than decisive. The entry vector here is documented and load-bearing. (4) RM22 (Strategy to Execution lens): the company-wide authentication policy did not become a configured, enforced control on the inherited Citrix remote-access portal, so a single compromised credential logged in as a legitimate user even though the same credential had been visible in infostealer logs days before (causal role: Enabling). RM34 (Strategy to Execution lens): monitoring and alert-handling requirements were not operated as intended on the acquired estate - access persisted from 12 to 21 February and surfaced only at encryption (causal role: Obscuring). RM31 (Strategy to Execution lens): the continuity requirement was not translated into surviving redundancy - the backup arrangements intended to mitigate an attack were compromised because of the age of the technology, forcing a ground-up rebuild (causal role: Constraining). RM39 (Strategy to Execution lens): notification and disclosure workflows were not operationalised as policy demanded - a belatedly confirmed ransom payment and individual notices still running months after the breach, with the notification letter omitting the company's own known account of the no-MFA credentials (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

Description matches the stated victim (eurepoc row, incident_id 3196); no related_rows in the case file. Dataset discrepancies: eurepoc_extra.zero_days=Yes reflects the early ScreenConnect zero-day theory (AHA, open-source reporting); the intrusion vector the victim ultimately confirmed was a stolen password on an MFA-unprotected Citrix portal, and the classification rests on that confirmed vector, so no RM18 is coded (zero-day exclusion moot). The initial 8-K suspicion of a nation-state-associated actor gave way to the criminal ALPHV/BlackCat attribution confirmed by the victim. Detection and egress origin/break are coder inferences (no source documents why monitoring and egress controls failed), so those stages cannot win a tie-break. Later investor/derivative-suit allegations (confidential witnesses; reported by Healthcare Dive and Insurance Journal) claim leadership rushed the Change integration and declined funding to fix legacy security; not used as evidence here - if treated as documented they would push the entry break toward leadership (Strategy to Leadership). finance.senate.gov serves the Senate Finance version of the Witty testimony only as HTML; the identical House O&I PDF was opened instead. Sector: health data processor under the method spec's CBS rule, hence Q. Link check: help.senate.gov blocks automated access (HTTP 403); the page was opened and read during research.