One Medical Seniors
bd_b94d4ea581c7e829 · schema v1 · pii pii-v1
Full breach record for One Medical Seniors →Press / 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.
One Medical Data Breach Lawsuit Investigation. One Medical Seniors: A data breach at One Medical Seniors, a healthcare provider for seniors, was discovered. The incident, which occurred between June 8 and June 11, 2026, affected patients in several U.S. cities. A ransomware group named ShinyHunters claimed responsibility for the attack, stating that 8.8 TB of data had been compromised. The breach involved a third-party file storage system used for data archiving, without impacting the primary electronic medical records system.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 13, 2026
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
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.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
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.