First Baptist Church of Hammond
bd_58ac4cdec3e0a04d · schema v1 · pii pii-v1
Full breach record for First Baptist Church of Hammond →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Rhysida 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.
Source: Ransomware.live
Post text · scraped from the leak site
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.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 29, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Illinois State AGbd_b1a7ad01b125a0fe2025-08-01 · +3dVerified by operator
- Vermont State AGbd_4204e1002cded4262025-08-20 · +22dVerified
- Montana State AGbd_5566a28cc1e477882025-08-20 · +22dVerified by operator
- Nebraska State AGbd_17cf995dead9c67d2025-08-21 · +23dVerified by operator
Show 4 more filings ↓Show fewer ↑up to 23d gap
- Massachusetts State AGbd_8d4ca7e05a750f782025-08-21 · +23dVerified by operator
- Indiana State AGbd_e3aed04ac4644d012025-08-21 · +23dVerified by operator
- New Hampshire State AGbd_e9e27b94d10bddd42025-08-21 · +23dVerified by operator
- Maine State AGbd_f26219b192211b432025-08-21 · +23dVerified by operator
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Jul 29, last Aug 21 (ME) — a 23-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.
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.
rhysida
According to ransomware.live, Rhysida is a ransomware-as-a-service (RAAS) group that emerged in May 2023. The group utilizes a namesake ransomware through phishing attacks and Cobalt Strike to breach the targets' networks and deploy their payloads. The group threatens to publicly distribute exfiltrated data if the ransom is not paid, and it's worth mentioning that Rhysida is still in the early stages of development. The ransomware leaves PDF notes in the affected folders, instructing victims to contact the group through its portal, and payment is made via Bitcoin. After encryption, the ransomware appends the extension '.ryshida' to encrypted files. Source: https://github.com/crocodyli/ThreatActors-TTPs