MalwareHealthcareHealthcareRansomwareData EncryptedCustomer Data InvolvedPHIHealth (basic)Identity (basic)LowContained

Direct Scripts

bd_e65e13dc09abc601 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 30, 2019

Filed

Feb 22, 2019

To disclose

23 days

Affected

2state residents only

Linked

4 filings

Confidence

67%

Full breach record for Direct Scripts →

Direct Scripts experienced a ransomware attack on January 30, 2019, affecting a server containing customer names, addresses, and prescription information (PHI). No SSNs or credit card data were stored on the impacted server. Two New Hampshire residents were affected. The company engaged a forensics firm and offered identity protection services.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 23 days

Jan 30, 2019

Discovered

Feb 22, 2019

Filed

vs. sector median

9 wks faster

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Montana State AGbd_e82d53d6b7c0ccd62019-02-22Verified
HHS OCRbd_673e0645e872913e2019-03-06 · +12dVerified
Illinois State AGbd_6fee2b723be32d612019-01-01 · +52dVerified

Name: Direct Scripts
norm: direct scripts

Name: Direct Scripts
norm: direct scripts
Industry: Healthcarellm

Discovered: Jan 30, 2019
Materiality determined: —
Notification sent: Feb 22, 2019
Affected individuals: 2state-resident count only
Data types: PHIHealth (basic)Identity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Notified the New Hampshire Attorney General

During the incident: Launched an internal investigation
Engaged an independent forensics firm to conduct an investigation
Providing complimentary Automatic Identity Protection to the potentially affected residents
Changes made: Taken steps to strengthen the security of personal information in its possession
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 23 days(23 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Illinois State AGJan 1 · first

Montana State AG+52d

New Hampshire State AG+52d · this page

HHS OCR+64d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/direct-scripts-20190222.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 22, 2019
Raw hash: cddcf68b7120c775be83804ed7f237372e218c044f615a0e85f8020dbdefc56f

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityDirect Scripts

Victim entityDirect Scripts

Incidentdiscovered Jan 30, 2019

Stated responseLaunched an internal investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov