First Secure Community Bank
bd_ce1f07f672f64513 · schema v1 · pii pii-v2
Full breach record for First Secure Community Bank →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Storm 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 Secure Bank Group is a U.S.-based financial services organization focused on providing community-oriented banking solutions to individuals, families, and businesses. The group operates through affiliated banking institutions, including First Secure Bank and The State Bank Group. Its services include personal and business checking and savings accounts, commercial and consumer lending, mortgages, online banking, treasury services, and other financial products. First Secure Bank Group emphasizes personalized customer service, long-term relationships, and supporting the financial growth of the communities it serves. Through its network of banking institutions, the group provides accessible financial solutions while maintaining a strong focus on local businesses, community development, and responsible banking practices. The company headquarters is located in 2175 Oneida St, Joliet, IL 60435, USA. 51-200 Employees
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 27, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.