Healthcare provider · Hospital and clinical care services · Integrated health system · USA

Sutter Health Data Breach (2023)

Healthcare system and provider.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
High
Fourth of five bands on the Breach Risk Index
Observed minimumAt least this much was seen. Read it as a floor · as of September 16, 2026
What this rating measures

The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.

It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.

Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →

Data sensitivity
Restricted

Includes data that cannot be reissued or taken back. A changed password does not reach it.

Circulating
1,463,310 rows
Field types
9 seen · 9 in the notice
Breach date
May 30, 2023
Observed as of
Sep 16, 2026
Attributed
Cl0p / CL0P
Vector
Web Application Exploit
Evidence
High
How it unfoldedFirst listed 18 months after the breach
  1. Breach
  2. 16 months laterNotice filed · HHS OCR
  3. 21 months laterListed in breach catalogues
  4. Observed · scored
What came out

What data was exposed

Medical DiagnosisCannot be reissued
Clinical Metrics (vitals)Cannot be reissued
Health Insurance InformationCannot be reissued
Doctor NameCannot be reissued
Home addressWhere you sleep
Account BalanceFinancialNot in the notice
Email AddressContact
Full NameIdentity
Phone NumberContact
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material · Flagged fields are circulating but missing from the company's notice
What it enables

How this data can be used against you

Enabled

Physical targeting

Links a named person to where they live or go.

Not enabled

Identity

No usable identity package in what circulates.

Not enabled

Social engineering

Contact details only, with too little context for a convincing approach.

Not enabled

Account access

No usable login material in what circulates.

Not enabled

Financial

No usable financial detail in what circulates.

Not enabled

Coercion

Nothing in what circulates is sensitive enough for leverage.

Not enabled

Health

No medical detail in what circulates.

Not enabled

Crypto

Nothing in what circulates is tied to crypto assets.

Enabled: the set on its own is enough · Partial: part of what is needed, or weakened · Not enabled: nothing usable in what circulates
What you should do

Three key actions to take

Assume your home address is findable

Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.

Check your health insurance statements

Read each Explanation of Benefits for care you did not receive, and report anything unfamiliar to your insurer.

Add a verbal password at your bank and brokerage

Ask each one to require it before any change made by phone.

Check it yourself

Check whether you were affected

Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

Talk to us about your exposure

If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.

Request a confidential call →
Full record · 9 sections

The full breach analysis

What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.

  • What happened
  • Recent developments
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach happened

In late May 2023, the Cl0p ransomware gang exploited a zero-day in Progress Software’s MOVEit Transfer platform (CVE-2023-34362) to steal data from Sutter Health’s patient-engagement vendor Welltok (Virgin Pulse) during a May 30-31 window. The exposure affected roughly 845,441 Sutter patients and included names, addresses, phone numbers, emails, dates of birth, insurance-provider details, doctor names, diagnosis/treatment codes, and clinical metrics like blood pressure and weight; Social Security and payment-card numbers were not included. Sutter was notified on September 22, 2023 and disclosed on November 3, 2023. The data later appeared on Cl0p’s leak site and an underground marketplace (about 1.46 million database rows in December 2024). This was a supply-chain/vendor breach, not a direct compromise of Sutter systems.

Recent developments

What has happened since the breach

The patient data was exposed not through a direct attack on Sutter but via its patient-engagement vendor Welltok (Virgin Pulse) during the 2023 MOVEit zero-day campaign. Sutter disclosed the incident on November 3, 2023 and offered one year of credit monitoring; it was criticized for the roughly four-month delay. Litigation (Copans v. Sutter Health & Welltok) was consolidated into the federal In re MOVEit MDL.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Confirmed by the company
Filed with
HHS OCR and 1 otherHHS OCR, Aug 18, 2023; California Attorney General, Nov 3, 2023
Affected
845,441 people
Fields named
9email address, full name, medical diagnosis, phone number, home address, health insurance information, doctor name, clinical metrics (vitals), date of birth
Observed by ObscureIQ

Circulating

Observed as of
Sep 16, 2026
Breach date
May 30, 2023
Volume
1,463,310 rows
Fields seen
9account balance, email address, full name, medical diagnosis, phone number, home address, health insurance information, doctor name, clinical metrics (vitals)
Circulating, not in the notice

1 field: account balance.

In the notice, not seen circulating

1 field: date of birth.

Counts are not compared: the notice counts people, the dataset counts rows. The score is built only on what is seen circulating.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeCirculating
Account BalanceExpires fastNoYes
Email AddressLasts for yearsYesYes
Full NameLasts for yearsYesYes
Medical DiagnosisLasts for yearsYesYes
Phone NumberFades over a few yearsYesYes
Home addressLasts for yearsYesYes
Health Insurance InformationLasts for yearsYesYes
Doctor NameFades over a few yearsYesYes
Clinical Metrics (vitals)Fades over a few yearsYesYes
Date of BirthLasts for yearsYesNot seen

Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.

Downstream risk

How attackers can use this data

Severe risk. Exposure enables identity theft, medical fraud, insurance abuse, and targeted scams exploiting care relationships or treatment status.

Principal risk advisory

Risks for executives and other high-profile people

A healthcare-linked breach: exposure ties a named individual to a provider relationship and, where clinical or insurance data is present, to conditions and treatment. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.

Threat actor

Who is behind this breach

Attributed to Cl0p / CL0P. Part of the MOVEit / Cl0p (2023) campaign.

Profile of Cl0p / CL0P and the other breaches in our records tied to it →

Background

About the company

Sutter Health is a large not-for-profit integrated health system based in Sacramento, California, operating hospitals, clinics, and physician networks across Northern California and serving millions of patients. It maintains patient identity, clinical, insurance, and billing records across its facilities and works with third-party vendors for patient-engagement and administrative services.

Data context

Why the company holds this data

Integrated health systems collect patient identity, contact, insurance, billing, appointment, and clinical records across hospitals, clinics, and administrative operations.

Cl0p →Web Application ExploitHealthcareHospital & Health SystemNonprofit2023

About this record

The reported figure, 845,441 people, is what the company or a regulator disclosed. The circulating figure, 1,463,310 rows, is what has been observed in the published data; the two measure different things and are not compared as equals. Circulation was last verified on Sep 16, 2026. The rating was last computed on Sep 16, 2026. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI