People search One Medical data breach timeline because regulated data and trust are existential—one incident triggers class actions and regulator exams. BreachHistory indexes 1 One Medical-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why One Medical breach history matters
One Medical operates in Healthcare (United States). Across indexed rows, recurring themes include ransomware and extortion, third-party and supply-chain exposure, unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — confirmed breach; legacy One Medical Seniors/Iora archive accessed (Jun)
Verified breach. Verified breach — disclosed June 17, 2026. Amazon-owned One Medical confirmed an unauthorized third party accessed a third-party file storage platform containing archived legacy data for One Medical Seniors patients (formerly Iora Health, acquired 2021). One Medical discovered the activity June 13, 2026, secured the system, and determined access occurred June 8–11, 2026. The company stated the incident was limited to that archival platform—not other clinics, services, or the main One Medical EMR—and contained demog Exposed categories include Legacy Iora Health/One Medical Seniors demographic and clinical records for patients in Atlanta, Cape Cod, Charlotte, Piedmont Triad, Denver, Houston, Phoenix, Tucson, and Seattle . No attested victim count is published for this row yet. See the one-medical-shinyhunters 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple One Medical catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple One Medical catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple One Medical catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Watch for medical-ID theft and billing fraud after health-data incidents.
- Step 5: Bookmark the One Medical company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/one-medical · Latest: one-medical-shinyhunters2026.
Sources: BreachHistory catalog (1 row for One Medical), company and regulator disclosures cited in individual breach records.