GLOBALClaimed by QuantumFirst sighting
Posted to leak site Feb 2, 2022bd_bd1149f74ae8c654
Altoona Area School District serves K-12th grade students and is located in Altoona, PA.
Clustered 4 filings across 4 jurisdictions · filing window Feb 2, 2022 → Apr 11, 2022. View entity profile → Other incidents for this victim →
incident inc_5bb0ae2e0cda416b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT NH PA
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 2, 2021
When the intrusion reportedly occurred, per the linked filings
Dec 2, 2021
Reported by NEW HAMPSHIRE AG filing
Altoona Area School District serves K-12th grade students and is located in Altoona, PA.
Altoona Area School District notified the New Hampshire Attorney General of a data security incident detected on December 2, 2021. Unauthorized access to systems containing personal information of 3 New Hampshire residents was confirmed on March 14, 2022. Affected data included names, dates of birth, and Social Security numbers. The District engaged forensic experts, reported to the FBI, and provided complimentary identity protection services to affected individuals.
Altoona Area School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-01. The breach occurred on 12/2/2021. 2 Montana residents were affected.
Affected (this filing): 2
Altoona Area School District reported to HHS on 2022-04-11 a Hacking/IT Incident affecting 9196 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI (names, DOB, SSN, financial/health data). The entity provided credit monitoring and enhanced security safeguards.
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.
Affected (this filing): 3
Affected (this filing): 9,196