Riverhead Central School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-22. The breach occurred from 11/9/2021 to 12/3/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Mar 22, 2022 → Mar 23, 2022. View entity profile → Other incidents for this victim →
incident inc_888363548e1d4ca4 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 9, 2021
When the intrusion reportedly occurred, per the linked filings
Dec 3, 2021
Reported by MAINE AG filing
Riverhead Central School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-22. The breach occurred from 11/9/2021 to 12/3/2021. 1 Montana residents were affected.
Affected (this filing): 1
Riverhead Central School District experienced a ransomware attack on November 9, 2021, discovered on December 3, 2021. The incident affected 22,050 individuals, including names and Social Security Numbers. The district notified affected individuals on March 22, 2022, and provided 12 months of credit monitoring and ID protection through TransUnion/IDX. Two Maine residents were specifically identified among the affected.
Affected (this filing): 22,050
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.