9.5 Million People's Health and Personal Records Stolen in Aesto Health Breach

A Birmingham, Alabama healthcare data company discovered in December 2025 that criminals had broken into its cloud storage and stolen records including Social Security numbers, medical histories, and financial account details belonging to more than 9.5 million people.

ThreatVectr NewsdeskAI-assistedPublished Updated · Editor: Lee Brown· 3 min read
A cloud storage interface showing folders of sensitive documents being copied or accessed, medical records and personal data files highlighted in red, server ra
Illustration made with AI. Not a photograph of the events described.
Share

Key points

  • Aesto Health, a healthcare data services company based in Birmingham, Alabama, confirmed a breach affecting 9,540,683 people.
  • Criminals accessed its Amazon Web Services cloud storage between December 2 and 18, 2025, but the investigation wasn't completed until May 26, 2026.
  • Stolen data includes Social Security numbers, driver's licence numbers, medical records, health insurance details, and financial account numbers.
  • At least two dozen healthcare providers that used Aesto Health's services are caught up in the incident across several US states.
  • Aesto Health has reported the breach to the US Department of Health and Human Services, which added the company to its public breach register on Monday.

Aesto Health isn't a name most patients would recognise. The company works behind the scenes, helping medical practices store old files and exchange electronic health records, and that background role is what made the breach so wide-reaching: one company held data belonging to clients across many states.

What happened, and when?

Criminals broke into portions of Aesto Health's Amazon Web Services infrastructure, the cloud computing platform the company used to store client data, and spent roughly two weeks pulling out files before anyone noticed. The intrusion ran from December 2 to December 18, 2025, when Aesto Health detected the unauthorised activity and shut it down.

External cybersecurity specialists the company brought in then spent months working out exactly what had been taken. That review concluded on May 26, 2026. The company issued its breach notice in June 2026, roughly six months after discovery. Federal rules allow time for investigation before disclosure, but six months is long by any measure. Our 25 August report on the LACMA breach documented a similar delay: notifications went out more than a year after detection.

What was stolen?

Names, Social Security numbers, driver's licence numbers, dates of birth, taxpayer identification numbers, financial account numbers, medical information, and health insurance details were all among the records stolen. That's nearly everything a criminal needs to open a fraudulent account, file a false tax return, or sell an identity.

At least two dozen healthcare providers that relied on Aesto Health's services have been pulled into the incident. Some have chosen to contact affected patients directly.

Should affected people be worried?

Social Security numbers and medical records together are among the most valuable combinations a criminal can hold. They can be sold, used to open credit accounts, or used to fraudulently bill insurers.

Data type stolen Risk to individuals
Social Security number Identity theft, fraudulent credit applications
Financial account numbers Unauthorised bank or card transactions
Medical and insurance records Insurance fraud, medical identity theft
Driver's licence number Identity fraud, false account openings
Taxpayer ID number Fraudulent tax filings

If you received a notification letter from Aesto Health or any of its healthcare provider clients, accept any free credit monitoring offer included. Place a fraud alert, or a full credit freeze, with the major credit bureaus. Watch explanation-of-benefits statements from your health insurer for treatments you never received. Report anything suspicious to the US Federal Trade Commission at reportfraud.ftc.gov.

The Aesto case fits a pattern that keeps repeating: a vendor nobody's heard of quietly holds records for dozens of providers, and a single intrusion multiplies across an entire supply chain. Watch how many of those two dozen providers now face their own notification obligations.

© 2026 Threat Vectr