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

Oklahoma Department of Securities — November 2018 breach

Clustered 10 filings across 9 jurisdictions · filing window May 10, 2019 → Jun 25, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

293,492

First → last filing

May 10, 2019 → Jun 25, 2019

Merge confidence

100%

incident inc_dc00c80f309744ec · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Nov 29, 2018–Dec 11, 2018, discovered Dec 11, 2018 — the first regulatory filing landed 150 days later (flagged late). 293,492 individuals reported across the linked filings. Data reported: Government ID, Minor, PII, and 4 more. Notifications rolled out on a 46-day schedule across 10 filings beginning May 10, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
150days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
46days

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 clocksCalifornia✗ CA 60-day late · 147dOregon✗ OR AG >45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Nov 29, 2018breach begins
Dec 11, 2018discovered
notification delay · 150 days
May 10, 2019first filing
Jun 25, 2019most 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. MAY 10CA AGCA AG noticefirst filing · no count statedday 0
  2. MAY 10WA AGWA AG notice2,793 WA residentsday 0
  3. MAY 10MA AGMA AG notice9,365 MA residentsday 0
  4. MAY 10OR AGOR AG noticestates nationwide total 293,492day 0
  5. MAY 14NH AGNH AG notice2,809 NH residents+4d
  6. MAY 15MT AGMT AG notice474 MT residents+5d
  7. MAY 17SC AGSC AG notice1,392 SC residents+7d
  8. JUN 20CA AGCA AG noticeno count stated+41d
  9. JUN 20DE AGDE AG noticeno count stated+41d
  10. JUN 25HI AGHI AG noticemost recent · 1,028 HI residents+46d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 29, 2018
CA AG
Discovered
Dec 11, 2018· 12d undetected
CA AG + WA AG + OR AG +3
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PII
CA AG + SC AG + DE AG +4
Attack vector
Misconfiguration
CA 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)

293,492

Sum of filed state slices

17,861· 6.1% of stated

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

US293,492
MA9,365
NH2,809
WA2,793
SC1,392
HI1,028
MT474

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

46 days

Cadence

~1 / 5.1d

vs. multi-state median

5.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.