Cloud Security Office Hours Banner

Change Healthcare 2024

Step-by-step kill chain mapped to MITRE ATT&CK Cloud, sourced from official post-mortems and primary technical analyses.

February 2024 Critical Healthcare Infrastructure

Change Healthcare / ALPHV - Stolen Credentials on a Citrix Portal With No MFA → Nine Days of Lateral Movement → Ransomware → A Third of US Patients Affected

On February 12, 2024 the ALPHV/BlackCat ransomware group used compromised credentials to log in to a Change Healthcare Citrix remote access portal. The portal did not have multi-factor authentication enabled. The actors moved laterally and exfiltrated data for nine days before deploying ransomware on February 21. Change Healthcare processes around 15 billion healthcare transactions a year and touches roughly one in three US patient records, so the outage did not stay technical: pharmacies could not verify coverage, providers could not submit claims or get paid, and parts of the US healthcare payment system stopped working for weeks. UnitedHealth reportedly paid approximately $22 million, and ultimately reported around 190 million individuals affected - the largest healthcare data breach in US history. The initial access was one account, on one internet-facing portal, missing one control.

~190 million individuals affected - the largest US healthcare breach
No MFA on an internet-facing remote access portal
9 days between initial access and ransomware deployment
~$22M ransom reportedly paid; weeks of national disruption
📄 Cybersecurity Dive - Compromised credentials, no MFA ↗ 📄 BleepingComputer - Hacked using a stolen Citrix account with no MFA ↗
Initial Access - One Portal, One Missing Control
01
On February 12, 2024 the actors used stolen credentials to access a Citrix remote desktop portal that had no multi-factor authentication enabled
T1133 - External Remote Services T1078 - Valid Accounts

UnitedHealth's chief executive confirmed to Congress that the portal lacked MFA. There is no exploit in this step and no sophistication - a valid username and password, typed into a remote access gateway exposed to the internet, and that was sufficient. Remote access portals are the most consistently targeted surface in ransomware operations precisely because they are designed for access from anywhere, so an attacker holding credentials is indistinguishable from an employee working from home. Whether the credentials came from an infostealer log, a prior breach or a purchase was not conclusively established publicly; what was established is that a second factor would have made the answer irrelevant.

Date: February 12, 2024
Surface: A Citrix remote desktop portal, internet-facing
Missing control: Multi-factor authentication - confirmed in congressional testimony
Credential source: Not conclusively established publicly
Why it did not matter: A second factor would have made the source moot
Citrix PortalNo MFAStolen CredentialsT1133
🔀 Lateral Movement - Nine Days Before Anything Broke
02
The actors moved laterally through the environment and exfiltrated data over nine days before deploying ransomware on February 21
T1021 - Remote Services T1041 - Exfiltration Over C2 Channel

Nine days is a long time, and it is the part of this chain that offers defenders the most. Modern ransomware operations are double-extortion: the data has to be stolen before anything is encrypted, because the stolen copy is the leverage that survives a good backup. That means there is a substantial window in which the intrusion is quiet but active - credential harvesting, network enumeration, privilege escalation, and sustained outbound transfer of large volumes of data. Every one of those is detectable. Encryption is the end of the attack, not the beginning, and an organization that only detects at the encryption stage has skipped past its entire opportunity to intervene.

Dwell time: February 12 to February 21 - nine days
Activity in that window: Lateral movement, privilege escalation, bulk data exfiltration
Why data first: Double extortion - the stolen copy is leverage a backup cannot defeat
Detection opportunity: Nine days of anomalous internal and outbound activity
Encryption: The end of the attack, not the start
Double Extortion9-Day DwellDetection WindowT1021
🏥 Impact - When the Blast Radius Is a Country's Healthcare Payments
03
Change Healthcare processes ~15 billion transactions a year; with it offline, pharmacies could not verify coverage and providers could not submit claims or receive payment
T1486 - Data Encrypted for Impact

