DisclosureLens
Leak SiteState AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 8 filings

National Math and Science Initiative — September 2021 breach

Clustered 8 filings across 8 jurisdictions · filing window Oct 21, 2021 Feb 11, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

191,255

First → last filing

Oct 21, 2021 Feb 11, 2022

Merge confidence

100%

incident inc_cab75e1e65c0437d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 23, 2021–Oct 18, 2021, discovered Oct 13, 2021 — the first regulatory filing landed 117 days later. 191,255 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 113-day schedule across 7 filings beginning Oct 21, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
117days

Discovered → first regulatory filing

Discovery variance
85days

Range of discovered_at dates across filings

Leak precedence
109days 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
113days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >90dMaine ME AG >30d · 32dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 23, 2021breach begins
Oct 13, 2021discovered · members disagree
notification delay · 117 days
Feb 7, 2022first filing
Feb 11, 2022most 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. OCT 21Leak siteconti postfirst filing · attacker claim · unverifiedday 0
  2. FEB 7CA AGCA AG noticeno count stated+109d
  3. FEB 7MT AGMT AG notice19 MT residents+109d
  4. FEB 7ME AGME AG noticestates nationwide total 191,255+109d
  5. FEB 7IN AGIN AG noticestates nationwide total 191,255+109d
  6. FEB 8MA AGMA AG notice105 MA residents+110d
  7. FEB 8SC AGSC AG notice1,899 SC residents+110d
  8. FEB 11NH AGNH AG noticemost recent · 20 NH residents+113d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 23, 2021Oct 18, 2021
CA AG
Discovered
Oct 13, 2021CA AG + MT AG + NH AGJan 6, 2022ME AGfilings disagree on discovery
Data types
Government ID · Identity (basic)
CA AG + MT AG + ME AG +3
Attack vector
Unauthorized Access
MT 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)

191,255

Sum of filed state slices

8,105· 4.2% of stated

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

US191,255
IN6,048
SC1,899
MA105
NH20
MT19
ME14

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
Reviewed
operator-reviewed Aug 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.

Filing velocity

Spread

113 days

Cadence

~1 / 16.1d

vs. multi-state median

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