Data breach, reported Jun 26, 2026
Aesto data breach
Aesto, LLC, a vendor that held data for health care clients, says an unauthorized actor may have accessed or taken information from part of its Amazon Web Services setup between Dec 2 and Dec 18, 2025. Aesto reported 9,540,683 people affected to HHS, and letters offer Kroll identity monitoring. As of Nov 18, 2026, Claim has not found an announced settlement for this breach in the sources listed on this page.
Updates
Payment card number is no longer in the data types listed for this breach in the state filings, so the page lists only the types the filings and letter support. The filings' list of data types was last checked on Nov 18, 2026. Source
Key facts
What happened
Aesto's law firm, McDonald Hopkins, described the incident in a letter dated Jun 26, 2026 and filed with the Washington Attorney General. It says that on or about Dec 18, 2025, Aesto had a network security incident that affected a limited portion of its Amazon Web Services (AWS) infrastructure. The data involved was owned by Aesto's clients that are HIPAA covered entities, such as health care providers.
According to the letter, after a forensic investigation and manual document review, Aesto confirmed on May 26, 2026 that between on or about Dec 2, 2025 and Dec 18, 2025, a limited amount of sensitive information may have been accessed or taken by an unauthorized actor. Aesto notified the affected clients on Jun 26, 2026. The letter says the incident did not affect the clients' own systems and that Aesto has no evidence the information was misused.
What information was exposed
The types of data differ by person. The state filings list:
- Washington: name, Social Security number, driver's license number, financial and banking information, date of birth, medical information and protected health information.
- Texas: name, address, Social Security number, government ID number, medical information, health insurance information and date of birth.
- Vermont: Social Security numbers, government ID numbers and health records.
Who was notified
Aesto filed with Oregon on Jun 26, 2026, with HHS on Jul 31, 2026, with Washington on Aug 4, 2026, with Vermont on Sep 25 and Oct 30, 2026, with California on Oct 30, 2026 and with Texas on Nov 3, 2026.
- HHS: 9,540,683 people.
- Texas: 1,423,768 people in total, including 171,357 Texans.
- Washington: 37,253 residents, in a filing that names Grant County Public Hospital District #2.
- Vermont: 318 and 27 residents in two filings.
Because Aesto held the data for its clients, your letter may name your hospital or clinic as well as Aesto.
What Aesto is offering
The sample letter filed with California offers complimentary identity monitoring through Kroll. The number of months and the activation deadline are printed in each letter. To enroll, visit enroll.krollmonitoring.com/redeem and enter the activation code and verification ID from your letter. The letter also includes steps to protect medical information, such as reviewing your explanation of benefits statements.
What to do now
- Enroll in the Kroll monitoring before the deadline in your letter.
- Place a free credit freeze with Equifax, Experian and TransUnion if your letter lists your Social Security number.
- Only share your health insurance card with your providers and the family members on your plan, as the letter suggests.
- Ask your insurer for a year to date list of services paid under your name and follow up on anything you do not recognize.
- Report identity theft to your local police, your state attorney general and the Federal Trade Commission. The letter gives the FTC phone number 1-877-438-4338.
Lawsuits and settlements
As of Nov 18, 2026, Claim has not found an announced settlement for the Aesto breach in the sources listed on this page. A breach notice is the organization's own report and not a finding of wrongdoing. Claim tracks new data breach settlements and lists them when they open.
Frequently asked questions
Is the Aesto breach letter real?
Aesto filed its notice with the California and Washington attorneys general and reported the breach to HHS. The letter uses Kroll for identity monitoring at enroll.krollmonitoring.com/redeem. It does not ask for payment.
I never heard of Aesto. Why was my data there?
Aesto's law firm says the data belonged to Aesto's clients that are HIPAA covered entities, such as health care providers. Your letter may name the provider whose records Aesto held.
Will there be an Aesto settlement?
As of Nov 18, 2026, Claim has not found an announced settlement for this breach in the sources listed on this page. Claim tracks new data breach settlements and lists them when they open.
What should I do if my Social Security number was exposed?
Enroll in the Kroll monitoring, place a free credit freeze with Equifax, Experian and TransUnion, and ask the IRS for an Identity Protection PIN. Report misuse to the FTC at 1-877-438-4338, the number in the letter.
Claim finds settlements you qualify for and helps you file.
Get alerts if a settlement opens