Boyd Gaming Corporation
bd_1a7e1ea1df6ca8ff · schema v1 · pii pii-v1
Full breach record for Boyd Gaming Corporation →Boyd Gaming Corporation filed an 8-K on September 23, 2025, disclosing a cybersecurity incident where an unauthorized third party accessed internal IT systems and exfiltrated employee and limited other individual data. The incident had no impact on business operations. The Company engaged external cybersecurity experts and federal law enforcement, and is notifying impacted individuals and regulators.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Sep 23, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Indiana State AGbd_106fff4bfd61efe62025-09-24 · +1dVerified
- Montana State AGbd_b508b0707b18975f2025-09-24 · +1dVerified
- Maine State AGbd_5466f54815e13dc02025-10-01 · +8dVerified
- Illinois State AGbd_7fc93624cae46c4c2025-10-01 · +8dVerified
Show 5 more filings ↓Show fewer ↑up to 13d gap
- California State AGbd_d00c1c2465555cb62025-10-01 · +8dVerified
- Vermont State AGbd_4d481001b07bc0f12025-10-02 · +9dVerified
- Texas State AGbd_5385549096954c1e2025-10-02 · +9dVerified
- Iowa State AGbd_fa49a9bb13c2a59c2025-10-02 · +9dVerified
- New Hampshire State AGbd_08fb36c9e929cb422025-10-06 · +13dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing Sep 23, last Oct 6 (NH) — a 13-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.