DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteSEC 8-KState AGConfirmed14 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvhigh sensitivity
Merged incident · 14 records

MGM RESORTS INTERNATIONAL — March 2019 breach

Clustered 14 records across 11 jurisdictions: 13 filings and 1 leak-site claim · filing window Sep 13, 2023 → Dec 5, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 records

States

10

Affected · reported

1,248,491

First → last filing

Sep 13, 2023 → Dec 5, 2023

Merge confidence

100%

incident inc_3b7cc1809a734581 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 1, 2019–Sep 12, 2023, discovered Sep 8, 2023 — the first regulatory filing landed 5 days later. 1,248,491 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 83-day schedule across 13 filings beginning Sep 13, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
5days

Discovered → first regulatory filing

Discovery variance
21days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 1d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

SEC filing delay
1days

Materiality determination to SEC 8-K filing

Filing span
83days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta

Regulatory clocksOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 27dWashington✓ WA AG ≤30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2019breach begins
Sep 8, 2023discovered · members disagree
notification delay · 5 days
Sep 13, 2023first filing
Dec 5, 2023most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. SEP 13SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. SEP 14Leak sitealphv postattacker claim · unverified+2d
  3. OCT 5OR AGOR AG noticeno count stated+22d
  4. OCT 5VT AGVT AG noticeno count stated+22d
  5. OCT 5MA AGMA AG notice313,400 MA residents+22d
  6. OCT 5IN AGIN AG noticeno count stated+22d
  7. OCT 5ME AGME AG notice0 affected+22d
  8. OCT 5SEC 8-KSEC 8-K noticeno count stated+22d
  9. OCT 5DE AGDE AG noticeno count stated+22d
  10. OCT 5WA AGWA AG notice811,740 WA residents+22d
  11. OCT 5MT AGMT AG notice1 MT residents+22d
  12. OCT 5CA AGCA AG noticeno count stated+22d
  13. OCT 6SC AGSC AG notice123,350 SC residents+23d
  14. DEC 5CA AGCA AG noticemost recent · no count stated+83d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 8, 2023 – Sep 12, 2023
OR AG
Discovered
Sep 8, 2023OR AG + ME AGSep 11, 2023SC AGSep 12, 2023SEC 8-KSep 29, 2023WA AG + MT AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + ME AG + SEC 8-K +6
Attack vector
Unauthorized Access
VT 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

WA811,740
MA313,400
SC123,350
MT1
ME0

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

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

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

SEC 8-K / victim statement2 members

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 Aug 22, 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

83 days

Cadence

~1 / 6.9d

vs. multi-state median

13.8× 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.