Postmeds, Inc.
bd_88b5f8421795a019 · schema v1 · pii pii-v1
Full breach record for Postmeds, Inc. →2 incidents on filePostmeds, Inc. (CA) reported to HHS on 2023-10-30 a Hacking/IT Incident affecting 2,369,026 individuals. The incident originated at a business associate who experienced a cybersecurity incident impacting PHI. Data involved included names, dates of birth, medications, and some Social Security numbers. Breached information was located on a Network Server. OCR provided the covered entity with technical assistance regarding the HIPAA Rules.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Oct 30, 2023
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Montana State AGbd_8c3ca42ce890db772023-10-30Verified
- California State AGbd_b727b31473a158752023-10-30Verified
- Washington State AGbd_c1180337de38fb7b2023-10-30Verified
- Oregon State AGbd_ffc5b8f5041d0d7c2023-10-30Verified
Show 3 more filings ↓Show fewer ↑up to 80d gap
- Vermont State AGbd_082b80ffa053fb242024-01-17 · +79dVerified
- Massachusetts State AGbd_5a7b739ab24db6492024-01-18 · +80dVerified
- New Hampshire State AGbd_cc30f060acac4baf2024-01-18 · +80dVerified
Filing propagation · 8 filings · 7 states
View merged incident ↗Pattern: first filing Oct 30 (MT), last Jan 18 (NH) — a 80-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.