medQ, Inc.
bd_47b1f8800add20a6 · schema v1 · pii pii-v1
Full breach record for medQ, Inc. →2 incidents on fileMedQ, Inc. reported to HHS on 2024-02-23 a Hacking/IT Incident affecting 55,917 individuals. Breached information located on Network Server. The incident involved ransomware encrypting PHI including names, addresses, DOB, driver's license, SSN, claims, diagnoses, and treatment info. MedQ notified HHS, individuals, and media, provided credit monitoring, and implemented safeguards.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Feb 23, 2024
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
- California State AGbd_5a44626b9e34f6582024-02-23Verified
- Massachusetts State AGbd_bb9314f65e0432352024-02-23Verified
- Indiana State AGbd_bdb2089ed777401b2024-02-23Verified
- Maine State AGbd_dcfa5a8e797d467d2024-02-23Candidate
Show 3 more filings ↓Show fewer ↑up to 96d gap
- Montana State AGbd_e84e7d460997ea882024-02-23Verified
- 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 (CA), 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.