Postmeds, Inc.
bd_082b80ffa053fb24 · schema v1 · pii pii-v1
Full breach record for Postmeds, Inc. →2 incidents on filePostmeds, Inc. notified Vermont AG of a cybersecurity incident discovered August 31, 2023. A bad actor accessed files containing names, SSNs, and prescription data between Aug 30 and Sep 1, 2023. Postmeds engaged cybersecurity professionals, secured the environment, and provided one year of credit monitoring to affected individuals.
J jump to incidentP pin to compareR raw source
Incident timeline
Aug 30, 2023
Begins
Aug 31, 2023
Discovered
Jan 17, 2024
Filed
vs. sector median
+8 wks slower
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Massachusetts State AGbd_5a7b739ab24db6492024-01-18 · +1dVerified
- New Hampshire State AGbd_cc30f060acac4baf2024-01-18 · +1dVerified
- HHS OCRbd_88b5f8421795a0192023-10-30 · +79dVerified
- Montana State AGbd_8c3ca42ce890db772023-10-30 · +79dVerified
Show 3 more filings ↓Show fewer ↑up to 79d gap
- California State AGbd_b727b31473a158752023-10-30 · +79dVerified
- Washington State AGbd_c1180337de38fb7b2023-10-30 · +79dVerified
- Oregon State AGbd_ffc5b8f5041d0d7c2023-10-30 · +79dVerified
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.