Healthcare Technology Company · Clinical documentation, billing, and physician workflow services · Healthcare document and billing platform · USA

Doctor Alliance Data Breach (2025)

Healthcare billing and collections management company.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
Elevated
Third 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 October 27, 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. 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
386,583 rows
Field types
4 seen · 10 in the notice
Breach date
2025-10-31
Observed as of
2026-10-27
Attributed
Kazu
How it unfolded45 days from breach to listing
  1. Breach
  2. 10 months laterListed in breach catalogues
  3. Observed · scored
What came out

What data was exposed

Social Security NumberCannot be reissued
Email AddressContactNot in the notice
Full NameIdentity
Phone NumberContactNot in the notice
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

Nothing in what circulates to build an approach on.

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

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.

Lock your mobile number

Ask your carrier for a port-out PIN so no one can move your number to a new 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

Doctor Alliance, a Dallas-based healthcare technology company providing clinical document management and billing services to home health agencies and physician practices, suffered a credential-abuse data breach between October 31 and November 17, 2025. An unauthorized party obtained Doctor Alliance web-portal login credentials through unknown means and used a script to systematically request patient documents from the portal by enumerating combinations of patient IDs and document numbers. A hacker using the alias 'Kazu' claimed responsibility on a hacking forum on November 7, 2025, asserting theft of 1.24 million files totaling 353 gigabytes and demanding a $200,000 ransom by November 21, 2025. Doctor Alliance was alerted on November 13, 2025, notified the FBI on November 16, 2025, and posted a public notice on its website. Multiple home-health clients including Amedisys, AccentCare, Angels Care Home Health, and Prima Care subsequently issued downstream patient notifications.

The breach affected approximately 387,000 individuals based on records indexed by breach-tracking services, with approximately 33,000 unique Social Security numbers and 7,900 unique email addresses among the records. Compromised fields included patient names, addresses, phone numbers, email addresses, dates of birth, Social Security numbers, medical record numbers, Medicare numbers, diagnoses, treatment information, medications, and provider information. Although the hacker's claim of 1.24 million files initially suggested 1.2 million affected individuals, subsequent analysis indicated the actual patient-individual count is substantially smaller, with many files representing duplicate documents for the same patients across multiple home-health visits.

For affected patients, the practical risk profile combines identity-fraud exposure with home-health and Medicare-specific risks. The combination of name, address, date of birth, and Social Security number is a strong base for synthetic identity fraud and fraudulent credit applications. Inclusion of Medicare numbers raises direct healthcare-fraud risk including fraudulent home-health billing. Inclusion of medication and diagnosis information supports highly targeted medical-themed phishing referencing real prescriptions and treatments. Patients receiving home-health services are categorically more vulnerable to medical-fraud and emotional-manipulation scams because they are often elderly or recovering from illness. Affected patients should freeze credit at all three U.S. bureaus, monitor Medicare summary notices and home-health billing statements closely, alert family caregivers to be cautious of unsolicited contact, and treat unsolicited communications referencing Doctor Alliance, home-health agencies, or Medicare with caution.

Recent developments

What has happened since the breach

Doctor Alliance was alerted to a cybersecurity incident on November 13, 2025 after a hacker using the alias 'Kazu' posted on an underground hacking forum on November 7, 2025 claiming to have stolen 1.24 million files totaling 353 GB from Doctor Alliance's systems. The hacker demanded a $200,000 ransom by November 21, 2025, threatening to sell the data if payment was not made. Doctor Alliance's investigation determined that an unknown unauthorized party had obtained Doctor Alliance web-portal credentials and accessed certain files intermittently between October 31, 2025 and November 17, 2025. The unauthorized party also used a script to send multiple requests to the Doctor Alliance web portal using varying combinations of patient IDs and document numbers, indicating credential abuse and enumeration rather than ransomware encryption. Doctor Alliance notified the FBI on November 16, 2025 and posted a public notice on its website. Affected home-health clients including Amedisys (notified January 5, 2026), Angels Care (notified January 13, 2026), and AccentCare (notified February 2026) issued downstream patient notifications. Multiple class-action lawsuits were filed in the U.S. District Court for the Northern District of Texas, Dallas Division.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
The notice covers part of the affected group
Affected
Not disclosed
Fields named
10Social Security number, full name, date of birth, medical diagnosis, health insurance information, provider name, medication, treatment information, disability status, medical record number
Observed by ObscureIQ

Circulating

Observed as of
2026-10-27
Breach date
2025-10-31
Volume
386,583 rows
Fields seen
4Social Security number, email address, phone number, full name
Circulating, not in the notice

2 fields: email address, phone number.

In the notice, not seen circulating

8 fields: date of birth, medical diagnosis, health insurance information, provider name, medication, treatment information, disability status, medical record number.

Potential scope · could reach Severe

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

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
Social Security NumberLasts for yearsYesYes
Email AddressLasts for yearsNoYes
Phone NumberFades over a few yearsNoYes
Full NameLasts for yearsYesYes
Date of BirthLasts for yearsYesNot seen
Medical DiagnosisLasts for yearsYesNot seen
Health Insurance InformationLasts for yearsYesNot seen
Provider nameFades over a few yearsYesNot seen
MedicationLasts for yearsYesNot seen
Treatment informationLasts for yearsYesNot seen
Disability StatusLasts for yearsYesNot seen
Medical Record NumberLasts 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, billing abuse, and provider impersonation. Document and workflow data can also expose treatment relationships and operational vulnerabilities inside clinics.

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 the main risk is credible impersonation and enrichment of existing exposure.

Threat actor

Who is behind this breach

Attributed to Kazu.

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

Background

About the company

Doctor Alliance (operating as My 485, Inc.) is a Dallas, Texas-based healthcare technology company that provides clinical document management, billing, and physician-workflow services to home health agencies and physician practices across the United States. The company's platform integrates with electronic health record systems and processes high volumes of clinical and administrative data, including patient documents, plan-of-care signatures, and Medicare 485 forms. Doctor Alliance's clients include major U.S. home health operators such as Amedisys, AccentCare, Interim HealthCare, Angels Care Home Health, and Prima Care. As a HIPAA-regulated healthcare business associate, Doctor Alliance maintains substantial volumes of protected health information aggregated across its many home-health and physician clients, alongside provider records, scheduling information, and billing data.

Data context

Why the company holds this data

Healthcare workflow and billing platforms collect patient identity, provider records, billing data, clinical documents, scheduling information, and physician workflow records across practice-management operations.

Kazu →HealthcareHealth IT & BillingPrivate company2025

About this record

Only state-level notices have been found; no total has been disclosed. The circulating figure, 386,583 rows, is what has been observed in the published data. Circulation was last verified on 2026-10-27. The score was last computed on 2026-10-27. 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