Healthcare provider · Primary and specialty care services · Medical practice network · USA

Sunflower Medical Group Data Breach (2024)

Primary and specialty care medical group.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
High
Fourth of five bands on the Breach Risk Index

Could reach Severe if more of this data surfaces.

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
356,822 rows
Field types
9 seen · 11 in the notice
Breach date
Dec 15, 2024
Observed as of
Sep 16, 2026
Attributed
Rhysida
Vector
Ransomware / Extortion
Evidence
Medium
How it unfolded3 months from breach to listing
  1. Breach
  2. Notice filed · California AG
  3. 18 months laterListed in breach catalogues
  4. Observed · scored
What came out

What data was exposed

Government IDCannot be reissued
Medical DiagnosisCannot be reissued
Social Security NumberCannot be reissued
Health Insurance InformationCannot be reissued
Doctor NameCannot be reissuedNot in the notice
Home addressWhere you sleep
Account BalanceFinancial
Email AddressContact
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

Not enabled

Identity

No usable identity package in what circulates.

Not enabled

Physical targeting

No usable location detail 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.

Freeze your credit, or confirm your freeze is in place

If you have not already, place a free freeze at Equifax, Experian and TransUnion. If you have, sign in to each and confirm it is still on.

Get an IRS Identity Protection PIN

It stops anyone else from filing a tax return under your Social Security number.

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

Kansas-based Sunflower Medical Group detected unusual network activity on January 7, 2025 and determined an unauthorized party had accessed its systems around December 15, 2024, copying files with sensitive personal information. The Rhysida ransomware group said it carried out the attack, advertising a stolen ~3 TB SQL database (claimed to hold data on roughly 400,000 patients). Sunflower filed a breach notice with the Maine Attorney General on March 7, 2025 and notified affected individuals. Official filings put the affected count at 220,968; a DataBreach.com parse recorded 356,822.

Exposed data included names, addresses, birth dates, Social Security numbers, health insurance and medical information, and driver's license numbers. The company later agreed to a class-action settlement worth as much as $1.2 million.

Recent developments

What has happened since the breach

After the December 2024 intrusion (detected January 7, 2025), Sunflower notified affected individuals, filed with state regulators, and offered identity-theft protection. It later agreed to a class-action settlement worth as much as $1.2 million. The Rhysida ransomware group claimed the attack and advertised a 3 TB SQL database for sale.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Filed with
California Attorney General and 2 othersCalifornia Attorney General, Mar 7, 2025; HHS OCR, Mar 7, 2025; Texas Attorney General, May 14, 2025
Affected
220,968 people
Fields named
11account balance, email address, government ID, medical diagnosis, phone number, home address, Social Security number, health insurance information, date of birth, driver's license, full name
Observed by ObscureIQ

Circulating

Observed as of
Sep 16, 2026
Breach date
Dec 15, 2024
Volume
356,822 rows
Fields seen
9account balance, email address, government ID, medical diagnosis, phone number, home address, Social Security number, health insurance information, doctor name
Circulating, not in the notice

1 field: doctor name.

In the notice, not seen circulating

3 fields: date of birth, driver's license, full name.

Potential scope · could reach Severe

If the fields named only in the notice surface, this record would be rated Severe.

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 fastYesYes
Email AddressLasts for yearsYesYes
Government IDLasts for yearsYesYes
Medical DiagnosisLasts for yearsYesYes
Phone NumberFades over a few yearsYesYes
Home addressLasts for yearsYesYes
Social Security NumberLasts for yearsYesYes
Health Insurance InformationLasts for yearsYesYes
Doctor NameFades over a few yearsNoYes
Date of BirthLasts for yearsYesNot seen
Driver's LicenseLasts for yearsYesNot seen
Full NameLasts 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 of identity theft, medical fraud, insurance abuse, and targeted healthcare scams. Care-network data can also expose ongoing treatment relationships.

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 Rhysida.

Profile of Rhysida and the other breaches in our records tied to it →

Background

About the company

Sunflower Medical Group is a Kansas-based primary and specialty care medical practice providing outpatient healthcare across multiple clinics. It maintains patient identity, contact, insurance, billing, scheduling, and treatment records spanning primary and specialty care relationships.

Data context

Why the company holds this data

Medical practice networks collect patient identity, contact, insurance, billing, appointment, and treatment records across primary and specialty care operations.

Rhysida →Ransomware / ExtortionHealthcarePhysician Practice & ClinicPrivate company2024

About this record

The reported figure, 220,968 people, is what the company or a regulator disclosed. The circulating figure, 356,822 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