INSPECTING ARCHIVED INTELLIGENCE (OUTDATED VERSION).
Aesto attackers breach AWS, exposing 9.5 million patient records
|
2026-09-02 17:15
CRITICAL
LOW
DATA BREACH
Executive Summary
AI-generated
On December 2, 2025, hackers broke into Aesto's Amazon Web Services infrastructure and stole sensitive information related to patients of its customers. The stolen data includes names, Social Security numbers, medical information, driver’s license numbers, financial account numbers, health insurance data, and more. At least 30 healthcare organizations were affected by the breach, with millions of people impacted overall. Aesto notified federal regulators on TKDAY that millions had sensitive information leaked during a cyberattack last December, while also filing breach notices in several states on behalf of its customers. No hacking group has publicly taken credit for the attack and the company did not respond to requests for comment.
Technical Mitigations AI-generated
• Reset credentials and API keys that may have been exposed, and review access logs for the affected accounts or integrations.
Intelligence Metadata
Actors / Malware / CVEs / Campaigns
Target & Sectors
Global Scope
technologytechnology
healthhealth
financefinance
Incident Timeline
December 2
Threat actors broke into Amazon Web Services infrastructure between December 2 and December 18, 2025.
Click on any entity below to view its context and source!
tactic
T1584.006 - Web Services
In its June
statement
, the company said an investigation revealed that hackers broke into its Amazon Web Services infrastructure between December 2 and December 18, stealing troves of information related to patients of its customers.
The network security incident affected part of its Amazon Web Services infrastructure between December 2 and 18, 2025.
organisation
Amazon
In its June
statement
, the company said an investigation revealed that hackers broke into its Amazon Web Services infrastructure between December 2 and December 18, stealing troves of information related to patients of its customers.
December 18, 2025
Threat actors gained unauthorized access to part of Aesto's Amazon Web Services infrastructure between December 2 and December 18, 2025.
Click on any entity below to view its context and source!
industry
Health
“After an extensive forensic investigation and manual document review, on May 26, 2026, we confirmed that between on or about December 2, 2025, and December 18, 2025, certain protected health information belonging to patients of various Covered Entity clients stored within Aesto’s network may have been accessed and/or acquired by an unauthorized actor.”
organisation
Covered Entity
“After an extensive forensic investigation and manual document review, on May 26, 2026, we confirmed that between on or about December 2, 2025, and December 18, 2025, certain protected health information belonging to patients of various Covered Entity clients stored within Aesto’s network may have been accessed and/or acquired by an unauthorized actor.”
organisation
Amazon
The company discovered the incident on December 18, 2025, after attackers gained access to part of its Amazon Web Services infrastructure.
tactic
T1584.006 - Web Services
The company discovered the incident on December 18, 2025, after attackers gained access to part of its Amazon Web Services infrastructure.
December 18
Threat actors exploited vulnerabilities in Amazon Web Services infrastructure between December 2 and December 18 to steal sensitive health data from Aesto's record system.
Click on any entity below to view its context and source!
organisation
Amazon
In its June
statement
, the company said an investigation revealed that hackers broke into its Amazon Web Services infrastructure between December 2 and December 18, stealing troves of information related to patients of its customers.
tactic
T1584.006 - Web Services
In its June
statement
, the company said an investigation revealed that hackers broke into its Amazon Web Services infrastructure between December 2 and December 18, stealing troves of information related to patients of its customers.
May 26, 2026
An unauthorized actor accessed or acquired protected health information stored in Aesto's network between December 2 and December 18, 2025.
Click on any entity below to view its context and source!
industry
Health
“After an extensive forensic investigation and manual document review, on May 26, 2026, we confirmed that between on or about December 2, 2025, and December 18, 2025, certain protected health information belonging to patients of various Covered Entity clients stored within Aesto’s network may have been accessed and/or acquired by an unauthorized actor.”
On May 26, 2026, Aesto confirmed that an unauthorized actor may have accessed or acquired protected health information stored in its network.
organisation
Covered Entity
“After an extensive forensic investigation and manual document review, on May 26, 2026, we confirmed that between on or about December 2, 2025, and December 18, 2025, certain protected health information belonging to patients of various Covered Entity clients stored within Aesto’s network may have been accessed and/or acquired by an unauthorized actor.”
June 26, 2026
General Document Context Starting June 26, 2026, it notified affected healthcare clients whose patients’ data may have been accessed.
Click on any entity below to view its context and source!
industry
Healthcare
Starting June 26, 2026, it notified affected healthcare clients whose patients’ data may have been accessed.
September 01, 2026
Attackers accessed Aesto Health's AWS infrastructure, exposing personal and health data of more than 9.5 million people.
Click on any entity below to view its context and source!
industry
Health
Attackers Access Aesto Health AWS Infrastructure, Exposing 9.5 Million Records
Pierluigi Paganini
September 01, 2026
Aesto Health suffered a breach exposing personal and health data of more than 9.5 million people after attackers accessed its AWS infrastructure.
organisation
Aesto Health
Attackers Access Aesto Health AWS Infrastructure, Exposing 9.5 Million Records
Pierluigi Paganini
September 01, 2026
Aesto Health suffered a breach exposing personal and health data of more than 9.5 million people after attackers accessed its AWS infrastructure.
organisation
AWS
Attackers Access Aesto Health AWS Infrastructure, Exposing 9.5 Million Records
Pierluigi Paganini
September 01, 2026
Aesto Health suffered a breach exposing personal and health data of more than 9.5 million people after attackers accessed its AWS infrastructure.
2026/09/02
Threat actors accessed Aesto Health's Amazon Web Services infrastructure, exposing sensitive information of over 9.5 million individuals.
Click on any entity below to view its context and source!
organisation
TKDAY
On TKDAY, it notified the Department of Health and Human Services that millions were impacted by the data breach.
organisation
the Department of Health and Human Services
On TKDAY, it notified the Department of Health and Human Services that millions were impacted by the data breach.
organisation
Social Security
The stolen data includes names, Social Security numbers, medical information, driver’s license numbers, financial account numbers, health insurance data and more.
organisation
Together Women's Health
Aesto filed breach notices in several states on behalf of its customers, including Together Women's Health in Texas and
California
.
organisation
CareCloud
Another
3.7 million people
were impacted by a March cybersecurity incident involving electronic health records giant CareCloud.
organisation
the US Department of Health and Human Services
The healthcare firm also
notified
the US Department of Health and Human Services (HHS), reporting that the incident impacted 9540683 individuals.
organisation
HHS
The healthcare firm also
notified
the US Department of Health and Human Services (HHS), reporting that the incident impacted 9540683 individuals.
organisation
Attackers Access Aesto Health AWS Infrastructure
Attackers Access Aesto Health AWS Infrastructure, Exposing 9.5 Million Records.
organisation
EHR
Its services include secure data migration, electronic health record (EHR) exchanges and long-term data archiving.
organisation
SecurityAffairs
Follow me on Twitter:
@securityaffairs
and
Facebook
and
Mastodon
Pierluigi Paganini
(
SecurityAffairs
– hacking, Aesto Health)
victims
30 healthcare organizations
At least 30 healthcare organizations were affected by the Aesto breach.
organisation
the Notice of Data Security Incident
“On or about December 18, 2025, Aesto experienced a network security incident that impacted a limited portion of our Amazon Web Services infrastructure.”
reads
the Notice of Data Security Incident.
Tactical Metrics
Metrics
victims
30
Healthcare Organizations
Click for context!
At least 30 healthcare organizations were affected by the Aesto breach.
Intelligence Sources
BleepingComputer
2026-09-01
Aesto Health says data breach affects over 9.5 million patients
BleepingComputer
Security Affairs
2026-09-01
TheRecord
2026-09-02
Unpublish from Social Media?
Are you sure you want to delete this podcast video from all synchronized social networks (YouTube, Facebook, Threads)?
Important:
Due to Meta API restrictions, Instagram Reels cannot be deleted automatically via API by third-party apps.
View Profile to Delete Manually
View Profile to Delete Manually
Tactical Intelligence
Report Intelligence Issue
Podcast Options
Generate
Incident Version History
CURRENT VERSION
Last Updated: 2026-11-12T10:18
Comprehensive Tactical Telemetry
Highly Correlated Entities
23x
organisation
Identified Entity
TKDAY
entity
15x
timeline
Temporal Reference
2026/08/26
date
4x
industry
Targeted Sector
Health
sector
4x
attribution
Attributing Entity
Social Security
authority
Contextual Telemetry
Context Block
6 METRICS
tactic
Cyber Operation Type
Data Breach
tactic
victims
Healthcare Organizations
30
healthcare organizations
tactic
MITRE ATT&CK Technique
T1584.006 - Web Services
technique
target region
Target Country
United States
country
general metric
Individuals
9,540,683
individuals
general metric
Healthcare Providers
29
healthcare providers
Click on any entity below to view its context in the main text!
Selective Unpublish
Select the networks you want to remove this post from. The system will try to delete the real post through the API and clean the database so you can publish it again.
By navigating this website, you accept the use of strictly necessary technical cookies for session security and basic platform functionality. We do not use tracking or advertising cookies. Read our Privacy Policy.
Generating report…
0s