HackingOtherCustomer Data InvolvedIdentity (basic)Government IDFinancial accountMediumContained

Colonial Presbyterian Church

bd_7fca11e372701714 · schema v1 · pii pii-v2

Severity

Medium

Discovered

Apr 1, 2026

Filed

Aug 18, 2026

To disclose

20 weeks

Affected

1state residents only

Linked

5 records

Confidence

67%

Full breach record for Colonial Presbyterian Church →

Colonial Presbyterian Church detected suspicious network activity on April 1, 2026. An unauthorized user acquired files containing names, addresses, Social Security numbers, and financial account/routing information. One New Hampshire resident was affected. The organization disconnected network access, engaged forensic investigators, and offered 12 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d20 weeks discovery → filing

Incident timeline

discovery → filing · 20 weeks / 139 days

Apr 1, 2026

Discovered

Aug 18, 2026

Filed

vs. sector median

+14 wks slower

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

A leak claim by pear about this victim was first seen 130 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Sitekairosbd_e05afe7d908f48c72026-04-13 · +127dVerified by operator
Leak Sitepearbd_04944ac226caac3a2026-04-07 · +133dVerified by operator

Regulatory filings (2) · sorted by filing gap

Indiana State AGbd_2acaeff141a839332026-08-18Verified
Massachusetts State AGbd_fef24d5387a8fb3e2026-08-01 · +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 18, 2026
Affected individuals: 1state-resident count only
Data types: Identity (basic)Government IDFinancial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Notified the New Hampshire Attorney General

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 to determine the nature and scope of the incident
Changed administrative credentials
Restored operations in a safe and secure mode
Notified the potentially affected individuals
Offering twelve (12) months of complimentary credit monitoring and identity theft restoration services through HaystackID
Changes made: Implemented and will continue to implement additional cybersecurity measures
Implemented policies and procedures to safeguard sensitive information within its care
Enhanced the security measures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 20 weeks(139 days from discovery to filing)
Compliance flags: Leak >90d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Massachusetts State AGAug 1 · first

Indiana State AG+17d

New Hampshire State AG+17d · 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.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/colonial-presbyterian-church-20260818.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 18, 2026
Raw hash: c4810f0483229651ff732f345a27efcd34675081acb1edccdc2edcbcf71428ae

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

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov