JACOBS ENTERTAINMENT, INC.
bd_3316cf3bdb191978 · schema v1 · pii pii-v1
Full breach record for JACOBS ENTERTAINMENT, INC. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Silentransomgroup 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
Jacobs Entertainment, Inc. (JEI) is a developer, owner and operator of gaming and entertainment facili...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 23, 2024
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 (6) · sorted by filing gap
- Montana State AGbd_92109ce8c74f23592024-11-06 · +43dVerified
- Indiana State AGbd_3115f359c2e6fdcb2024-11-07 · +44dVerified
- Maine State AGbd_9d9ad94fdc4373ea2024-11-11 · +48dVerified
- Massachusetts State AGbd_fef823bea859e7202024-11-13 · +50dVerified by operator
Show 2 more filings ↓Show fewer ↑up to 449d gap
- Maine State AGbd_b8b13c269b466bba2025-02-03 · +132dVerified
- Maryland State AGbd_f2ceef4a1a16100d2025-12-17 · +449dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Nov 6 (MT), last Dec 17 (MD) — a 406-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.
silentransomgroup
According to ransomware.live, a former Conti team