AccidentalTechnologyHealthcareInformationMisconfigurationDelayed DiscoveryCustomer Data InvolvedIdentity (basic)Health (basic)PIILowContained

MSCRIPTS

bd_65839045a2f36485 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 18, 2022

Filed

Mar 14, 2023

To disclose

17 weeks

Affected

179state residents only

Linked

4 filings

Confidence

64%

Full breach record for MSCRIPTS →4 incidents on file

mscripts, a prescription management vendor, disclosed that unauthenticated internet access to its cloud storage exposed patient data (names, DOB, addresses, prescription details) from Sept 2016 to Nov 2022. The incident was discovered on Nov 18, 2022. Forensic investigators were engaged. No SSN or financial data was involved.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 2240 days

discovery → filing · 17 weeks / 116 days

Sep 30, 2016

Begins

Nov 18, 2022

Discovered

Mar 14, 2023

Filed

vs. sector median

2 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

Washington State AGbd_0c0303edc104eef52023-03-14Candidate
California State AGbd_99c22a97c6b2ad6b2023-03-14Verified
Oregon State AGbd_f4fa36f617dfea4c2023-03-14Verified

Name: MSCRIPTS
norm: mscripts

Name: MSCRIPTS
norm: mscripts
Industry: TechnologyllmHealthcarellm

Discovered: Nov 18, 2022
Breach occurred: Sep 30, 2016 – Nov 18, 2022
Undetected for: 2,240 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 179state-resident count only
Data types: Identity (basic)Health (basic)PII
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External

During the incident: Took immediate steps to change the access settings
Began an investigation
Engaged a forensic investigation firm
Changes made: Changed the access settings
Continue to look for ways to further enhance the security measures applicable to the services we provide
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 weeks(116 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 ↗

Washington State AGMar 14 · first

California State AGMar 14 · first

Oregon State AGMar 14 · first

Montana State AGMar 14 · first · this page

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://dojmt.gov/wp-content/uploads/OCP/Consumer-Notification-Letter-828.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 14, 2023
Raw hash: 03ddd63af7a40054a103c237aff24fb434856a9f20bac8732d19a80ed85eaef7

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityMSCRIPTS

Victim entityMSCRIPTS

Incidentdiscovered Nov 18, 2022

Stated responseTook immediate steps to change the access settings

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov