DisclosureLens
HackingHealthcareHealthcareSupply Chain (3P Vendor)Business Associate (HIPAA)Customer Data InvolvedDelayed DiscoveryPHIGovernment IDIdentity (basic)Health (basic)MediumContained

My Doctor

bd_4dd8989391b8dd18 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Jun 26, 2026

Filed

Aug 14, 2026

To disclose

7 weeks

Affected

1state residents only

Linked

2 filings

Confidence

66%
Full breach record for My Doctor

My Doctor, LLC notified the NH Attorney General of a data security incident involving its third-party vendor, Aesto. An unauthorized actor accessed archived records stored on Aesto's AWS infrastructure between December 2 and December 18, 2025. My Doctor became aware of the incident on June 26, 2026. One New Hampshire resident was affected, with exposure of names and Social Security numbers. My Doctor offered 12 months of credit monitoring.

Incident timeline

undetected · 206 days
discovery → filing · 7 weeks / 49 days

Dec 2, 2025

Begins

Jun 26, 2026

Discovered

Aug 14, 2026

Filed

vs. sector median

6 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings · 2 states

View merged incident ↗
Vermont State AGAug 10 · first
New Hampshire State AG+4d · this page

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.