HackingHealthcareTechnologyHealthcareBusiness Associate (HIPAA)Customer Data InvolvedDelayed DiscoveryPHIHealth (basic)Identity (basic)LowContained

Aesto Health

bd_c547969d194bb5d1 · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 18, 2025

Filed

Aug 7, 2026

To disclose

33 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

64%

Full breach record for Aesto Health →6 incidents on file

Aesto LLC experienced a network security incident impacting its AWS infrastructure. Unauthorized access to sensitive information pertaining to HIPAA Covered Entity Clients occurred between December 2 and December 18, 2025. Aesto discovered the incident on December 18, 2025, and notified affected Covered Entities on June 26, 2026. The incident is contained. No evidence of misuse was found.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 16 days

discovery → filing · 33 weeks / 232 days

Dec 2, 2025

Begins

Dec 18, 2025

Discovered

Aug 7, 2026

Filed

vs. sector median

+22 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

Washington State AGbd_6ba6b179ea4373bf2026-08-04 · +3dCandidate
California State AGbd_b48dbb172911c31e2026-08-20 · +13dVerified

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

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

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: Not disclosed
Data types: PHIHealth (basic)Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External

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

Time to disclose: 33 weeks(232 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Washington State AGAug 4 · first

New Hampshire State AG+3d · this page

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://mm.nh.gov/files/uploads/doj/remote-docs/aesto-20260807.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 7, 2026
Raw hash: 96236268893b6214a62059a1b888cbdb698c3e0aa740c7dd1a6dd236fe10bb65

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

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov