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

Select Education Group — January 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Nov 17, 2023 → Mar 22, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

67,097

First → last filing

Nov 17, 2023 → Mar 22, 2024

Merge confidence

100%

incident inc_f9b00513a7be4dcf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 8, 2023–Nov 5, 2023, discovered Nov 5, 2023 — the first regulatory filing landed 136 days later (flagged late). 67,097 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 125-day schedule across 7 filings beginning Nov 17, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
136days

Discovered → first regulatory filing

Discovery variance
64days

Range of discovered_at dates across filings

Leak precedence
123days 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
125days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 73dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 8, 2023breach begins
Nov 5, 2023discovered · members disagree
notification delay · 136 days
Mar 20, 2024first filing
Mar 22, 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. NOV 17Leak siteblacksuit postfirst filing · attacker claim · unverifiedday 0
  2. MAR 20IN AGIN AG noticestates nationwide total 67,097+123d
  3. MAR 20VT AGVT AG noticeno count stated+123d
  4. MAR 21CA AGCA AG noticeno count stated+124d
  5. MAR 21OR AGOR AG noticestates nationwide total 67,097+124d
  6. MAR 21MT AGMT AG notice39 MT residents+124d
  7. MAR 21ME AGME AG noticestates nationwide total 67,097+124d
  8. MAR 22NH AGNH AG noticemost recent · 7 NH residents+125d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 8, 2023
IN AG
Discovered
Nov 5, 2023MT AG + NH AGJan 8, 2024OR AG + ME AGfilings disagree on discovery
Data types
Education · Financial account · Identity (basic) · Government ID · PII
VT AG + CA AG + MT AG +2
Attack vector
Unauthorized Access
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)

67,097

Sum of filed state slices

90· 0.1% of stated

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

US67,097
MT39
IN29
ME15
NH7

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

125 days

Cadence

~1 / 17.9d

vs. multi-state median

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