Every other chain on this page measures impact in records, dollars or systems. This one is measured in whether a patient could collect a prescription. Change Healthcare sits in the middle of US healthcare payments as a clearing house, so taking it offline did not degrade one company - it interrupted a function that thousands of independent providers and pharmacies depend on and have no alternative for. Small practices went weeks without revenue, some borrowing to make payroll; pharmacies fell back to manual processes or turned patients away. This is concentration risk in its most literal form: efficiency had routed a third of a country's patient transactions through a single processor, and no participant in that system had chosen or could see that dependency.

Volume handled: ~15 billion healthcare transactions per year
Reach: Roughly one in three US patient records
Consequences: Coverage verification, claims submission and provider payment all stopped
Duration: Weeks of disruption, with some services degraded for months
Root structural issue: Concentration - no alternative, and no visibility into the dependency
Concentration RiskCritical InfrastructureSystemic ImpactT1486
💸 Impact - The Ransom, and Then the Second Demand
04
UnitedHealth reportedly paid around $22 million; the ALPHV affiliate then claimed the operators had taken the payment, and the data resurfaced under a second extortion attempt
T1657 - Financial Theft

The payment did not end it. Public reporting described an exit scam within the ALPHV operation - the affiliate who conducted the intrusion claimed the core group took the ransom and disappeared - after which the stolen data appeared again in the hands of another extortion group demanding payment a second time. Whatever the internal truth, the lesson for anyone weighing a payment decision is concrete: paying buys a promise from a criminal organization that may not control its own affiliates, and the data can be monetized more than once. UnitedHealth ultimately reported roughly 190 million affected individuals, making this the largest healthcare data breach in US history.

Reported payment: ~$22 million
What followed: An apparent exit scam within ALPHV; the affiliate said it was not paid
Then: The data resurfaced under a second extortion demand
Final scale: ~190 million individuals - the largest US healthcare breach recorded
Lesson for payment decisions: A payment buys a promise, and data can be sold twice
ALPHV / BlackCatExit ScamDouble ExtortionT1657

🛡 How to Defend Against This Chain

Enforce MFA on every internet-facing access path, and audit for the ones you have forgotten. This is the entire chain in one sentence. Enumerate every remote access surface you expose - VPN, Citrix, RDP gateways, VDI, legacy portals - and verify MFA is enforced on each, rather than assuming it because policy says so. The exceptions are usually old systems nobody owns, which is exactly what was exploited here.
Hunt in the pre-encryption window, because it is nine days wide. Detection tuned only to ransomware execution arrives at the end of the story. Alert on the behaviours that precede it: credential dumping, unusual internal reconnaissance, new admin accounts, mass file access, and sustained outbound transfer volumes. See detection engineering.
Know your own concentration risk, including the vendors your vendors depend on. Thousands of providers discovered their revenue depended on a company they had no relationship with. Map the third parties that would stop your operations if they stopped, identify which have no substitute, and build a manual or alternate process for the critical ones. That mapping is the work; the alternate process is the outcome.
Segment so that one remote access foothold cannot reach everything. Nine days of lateral movement implies a flat enough environment to permit it. Separate clinical, administrative and payment systems, require re-authentication crossing those boundaries, and restrict which accounts can reach the systems that would halt operations. Segmentation converts a total outage into a partial one.
Decide your ransom position before you need it, and assume payment may not resolve anything. The payment here was followed by a second extortion attempt on the same data. Establish in advance who decides, what legal and regulatory constraints apply, and what your recovery looks like without paying - which means tested, immutable, offline backups, covered in backup and DR.
If you operate infrastructure others depend on, plan for their continuity too. The harm here fell mostly on organizations with no ability to influence Change Healthcare's security. If you are that kind of provider, your resilience planning is a duty to your customers' customers - and publishing enough during an incident for them to make decisions is part of it.

Related defense topics