Colonial Presbyterian Church
bd_fef24d5387a8fb3e · schema v1 · pii pii-v2
Full breach record for Colonial Presbyterian Church →Colonial Presbyterian Church detected suspicious activity on April 1, 2026, and disconnected network access. A forensic investigation found evidence that files were acquired by an unauthorized user. Affected data may include name, address, financial account number, and routing number. The incident impacted 3 Rhode Island residents. The organization engaged a third-party cybersecurity firm, changed credentials, and is offering 24 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Apr 1, 2026
Discovered
Aug 1, 2026
Filed
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Sitekairosbd_e05afe7d908f48c72026-04-13 · +110dVerified by operator
- Leak Sitepearbd_04944ac226caac3a2026-04-07 · +116dVerified by operator
Regulatory filings (1) · sorted by filing gap
- New Hampshire State AGbd_7fca11e3727017142026-08-18 · +17dVerified by operator
Filing propagation · 2 filings · 2 states
View merged incident ↗Pattern: first filing Aug 1 (MA), last Aug 18 (NH) — a 17-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.