medQ, Inc.
bd_e84e7d460997ea88 · schema v1 · pii pii-v1
Full breach record for medQ, Inc. →2 incidents on filemedQ, Inc. experienced a ransomware incident on its third-party hosted platform between Dec 20-26, 2023. Files were encrypted and copied by an unauthorized actor. Affected data included names, SSNs, driver's licenses, DOBs, PHI, and financial account numbers. medQ disconnected the network, engaged forensic investigators, and offered 12 months of credit monitoring. Notification was sent Feb 16, 2024.
J jump to incidentP pin to compareR raw source
Incident timeline
Dec 20, 2023
Begins
Dec 26, 2023
Discovered
Feb 23, 2024
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- HHS OCRbd_47b1f8800add20a62024-02-23Verified
- California State AGbd_5a44626b9e34f6582024-02-23Verified
- Massachusetts State AGbd_bb9314f65e0432352024-02-23Verified
- Indiana State AGbd_bdb2089ed777401b2024-02-23Verified
Show 3 more filings ↓Show fewer ↑up to 96d gap
- Maine State AGbd_dcfa5a8e797d467d2024-02-23Candidate
- New Hampshire State AGbd_c4a29c2a879476bb2024-03-13 · +19dVerified
- California State AGbd_7756d64c62956c672024-05-29 · +96dVerified
Filing propagation · 8 filings · 7 states
View merged incident ↗Pattern: first filing Feb 23 (TX), last May 29 (CA) — a 96-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.