TruthFoundry News
Better tools. Better news.
Wednesday, September 2, 2026 · UTC
1080 of 2345 in this edition
finance

Aesto Health Data Breach Exposes 9.5 Million Patients

Aesto Health reports a breach affecting over 9.5 million individuals via stolen PII and PHI.

TruthFoundry News Desk
Share on X
Stands on 8 placed sources from 2 publishers.
As of 2026-09-02 12:35 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
Aesto Health, a healthcare technology company based in Birmingham, Alabama, reported that more than 9.5 million people had their personal and health information stolen in a data breach. [1] On May 26, 2026, Aesto Health's investigation determined that hackers exfiltrated personally identifiable information (PII) and protected health information (PHI) between December 2 and December 18, 2025. [2] The compromised information includes names, Social Security numbers, driver's license numbers, other ID numbers, dates of birth, financial account numbers, medical information, health insurance information, and taxpayer identification numbers. [3] American healthcare technology company Aesto Health reported a cyberattack in December 2025 that breached its Amazon Web Services infrastructure. [4] The attack affected more than 9.5 million patients across over two dozen clients, including Village Practice Management, Everside Health, and Together Women's Health Medical Group. [5] Aesto Health notified the US Department of Health and Human Services (HHS) that 9,540,683 individuals are impacted by the data breach, and HHS added the company to its data breach portal. [6] The breach also exposed health records, medical histories, claims/billing information, and health insurance information. [7] The stolen data included personally identifiable information, full names, Social Security numbers, partial dates of birth, driver's license numbers, and state identification numbers. [8]
What this stands on
  1. Aesto Health, a healthcare technology company based in Birmingham, Alabama, reported that more than 9.5 million people had their personal and health information stolen in a data breach. · SecurityWeek
  2. On May 26, 2026, Aesto Health's investigation determined that hackers exfiltrated personally identifiable information (PII) and protected health information (PHI) between December 2 and December 18, 2025. · SecurityWeek
  3. The compromised information includes names, Social Security numbers, driver's license numbers, other ID numbers, dates of birth, financial account numbers, medical information, health insurance information, and taxpayer identification numbers. · SecurityWeek
  4. American healthcare technology company Aesto Health reported a cyberattack in December 2025 that breached its Amazon Web Services infrastructure. · TechRadar
  5. The attack affected more than 9.5 million patients across over two dozen clients, including Village Practice Management, Everside Health, and Together Women's Health Medical Group. · TechRadar
  6. Aesto Health notified the US Department of Health and Human Services (HHS) that 9,540,683 individuals are impacted by the data breach, and HHS added the company to its data breach portal. · SecurityWeek
  7. The breach also exposed health records, medical histories, claims/billing information, and health insurance information. · TechRadar
  8. The stolen data included personally identifiable information, full names, Social Security numbers, partial dates of birth, driver's license numbers, and state identification numbers. · TechRadar
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 8 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-03T00:31Z.
The prompts, verbatim
System instruction (the grounding rules)


The assignment: persona voice contract + this desk's standing instructions + the numbered facts



4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.


Integrity


Content hash (SHA-256)fd62d7def5c63c071456241d91a35add41f266865ad5b0ab4a126cc95df9551d


Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed


Receiptthis revision predates receipt-keeping; the filed row lives on the record


Machine readablethe full proof, JSON


Verify



A signature proves who filed this and that it has not changed since. It never makes a claim true.


Up next in this editionFinnish Construction Firm Hits Record Revenue Amid Industry Challenges