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

BetMGM, LLC — May 2022 breach

Clustered 10 filings across 10 jurisdictions · filing window Dec 20, 2022 → Dec 27, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

58,964

First → last filing

Dec 20, 2022 → Dec 27, 2022

Merge confidence

100%

incident inc_1b165985207e4d7d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion May 1, 2022–May 23, 2022, discovered Nov 28, 2022 — the first regulatory filing landed 22 days later. 58,964 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 7-day schedule across 10 filings beginning Dec 20, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
22days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 23dWashington✓ WA AG ≤30dCalifornia✓ CA 60-day OK · 23dOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2022breach begins
Nov 28, 2022discovered
notification delay · 22 days
Dec 20, 2022first filing
Dec 27, 2022most 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. DEC 20MA AGMA AG noticefirst filing · 4,436 MA residentsday 0
  2. DEC 21ME AGME AG notice459 affected+1d
  3. DEC 21DE AGDE AG noticeno count stated+1d
  4. DEC 21WA AGWA AG notice2,022 WA residents+1d
  5. DEC 21CA AGCA AG noticeno count stated+1d
  6. DEC 21MT AGMT AG notice45,755 MT residents+1d
  7. DEC 21OR AGOR AG noticeno count stated+1d
  8. DEC 21IN AGIN AG notice3,734 IN residents+1d
  9. DEC 22SC AGSC AG notice1,852 SC residents+2d
  10. DEC 27NH AGNH AG noticemost recent · 706 NH residents+7d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 21, 2022 – May 23, 2022
ME AG
Discovered
Nov 28, 2022· 191d undetected
ME AG + DE AG + WA AG +5
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + DE AG +5
Attack vector
Unauthorized Access
ME AG

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

MT45,755
MA4,436
IN3,734
WA2,022
SC1,852
NH706
ME459

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 filing10 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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

7 days

Cadence

~1 / 0.8d

vs. multi-state median

1.3× faster

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.