TRINITY HEALTH CORPORATION
bd_455d1b215eba5b54 · schema v1 · pii pii-v1
Full breach record for TRINITY HEALTH CORPORATION →19 incidents on fileTrinity 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.
J jump to incidentP pin to compareR raw source
Incident timeline
Apr 18, 2020
Begins
Jul 16, 2020
Discovered
Oct 23, 2020
Filed
vs. sector median
+3 wks slower
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- California State AGbd_6e3d23b7dac7f7942020-10-23Verified
- Maine State AGbd_ec12a22c818ff94b2020-10-23Candidate
- Massachusetts State AGbd_482ed296ab25e7142020-10-26 · +3dVerified
- New Hampshire State AGbd_7a8b08f8bebef4882020-11-02 · +10dVerified
Filing propagation · 5 filings · 5 states
View merged incident ↗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
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.