DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 9 filings

First Baptist Church of Hammond — June 2025 breach

Clustered 9 filings across 9 jurisdictions · filing window Jul 29, 2025 → Aug 21, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

5,217

First → last filing

Jul 29, 2025 → Aug 21, 2025

Merge confidence

100%

incident inc_c7ed015815ae4ae7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe malware. Intrusion Jun 29, 2025–Jul 2, 2025, discovered Jul 5, 2025 — the first regulatory filing landed 27 days later. 5,217 individuals reported across the linked filings. Data reported: Government ID, Health (basic), and Identity (basic). Notifications rolled out on a 22-day schedule across 8 filings beginning Jul 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
27days

Discovered → first regulatory filing

Discovery variance
33days

Range of discovered_at dates across filings

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
22days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 29, 2025breach begins
Jul 5, 2025discovered · members disagree
notification delay · 27 days
Aug 1, 2025first filing
Aug 21, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 29Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. AUG 1IL AGIL AG noticeno count stated+3d
  3. AUG 20MT AGMT AG notice2 MT residents+22d
  4. AUG 20VT AGVT AG noticeno count stated+22d
  5. AUG 21NE AGNE AG notice8 NE residents+23d
  6. AUG 21ME AGME AG noticestates nationwide total 5,217+23d
  7. AUG 21MA AGMA AG notice10 MA residents+23d
  8. AUG 21IN AGIN AG noticestates nationwide total 5,217+23d
  9. AUG 21NH AGNH AG noticemost recent · 21 NH residents+23d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 29, 2025 – Jul 2, 2025
MT AG
Discovered
Jul 5, 2025MT AG + VT AG + NE AG +1Jul 7, 2025ME AGAug 7, 2025IL AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID
IL AG + MT AG + VT AG +4
Attack vector
Ransomware
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

5,217

Sum of filed state slices

2,989· 57.3% of stated

43% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US5,217
IN2,927
ME21
NH21
MA10
NE8
MT2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

22 days

Cadence

~1 / 2.8d

vs. multi-state median

2.8× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.