First Baptist Church of Hammond
bd_f26219b192211b43 · schema v1 · pii pii-v1
Full breach record for First Baptist Church of Hammond →First Baptist Church of Hammond reported a breach where an unknown actor accessed its network, encrypted files with ransomware, and exfiltrated data containing names, SSNs, and driver's license numbers between June 29 and July 2, 2025. The incident was discovered on July 7, 2025. Approximately 5,217 individuals were affected, including 21 Maine residents. Notices were sent on August 21, 2025, offering 12 months of credit monitoring via TransUnion.
J jump to incidentP pin to compareR raw source
Incident timeline
Jun 29, 2025
Begins
Jul 7, 2025
Discovered
Aug 21, 2025
Filed
vs. sector median
2 wks faster
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siterhysidabd_58ac4cdec3e0a04d2025-07-29 · +23dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Nebraska State AGbd_17cf995dead9c67d2025-08-21Verified by operator
- Massachusetts State AGbd_8d4ca7e05a750f782025-08-21Verified by operator
- Indiana State AGbd_e3aed04ac4644d012025-08-21Verified by operator
- New Hampshire State AGbd_e9e27b94d10bddd42025-08-21Verified by operator
Show 3 more filings ↓Show fewer ↑up to 20d gap
- Vermont State AGbd_4204e1002cded4262025-08-20 · +1dVerified
- Montana State AGbd_5566a28cc1e477882025-08-20 · +1dVerified by operator
- Illinois State AGbd_b1a7ad01b125a0fe2025-08-01 · +20dVerified by operator
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Aug 1 (IL), last Aug 21 (ME) — a 20-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.