Alabama Ophthalmology Associates
bd_679b407e17b92387 · schema v1 · pii pii-v1
Full breach record for Alabama Ophthalmology Associates →2 incidents on filePress / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Alabama Ophthalmology Associates Provides Notice Following Data Security Incident. Alabama Ophthalmology Associates: Alabama Ophthalmology Associates experienced a data security breach that affected the personal and protected health information of certain current and former patients. The incident was discovered on January 30, 2025, and the company took steps to secure its network and notify potentially affected individuals. The potentially affected information includes names, addresses, dates of birth, driver's license numbers, Social Security numbers, medical information, and health insurance information. Linked ransomware group: bianlian.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 22, 2025
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Sitebianlianbd_96d0378c765266ca2025-02-19 · +29dVerified
- Leak Sitebianlianbd_6cfa972104e80ea52025-01-22Verified
Regulatory filings (3) · sorted by filing gap
- Pressbianlianbd_90cff1ac4a912cf12025-01-30 · +8dCandidate
- HHS OCRbd_450516280d94079d2025-04-08 · +76dVerified
- Vermont State AGbd_ba02658c7e2a50752025-04-08 · +76dVerified
Filing propagation · 4 filings · 2 states
View merged incident ↗Pattern: first filing Jan 22, last Apr 8 (VT) — a 76-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
bianlian
According to ransomware.live, BianLian ransomware operations began in late 2021. The group practices multi-pronged extortion, demanding payment for a decryptor, as well as the non-release of stolen data. The ransomware group hosts a public, TOR-based, blog to post victim identities and stolen data. Somewhat unique to BianLian at the time of their launch was their inclusion of an I2P mirror for their blog.