The State of Kansas Office of Judicial Administration — June 2023 breach

Clustered 2 filings across 2 jurisdictions · filed May 6, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

—

First → last dated filing

May 6, 2024

Merge confidence

100%

incident inc_1eb5f16cf3fb4aae · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Intrusion Jun 10, 2023–Oct 12, 2023, discovered Jun 10, 2023. Data reported: Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance

124days

Range of discovered_at dates across filings

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksCalifornia✗ CA 60-day late · 207dFull clock table in Litigation Timeline

Incident timeline

Jun 10, 2023breach begins

Jun 10, 2023discovered · members disagree

May 6, 2024first dated filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

MAY 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
MAY 6CA AGCA AG noticefirst filing · no count statedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 10, 2023 – Oct 12, 2023
Discovered: Jun 10, 2023IL AGOct 12, 2023CA AGfilings disagree on discovery
Data types: Identity (basic)
Attack vector: Unauthorized Access

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

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 filing2 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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Oct 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.

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.