Clustered 3 filings across 3 jurisdictions · filing window Jul 29, 2025 → Aug 20, 2025. View entity profile → Other incidents for this victim →
incident inc_c7ed015815ae4ae7 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 29, 2025 → Jul 2, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 5, 2025
Reported by VERMONT AG filing
First Baptist Church of Hammond Established in 1887, The First Baptist Church was listed as 2009's 12th largest church in America in Outreach magazine.
First Baptist Church of Hammond notified Vermont AG of a breach where an unknown actor accessed the network, encrypted files with ransomware, and exfiltrated names and SSNs between June 29 and July 2, 2025. The incident was discovered July 5, 2025. The church is offering 12 months of complimentary credit monitoring. Approximately 2 Rhode Island residents were impacted.
First Baptist Church of Hammond reported a data breach to the Montana Attorney General. The breach was reported on 2025-08-20. The breach occurred from 06/29/2025 to 07/02/2025. 6 Montana residents were affected.
Affected (this filing): 6
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.