First Secure Community Bank
bd_297822d7143e90e3 · schema v1 · pii pii-v2
Full breach record for First Secure Community Bank →Threat-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 Community Bank is a locally-owned financial institution based in Sugar Grove, Illinois, offering a range of personal and business banking services. Their product offerings include residential lending, personal and business credit cards, and interest-bearing accounts such as CDs and IRAs. The bank focuses on meeting the financial needs of local residents and businesses, ensuring convenience and security in managing finances. Established in 2000, First Secure Community Bank has become a trusted fixture in the community, dedicated to helping clients achieve their financial goals. The company headquarters is located in 670 Sugar Grove Parkway (Route 47), Sugar Grove, IL 60554, United States. 11-50 Employees
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 18, 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.