Direct Scripts
bd_673e0645e872913e · schema v1 · pii pii-v1
Full breach record for Direct Scripts →Direct Scripts reported to HHS on 2019-03-06 a Hacking/IT Incident affecting 9,319 individuals. Breached information located on Network Server. The entity experienced a ransomware attack compromising PHI (names, addresses, prescription info). The entity is no longer in business.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Mar 6, 2019
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 (3) · sorted by filing gap
- New Hampshire State AGbd_e65e13dc09abc6012019-02-22 · +12dVerified
- Montana State AGbd_e82d53d6b7c0ccd62019-02-22 · +12dVerified
- Illinois State AGbd_6fee2b723be32d612019-01-01 · +64dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Mar 6 (OH) — a 64-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.