Postmeds, Inc.
bd_b727b31473a15875 · schema v1 · pii pii-v1
Full breach record for Postmeds, Inc. →2 incidents on filePostmeds, Inc. disclosed a cybersecurity incident where a bad actor accessed pharmacy management files between August 30 and September 1, 2023. The company discovered the breach on August 31, 2023. Affected data included names and prescription information (medication type, demographics, prescribing physician). Social Security numbers were not involved. Postmeds engaged cybersecurity professionals, secured its environment, and is enhancing security protocols and employee training.
J jump to incidentP pin to compareR raw source
Incident timeline
Aug 30, 2023
Begins
Aug 31, 2023
Discovered
Oct 30, 2023
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- HHS OCRbd_88b5f8421795a0192023-10-30Verified
- Montana State AGbd_8c3ca42ce890db772023-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 (CA), 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.