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

National Student Clearinghouse — May 2023 breach

Clustered 15 filings across 12 jurisdictions · filing window Jan 1, 2023 → Dec 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

11

Affected · reported

271,496

First → last filing

Jan 1, 2023 → Dec 18, 2023

Merge confidence

100%

incident inc_46d5b89c5e144a9d · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 30, 2023, discovered May 30, 2023. 271,496 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Education, and 1 more. Notifications rolled out on a 351-day schedule across 14 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
21days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 164d

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

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 >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 178dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
May 30, 2023discovered · members disagree
Jan 1, 2023first filing
Dec 18, 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. JUN 14Leak sitecl0p postattacker claim · unverified+164d
  3. AUG 30DE AGDE AG noticeno count stated+241d
  4. AUG 31VT AGVT AG noticeno count stated+242d
  5. AUG 31MT AGMT AG notice393 MT residents+242d
  6. AUG 31ME AGME AG noticestates nationwide total 51,689+242d
  7. AUG 31MA AGMA AG notice198 MA residents+242d
  8. SEP 18NH AGNH AG notice103 NH residents+260d
  9. SEP 21OR AGOR AG noticestates nationwide total 227,553+263d
  10. SEP 21WA AGWA AG notice5,207 WA residents+263d
  11. SEP 21CA AGCA AG noticeno count stated+263d
  12. SEP 22SC AGSC AG notice2,696 SC residents+264d
  13. DEC 12CA AGCA AG noticeno count stated+345d
  14. DEC 15ME AGME AG noticestates nationwide total 271,496+348d
  15. DEC 18NH AGNH AG noticemost recent · 1,695 NH residents+351d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
DE AG
Discovered
May 30, 2023IL AG + NH AGMay 31, 2023DE AG + VT AG + MT AG +2Jun 20, 2023ME AG + WA AG + SC AGfilings disagree on discovery
Data types
Education · Identity (basic) · Government ID · PII
DE AG + VT AG + MT AG +6
Attack vector
Third-Party / Supply Chain
DE 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)

271,496

Sum of filed state slices

11,044· 4.1% of stated

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

US271,496
WA5,207
SC2,696
NH1,695
ME855
MT393
MA198

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

351 days

Cadence

~1 / 25.1d

vs. multi-state median

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