DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblacksuithigh sensitivity
Merged incident · 7 records

Nashua School District — March 2023 breach

Clustered 7 records across 6 jurisdictions: 6 filings and 1 leak-site claim · filed Feb 28, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

6

Affected · reported

9,829

First → last filing

Feb 28, 2024

Merge confidence

100%

incident inc_093a629660b749f8 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. Intrusion Mar 30, 2023–Apr 28, 2024, discovered Apr 28, 2023 — the first regulatory filing landed 306 days later (flagged late). 9,829 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
306days

Discovered → first regulatory filing

Discovery variance
236days

Range of discovered_at dates across filings

Leak precedence
286days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
0days

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 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 30, 2023breach begins
Apr 28, 2023discovered · members disagree
notification delay · 306 days
Feb 28, 2024first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. MAY 18Leak siteblacksuit postfirst record · attacker claim · unverifiedday 0
  2. FEB 28MA AGMA AG notice769 MA residents+286d
  3. FEB 28NH AGNH AG notice8,117 NH residents+286d
  4. FEB 28IN AGIN AG noticestates nationwide total 9,829+286d
  5. FEB 28ME AGME AG noticestates nationwide total 9,829+286d
  6. FEB 28VT AGVT AG noticeno count stated+286d
  7. FEB 28MT AGMT AG noticemost recent · 2 MT residents+286d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 30, 2023 – Apr 28, 2023
NH AG
Discovered
Apr 28, 2023NH AG + VT AG + MT AGDec 20, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + NH AG +2
Attack vector
Ransomware
NH 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)

9,829

Sum of filed state slices

8,992· 91.5% of stated

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

US9,829
NH8,117
MA769
ME93
IN11
MT2

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 filing6 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 22, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.