DisclosureLens
HackingOtherCustomer Data InvolvedIdentity (basic)Financial accountLowContained

Colonial Presbyterian Church

bd_fef24d5387a8fb3e · schema v1 · pii pii-v2

Severity

Low

Discovered

Apr 1, 2026

Filed

Aug 1, 2026

To disclose

Affected

3state residents only

Linked

4 filings

Confidence

67%
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.

Leak gap clock Leak >90d

Incident timeline

Apr 1, 2026

Discovered

Aug 1, 2026

Filed

This filing is one of 4 about the same incident.View merged incident
A leak claim by pear about this victim predates this filing by 116 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (2)

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings · 2 states

View merged incident ↗
Massachusetts State AGAug 1 · first · this page

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

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.