Aya Healthcare
ent_1c8b558341b1fca72de4974a
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
102
as filed · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Aya Healthcare
- Normalized
- aya healthcare— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- ayahealthcare.com
Disclosure history (5)newest first
- 🏎️Indiana State AGas victim2025-02-27
Aya Healthcare Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-12 and was reported on 2025-02-27. 102 Indiana residents were affected.
- 🦬Montana State AGas victim2025-02-27
Aya Healthcare, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2025-02-27. The breach occurred on 01/29/2025. 9 Montana residents were affected.
- 🦀Maryland State AGas victim2025-02-27
Aya Healthcare, Inc. notified Maryland AG of a data security incident where unauthorized third parties used stolen credentials (obtained from unrelated sources) to access user accounts. The breach involved automated bot access to limited personal information including names, contact info, SSNs, and nursing license numbers. Aya reset passwords and offered 24 months of credit monitoring.
- 🦞Maine State AGas victim2025-02-27
Aya Healthcare, Inc. experienced a data breach impacting four Maine residents. The breach occurred between January 12, 2025, and January 19, 2025, and was discovered on January 29, 2025. Affected individuals were notified on February 27, 2025. The company is offering 24 months of credit monitoring and identity theft restoration services through Experian. The specific details of the breach and the types of information compromised were not disclosed in the notification.
- 🍁Vermont State AGas victim2025-02-27
Aya Healthcare, Inc. notified consumers of a data security incident where unauthorized third parties used stolen credentials (usernames/passwords from unrelated sources) to gain access to user accounts. The breach occurred on January 12 and 19, 2025. An automated bot accessed limited information including names, contact info, nursing license numbers, SSNs, and vaccination status. Aya engaged cybersecurity experts, reset passwords, and offered 24 months of credit monitoring.