DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Boyd Gaming Corporation — September 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Sep 23, 2025 → Oct 6, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

19,381

First → last filing

Sep 23, 2025 → Oct 6, 2025

Merge confidence

100%

incident inc_6abe35562171411a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Sep 5, 2025–Sep 7, 2025, discovered Sep 6, 2025 — the first regulatory filing landed 17 days later (flagged late). 19,381 individuals reported across the linked filings. Data reported: Government ID, PII, Employment, and 1 more. Notifications rolled out on a 13-day schedule across 10 filings beginning Sep 23, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
17days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
13days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta — no leak-site claim in this cluster.

Regulatory clocksIowa✗ IA AG >5 bdayVermont⏱ VT AG >14 bdayCalifornia✓ CA 60-day OK · 18dMaine✓ ME AG ≤30d · 25dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 5, 2025breach begins
Sep 6, 2025discovered
notification delay · 17 days
Sep 23, 2025first filing
Oct 6, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 23SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. SEP 24MT AGMT AG notice40 MT residents+1d
  3. SEP 24IN AGIN AG notice11,000 IN residents+1d
  4. OCT 1IL AGIL AG noticeno count stated+8d
  5. OCT 1CA AGCA AG noticeno count stated+8d
  6. OCT 1ME AGME AG notice25 ME residents+8d
  7. OCT 2IA AGIA AG notice4,000 IA residents+9d
  8. OCT 2VT AGVT AG notice16 VT residents+9d
  9. OCT 2TX AGTX AG notice4,300 affected+9d
  10. OCT 6NH AGNH AG noticemost recent · 40 NH residents+13d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 5, 2025 – Sep 7, 2025
MT AG
Discovered
Sep 6, 2025· 1d undetected
MT AG + IL AG + CA AG +5
Data types
Employment · Identity (basic) · Government ID · PII
SEC 8-K + MT AG + CA AG +6
Attack vector
Unauthorized Access
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

IN11,000
TX4,300
IA4,000
MT40
NH40
ME25
VT16

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

13 days

Cadence

~1 / 1.4d

vs. multi-state median

1.4× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.