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

Riverhead Central School District — November 2021 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window Mar 22, 2022 → Mar 24, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

22,050

First → last filing

Mar 22, 2022 → Mar 24, 2022

Merge confidence

100%

incident inc_f258481dc9a24165 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion Nov 9, 2021, discovered Dec 3, 2021 — the first regulatory filing landed 109 days later. 22,050 individuals reported across the linked filings. Data reported: Government ID, Minor, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
109days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
87days 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
2days

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 · 110dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Nov 9, 2021breach begins
Dec 3, 2021discovered
notification delay · 109 days
Mar 22, 2022first filing
Mar 24, 2022most recent filing

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. DEC 25Leak sitelockbit2 postfirst record · attacker claim · unverifiedday 0
  2. MAR 22IN AGIN AG noticestates nationwide total 22,050+87d
  3. MAR 22MT AGMT AG noticestates nationwide total 422+87d
  4. MAR 23MA AGMA AG notice7 MA residents+88d
  5. MAR 23ME AGME AG noticestates nationwide total 22,050+88d
  6. MAR 24NH AGNH AG noticemost recent · states nationwide total 422+89d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 9, 2021
IN AG
Discovered
Dec 3, 2021· 24d undetected
MT AG + ME AG + NH AG
Data types
Identity (basic) · Government ID · Minor
MT AG + ME AG + NH AG +1
Attack vector
Ransomware
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)

22,050

Sum of filed state slices

18· 0.1% of stated

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

US22,050
MA7
NH6
IN2
ME2
MT1

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

2 days

Cadence

~1 / 0.5d

vs. multi-state median

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