DisclosureLens
GLOBALMalwareRetail & ConsumerRetailRansomwarePearRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Colonial Presbyterian Church

bd_04944ac226caac3a · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Apr 7, 2026

To disclose

—

Affected

Not disclosed

Linked

5 records

Confidence

50%
Full breach record for Colonial Presbyterian Church →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Pear on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: Consumer ServicesDiscovered: 2026-04-10

Source: Ransomware.live

Post text · scraped from the leak site

Colonial Presbyterian Church operates two campuses in Overland Park and South Kansas City

Incident timeline — mostly unverified

? — ?

Breach window unknown

Apr 7, 2026

Claim posted

—

Corroborated · see linked filings

This record's own dates cannot anchor compliance clocks; see the linked filings.

Claim → filing

—

Compliance clock

Not assessable

This leak-site claim is one of 5 records about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Filing propagation · 3 filings · 3 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

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2023-08-18

pear

According to ransomware.live, Pure Extraction And Ransom (PEAR) Team is the community of highly responsible and strictly disciplined members. We are a private team and have nothing common with any other threat actors. We've been monitoring this field for a long-long time. So, we understand all the processes and know well how it all works.

133 tracked hereFull profile →