Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 083
No. 083 Critical Brief · Regulatory Attribute Proof

Change Healthcare: Stolen credentials opened remote access, and US medical-claims processing stalled for weeks (UnitedHealth Group congressional testimony)

~1/3
Share of US health-insurance claims processing handled by Change Healthcare (also put at 40–50%). The outage lasted weeks
~9 days
From the intrusion (2024-02-12, estimated) to detection of the ransomware (02-21)
100M+
Medical records affected (HHS disclosure). Later estimates put it at up to 190 million
CountryUS
Incident date2024-02-21
Published2026-06-26
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

The login at the entry point used a stolen ID and password and was outwardly indistinguishable from legitimate remote access. Detection worked only at the ransomware-deployment stage, after lateral movement inside the network had progressed. Even when the password matches, unless you separately check that the person logging in is the authorized holder, a login with stolen credentials passes as legitimate access.

Figure 1"Detection" vs "pre-execution check"

Pre-execution check = before accepting a remote-access login, check that the party logging in is the authorized holder, and record it. Detection = noticing the attack after the intrusion. The intrusion date (02-12) is an estimate.

Pre-execution check · not known from the disclosuresBefore the login, check that the party is the authorized holder
What was confirmedAbout 9 days inside the network,
indistinguishable from legitimate access
Detection · worked after the intrusionNotices the ransomware deployment and shuts down core systems
02-12 (est.)
Login with stolen credentials
From 02-12
Lateral movement inside the network
02-21
Detects it and shuts down core systems
2024-05
Intrusion path stated in congressional testimony

What got through

What got through
A login to the Citrix remote-access entry point with stolen credentials (ID and password). UnitedHealth Group’s CEO said in congressional testimony that the intrusion path was a single Citrix account with no MFA configured.
What was stopped
Change Healthcare detected the attack at the ransomware-deployment stage and shut down core systems. By then the attacker had been moving laterally inside the network (the intrusion is estimated at 2024-02-12).
What the receiving side sees
In general, an entry point that accepts a password alone receives an ID and a password. A legitimate user’s login and a login with stolen credentials look the same to it.
Not disclosed
How the credentials were obtained (phishing, info-stealing malware or a dark-web purchase are possible, but the path has not been disclosed). The intrusion date is an estimate.

Pre-execution check

The condition that holds regardless of route is that the entry point checks, before accepting a login and separately from the password match, that the party logging in is the holder with authority over that scope.

The core of this case
Even when the password matches, unless you separately check that the person logging in is the authorized holder, a login with stolen credentials passes as legitimate access.
Who approves
The organization (the side that manages access rights). It decides in advance who may enter which scope, for which operational need.
Where the check happens
At the remote-access entry point. Beyond the password match, it checks before the login that the party is the authorized holder. Logins that cannot be checked do not go through.
What is recorded
Which party passed the entry point, under what authority and when, and under what authority it touched medical records and the like.

Detection limited the damage by shutting systems down, but it came about 9 days after the intrusion. Unlike cases where the entry point had no authentication at all, such as DeepSeek (an unauthenticated database), here a legitimate, authenticated entry point was logged into with credentials.

What Lemma does

Lemma builds the pre-execution check into the remote-access entry point. It does not look for intrusions; it checks before the login, separately from the password match, that the party logging in is the authorized holder.

Industries and operations to watch

IndustryHealthcare
Organizations that run infrastructure many providers connect to, such as medical-claims processing and health-information exchange. One entry point can stop operations nationwide.
OperationAccount administration and remote access
Accounts on entry points reached from outside, how logins work, and access rights to protected health information (PHI).

Current controls vs Lemma

The route in this case is column 1 (a remote-access login with stolen credentials). Column 2 is lateral movement and ransomware deployment after the login; this case was detected at that stage.

Control Remote-access login with stolen credentials Lateral movement and ransomware deployment after the login
MFA (factors beyond the password) Partial Not relevant
Ransomware detection and system shutdown Not effective Partial
Lemma (pre-execution check) Effective Partial

MFA adds resistance to a login with a stolen password alone by also checking factors other than the password. It was not configured on the Citrix account named as the intrusion path (UnitedHealth Group congressional testimony). Ransomware detection worked at the deployment stage and shut down core systems, but the first login was indistinguishable from legitimate access, and detection came about 9 days after the intrusion. Lemma checks before the login, separately from the password match, that the party is the authorized holder. Access to medical records can likewise be checked, at the time of access, for the authority it rests on, and recorded.

Note: Lemma’s check works only when it is built into the remote-access entry point and authority decisions are managed apart from the password. It can be passed if the authorized holder’s device or session is taken over as a whole. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three things to confirm about remote access in your organization

  • Can the entry points reached from outside be entered with a password alone?
  • Do you check at the entry point that the party logging in is the holder with authority over that scope?
  • Do you record who touched sensitive data such as medical records, and under what authority?

Facts and timeline

Affected organization
Change Healthcare (a UnitedHealth Group subsidiary; the largest medical-claims processing and health-information exchange network in the US).
Attacker
The AlphV/BlackCat ransomware group. RansomHub later carried out separate extortion.
Intrusion path
A login with stolen credentials (ID and password) to a Citrix remote-desktop / VPN gateway entry point that had no MFA configured (congressional testimony by UnitedHealth Group’s CEO).
Operational impact
For weeks, prescription-dispensing verification at pharmacies nationwide, hospital insurance billing and physician eligibility checks were impossible or severely delayed. Some hospitals had to ask for cash payment and could not verify prescription-drug stock.
Financial impact
The ransom UnitedHealth Group paid was approximately $22 million (a separate payment to RansomHub was also reported later). Total losses including the outage, recovery and provider support are reported in the billions of dollars.
Data impact
The medical records, personal information and insurance information of over 100 million Americans (up to 190 million in later estimates) may have been affected. It is described as the largest healthcare data breach in US history.

Glossary
Citrix remote access — The entry point for reaching internal systems from outside the company. This intrusion began with a login to it.
MFA (multi-factor authentication) — A way of logging in that confirms the person with another factor, such as a device in hand or a biometric, in addition to the password.
Lateral movement — An intruder moving from system to system inside a network and widening their privileges.

Timeline

2024-02-12 (estimated)
The attacker logs in to the Citrix account with no MFA configured, using stolen credentials, and begins moving laterally inside the network.
2024-02-21
Change Healthcare detects the ransomware attack and shuts down core systems. Medical claims and prescription processing halt nationwide.
2024-02-21 to March
Pharmacies, hospitals and physicians nationwide are affected. HHS (the US Department of Health and Human Services) announces an emergency response. The AHA (American Hospital Association) appeals to Congress, citing catastrophic impact.
March 2024 (estimated)
AlphV/BlackCat receives the approximately $22 million ransom and then disbands. Affiliates holding the data reappear as RansomHub and separately extort Change Healthcare.
2024-05
UnitedHealth Group CEO Andrew Witty testifies before Senate and House committees and states that the Citrix account with no MFA configured was the intrusion path.
From 2024-10
HHS discloses the affected count (initially over 100 million). Later estimates of up to over 190 million are reported.

This Brief rests on UnitedHealth Group’s congressional testimony and HHS disclosures as primary sources. The intrusion date (2024-02-12) is an estimate, and the affected count has been updated over time, so consult the latest information. What has not been disclosed does not mean there were no controls.

After disclosure

  • UnitedHealth Group / Change Healthcare: Shut systems down immediately and set up emergency funding assistance for providers (billions of dollars). Investigated and disclosed the scope of the breach in parallel with recovery.
  • HHS (US Department of Health and Human Services): Issued emergency guidance and temporarily relaxed how HIPAA rules were applied. Disclosed the affected count (over 100 million).
  • AHA (American Hospital Association): Asked Congress for emergency measures, citing “catastrophic and unprecedented” impact.
  • AlphV/BlackCat: Effectively disbanded after receiving approximately $22 million. According to a whistleblower, the group leader kept the ransom, and affiliates regrouped as RansomHub with the data.
  • Industry debate: Debate over making MFA a de facto requirement in healthcare IT accelerated. HHS began considering a revision to the HIPAA Security Rule that would state an MFA requirement. Attention to third-party risk management for healthcare infrastructure grew.

Sources

References: “The last layer left for cyber defense in the age of AI”, “Proof-as-Auth: sign in without ever sending your key”

The same method elsewhereSee all 21 "Account takeover" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"Change Healthcare: Stolen credentials opened remote access, and US medical-claims processing stalled for weeks (UnitedHealth Group congressional testimony)".
Lemma Critical Brief No.083. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/083-change-healthcare-mfa-credential-access/
Read nextNext
All Briefs →
Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.