DisclosureLens
MalwareHealthcareHealthcareRansomwareSupply Chain (3P Vendor)Data EncryptedCustomer Data InvolvedPIIPHIIdentity (basic)Health (basic)LowResolved

TRINITY HEALTH CORPORATION

bd_455d1b215eba5b54 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 16, 2020

Filed

Oct 23, 2020

To disclose

14 weeks

Affected

4state residents only

Linked

5 filings

Confidence

65%
Full breach record for TRINITY HEALTH CORPORATION19 incidents on file

Trinity Health notified Montana residents of a third-party vendor (Blackbaud) ransomware incident affecting donor/patient database backups. Attack occurred April 18-May 16, 2020. Exposed PII and PHI including names, DOB, insurance status. Trinity engaged forensic investigation and offered 12 months of Kroll identity monitoring.

Incident timeline

undetected · 89 days
discovery → filing · 14 weeks / 99 days

Apr 18, 2020

Begins

Jul 16, 2020

Discovered

Oct 23, 2020

Filed

vs. sector median

+3 wks slower

This filing is one of 5 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 (4) · sorted by filing gap

Filing propagation · 5 filings · 5 states

View merged incident ↗
California State AGOct 23 · first
Maine State AGOct 23 · first
Montana State AGOct 23 · first · this page

Pattern: first filing Oct 23 (CA), last Nov 2 (NH) — a 10-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.