DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddragonforcehigh sensitivity
Merged incident · 10 filings

Ohio Lottery — December 2023 breach

Clustered 10 filings across 9 jurisdictions · filing window Dec 21, 2023 → May 13, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

538,959

First → last filing

Dec 21, 2023 → May 13, 2024

Merge confidence

100%

incident inc_aa74cbecbabe408f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Dec 24, 2023, discovered Dec 24, 2023 — the first regulatory filing landed 129 days later (flagged late). 538,959 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 144-day schedule across 8 filings beginning Dec 21, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
129days

Discovered → first regulatory filing

Discovery variance
103days

Range of discovered_at dates across filings

Leak precedence
132days before filing

Days between the first leak-site claim and the first regulatory filing. 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.

Filing span
144days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 136dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 34dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 24, 2023breach begins
Dec 24, 2023discovered · members disagree
notification delay · 129 days
May 1, 2024first filing
May 13, 2024most 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 21Leak sitedragonforce postfirst filing · attacker claim · unverifiedday 0
  2. DEC 27Leak sitedragonforce postattacker claim · unverified+7d
  3. MAY 1IL AGIL AG noticeno count stated+132d
  4. MAY 8VT AGVT AG noticeno count stated+139d
  5. MAY 8IN AGIN AG noticestates nationwide total 538,959+139d
  6. MAY 9MT AGMT AG notice25 MT residents+140d
  7. MAY 9ME AGME AG noticestates nationwide total 538,959+140d
  8. MAY 9CA AGCA AG noticeno count stated+140d
  9. MAY 10MA AGMA AG notice152 MA residents+141d
  10. MAY 13NH AGNH AG noticemost recent · 42 NH residents+144d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 24, 2023
IN AG
Discovered
Dec 24, 2023IL AG + VT AG + MT AG +2Apr 5, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + MT AG + ME AG +3
Attack vector
Unauthorized Access
MT AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

538,959

Sum of filed state slices

3,037· 0.6% of stated

99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US538,959
IN2,762
MA152
ME56
NH42
MT25

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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 Aug 23, 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

144 days

Cadence

~1 / 16d

vs. multi-state median

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