Aesto Data Breach: What Happened and What You Should Do
Aesto disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.
- Company
- Aesto
- People affected
- Undisclosed (318 VT)
Aesto has not published a national total in the sources reviewed. Vermont's table lists 318 Vermont residents (October 30, 2026); that is a Vermont-only count.
- Incident date
- December 2 – 18, 2025
- Discovered
- December 18, 2025
- Disclosed
- October 30, 2026
- Information exposed
- Name · possibly social security number, government identification, health information
- Status
- Notification underway
Notices with complimentary identity monitoring; call center 833-918-8060.
What happened in the Aesto breach?
How the attacker got in
A network security incident affected part of Aesto's Amazon Web Services infrastructure, where an unauthorized actor may have accessed or acquired archived health care records.
Reports conflict
Timeline of what is known
- 01December 2 – 18, 2025Unauthorized access
- 02December 18, 2025Breach discovered
- 03October 30, 2026Breach disclosed publicly
- 04October 2026Affected individuals notified
Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.
What information was exposed?
The categories below come from Aesto's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.
Name
Full name (Aesto notice).
Social Security number
Social Security number (Vermont AG table).
Government identification
Government ID number (Vermont AG table).
Health information
Health records (Vermont AG table).
Why this information matters
The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.
Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.
Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.
If you were affected, consider doing these things now
Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.
- 01Enroll in the complimentary identity monitoring using the activation code in your letter before its deadline.
- 02Consider a free credit freeze with Equifax, Experian, and TransUnion; it blocks new accounts in your name and is free to place and lift.
- 03Request an IRS Identity Protection PIN to help stop someone else from filing a tax return with your Social Security number.
- 04Review account statements and credit reports for activity you do not recognize.
- 05Review explanation of benefits statements from your health insurer for care you did not receive; letters may name your health care provider rather than Aesto.
AI Protection
Monitoring, alerts, and recovery help for what comes after a breach.
A breach puts information you can't take back into circulation. AI Protection watches for it being misused, alerts you when something changes, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.
How one breach can contribute to a larger exposure footprint
A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.
Illustrative pattern- Step 1
One breach
A single company's records are accessed without authorization.
- Step 2
Personal information is exposed
Some categories can be changed afterward. Others, like a name or date of birth, can't.
- Step 3
It may remain accessible
Copies of breached data can persist well beyond the original incident.
- Step 4
Sources can be combined
Fragments from different breaches and public sources may be assembled into a fuller profile.
- Step 5
More targeted attempts
A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.
A breach is an event. Exposure can last longer.
A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.
Involved in this breach and hard to change
None of the categories reported in this breach are in the hard-to-change group. Changeable items like passwords and account numbers should still be addressed.
What Aesto has done so far
Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.
Sources
Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.
Last updated November 3, 2026 · First published November 3, 2026
Questions about the Aesto breach
Take control of what happens next.
Monitoring for misuse of your information, alerts when something changes, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.