HackingOtherCustomer Data InvolvedFinancial accountIdentity (basic)Government IDMediumContained

Colonial Presbyterian Church

bd_fef24d5387a8fb3e · schema v1 · pii pii-v2

Severity

Medium

Discovered

Apr 1, 2026

Filed

Aug 1, 2026

To disclose

—

Affected

8state residents only

Linked

5 records

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.

J jump to incidentP pin to compareR raw source

Incident timeline

Apr 1, 2026

Discovered

Aug 1, 2026

Filed

This filing is one of 5 records about the same incident.View merged incident

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 (2) · sorted by filing gap

Indiana State AGbd_2acaeff141a839332026-08-18 · +17dVerified
New Hampshire State AGbd_7fca11e3727017142026-08-18 · +17dVerified by operator

Name: Colonial Presbyterian Church
norm: colonial presbyterian church
Domain: colonialkc.org

Name: Colonial Presbyterian Church
norm: colonial presbyterian church
Domain: colonialkc.org
Industry: Otherllm

Discovered: Apr 1, 2026
Materiality determined: —
Notification sent: Aug 5, 2026
Affected individuals: 8state-resident count only
Data types: Financial accountIdentity (basic)Government ID
Attack vector: Unknown
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External

During the incident: Disconnected all access to the network
Engaged a specialized third-party cybersecurity firm to assist with securing the environment
Conducted a comprehensive forensic investigation
Changed administrative credentials
Restored operations in a safe and secure mode
Enhanced the security measures
Changes made: Providing access to Single Bureau Credit Monitoring/Single Bureau Credit Report/Single Bureau Credit Score services at no charge for 24 months
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Massachusetts State AGAug 1 · first · this page

Indiana State AG+17d

New Hampshire State AG+17d

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.

Source URL: https://www.mass.gov/doc/2026-1382-colonial-presbyterian-church/download
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 1, 2026
Raw hash: 4358bb10fe6b38760af0ec5bc4fffd15f9f4f86a4d7bfdfd4ed9b26e06705dd5

Linked disclosures

Ransomware claims (2)

Regulatory filings (2) · sorted by filing gap

Reporting entityColonial Presbyterian Church

Victim entityColonial Presbyterian Church

Incidentdiscovered Apr 1, 2026

Stated responseDisconnected all access to the network

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.mass.gov