MalwareHealthcareHealthcareRansomwareSupply Chain (3P Vendor)Data ExfiltratedData EncryptedPIIHealth (basic)Identity (basic)LowContained

Mercy Health

bd_59b780888055df0b · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 16, 2020

Filed

Oct 18, 2020

To disclose

13 weeks

Affected

24state residents only

Linked

2 filings

Confidence

66%

Full breach record for Mercy Health →12 incidents on file

Mercy Health Foundation, Inc. notified Montana residents of a ransomware incident affecting its third-party vendor, Blackbaud, Inc. The attack occurred in May 2020, with notification received on July 16, 2020. Exfiltrated data included names, dates of birth, and health visit details. No SSNs or financial data were compromised.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 76 days

discovery → filing · 13 weeks / 94 days

May 1, 2020

Begins

Jul 16, 2020

Discovered

Oct 18, 2020

Filed

vs. sector median

+4 wks slower

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

Part of BLACKBAUD, INC. supply-chain incident (2020) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Delaware State AGbd_6bcdcb87d98dbbad2020-09-18 · +30dCandidate

Name: Mercy Health
norm: mercy health

Name: Mercy Health
norm: mercy health
Industry: Healthcarellm

Discovered: Jul 16, 2020
Breach occurred: May 1, 2020
Undetected for: 76 daysoccurrence → discovery
Materiality determined: —
Notification sent: Sep 11, 2020
Affected individuals: 24state-resident count only
Data types: PIIHealth (basic)Identity (basic)
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Third party: via Blackbaud, Inc.
Initial access: supply_chain

During the incident: Reviewed internal records to identify who may have been affected
Worked with Blackbaud to obtain additional information about the nature of the event
Reviewing relationship with Blackbaud and technical controls
Changes made: Reviewing relationship with Blackbaud and technical controls
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

Delaware State AGSep 18 · first

Montana State AG+30d · this page

Pattern: first filing Sep 18 (DE), last Oct 18 (MT) — a 30-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://dojmt.gov/wp-content/uploads/Mercy-Notif.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 18, 2020
Raw hash: 423798dbf930828d5a58c04e8a7bbe5ca54450615d7433e9937f4cecb99bf209

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityMercy Health

Victim entityMercy Health

Incidentdiscovered Jul 16, 2020

Stated responseReviewed internal records to identify who may have been affected

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov