Village of Skokie
bd_874543b93483ca62 · schema v1 · pii pii-v1
Full breach record for Village of Skokie →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Hunters International 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
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 18, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Illinois State AGbd_b1e459a4531096532024-01-01 · +14dVerified by operator
- Indiana State AGbd_fd72b39f8689619a2024-01-16 · +29dVerified by operator
- Massachusetts State AGbd_b4522a62bc7ea31d2024-01-26 · +39dVerified by operator
Filing propagation · 3 filings · 3 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Jan 26 (MA) — a 25-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.