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

Southern Illinois University — May 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 1, 2023 → Oct 30, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

38,286

First → last filing

Jan 1, 2023 → Oct 30, 2023

Merge confidence

100%

incident inc_ca9d268449c64f52 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 29, 2023–May 30, 2023, discovered May 29, 2023. 38,286 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 302-day schedule across 7 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
119days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 207d

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine✓ ME AG ≤30d · 30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 29, 2023discovered · members disagree
Jan 1, 2023first filing
Oct 30, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 26Leak sitecl0p postattacker claim · unverified+207d
  3. OCT 24IN AGIN AG noticestates nationwide total 38,286+296d
  4. OCT 25VT AGVT AG noticeno count stated+297d
  5. OCT 25MT AGMT AG notice21 MT residents+297d
  6. OCT 25ME AGME AG noticestates nationwide total 38,286+297d
  7. OCT 25MA AGMA AG notice5,163 MA residents+297d
  8. OCT 30NH AGNH AG noticemost recent · 22 NH residents+302d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
IN AG
Discovered
May 29, 2023IL AGSep 25, 2023VT AG + MT AG + ME AG +1filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + MT AG + ME AG +2
Attack vector
Third-Party / Supply Chain
VT 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)

38,286

Sum of filed state slices

5,702· 14.9% of stated

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

US38,286
MA5,163
IN486
NH22
MT21
ME10

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 Aug 25, 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

302 days

Cadence

~1 / 43.1d

vs. multi-state median

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