HackingTechnologyHealthcareInformationStolen CredentialsTargetedData ExfiltratedFinancial accountIdentity (basic)Government IDPHIPIIHealth (basic)HighContained

Aesto Health

bd_6ba6b179ea4373bf · schema v1 · pii pii-v1

Severity

High

Discovered

Dec 18, 2025

Filed

Aug 4, 2026

To disclose

33 weeks

Affected

37,253state residents only

Linked

3 filings

Confidence

70%

Full breach record for Aesto Health →6 incidents on file

Aesto, LLC reported unauthorized access to its AWS infrastructure between Dec 2 and Dec 18, 2025. The incident impacted sensitive information pertaining to HIPAA Covered Entity Clients. Aesto notified affected entities on June 26, 2026. 37,253 Washington residents were affected. No evidence of misuse was found.

J jump to incidentP pin to compareR raw source

Washington clock✗ WA AG >90d33 weeks discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 16 days

discovery → filing · 33 weeks / 229 days

Dec 2, 2025

Begins

Dec 18, 2025

Discovered

Aug 4, 2026

Filed

vs. sector median

+14 wks slower

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

New Hampshire State AGbd_c547969d194bb5d12026-08-07 · +3dVerified
California State AGbd_b48dbb172911c31e2026-08-20 · +16dVerified

Name: Aesto Health
norm: aesto health
Domain: aestohealth.com

Name: Aesto Health
norm: aesto health
Domain: aestohealth.com
Industry: TechnologyllmHealthcarellm

Discovered: Dec 18, 2025
Breach occurred: Dec 2, 2025 – Dec 18, 2025
Undetected for: 16 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 26, 2026
Affected individuals: 37,253state-resident count only
Data types: PIIPHI
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birthMedical informationProtected health information
WA-stated cause: Unauthorized Access
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Initial access: valid_credentials

During the incident: Commenced a prompt and thorough investigation
Worked very closely with external cybersecurity professionals experienced in handling these types of incidents
Conducted an extensive forensic investigation and manual document review
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 33 weeks(229 days from discovery to filing)
Compliance flags: WA AG >90d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Washington State AGAug 4 · first · this page

New Hampshire State AG+3d

California State AG+16d

Pattern: first filing Aug 4 (WA), last Aug 20 (CA) — a 16-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://agportal-s3bucket.s3.amazonaws.com/databreach/BreachA42154.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 4, 2026
Raw hash: ccc2a1b3d675bea8c4dcecf0165aa9e8ac4c81b69be99a64e1d98aac0a1be3d6

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityAesto Health

Victim entityAesto Health

Incidentdiscovered Dec 18, 2025

Stated responseCommenced a prompt and thorough investigation

ComplianceWA AG >90d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com