Editor’s Note (Updated: Dec. 19, 2025): This story was updated with additional reporting on the scope of systems affected and later public statements about whether sensitive data was accessed.
Changes in this update:
- Added details on affected systems cited in later reporting, including the student information system, phones and finance systems.
- Added Hudson School Board minutes noting the event was still being resolved weeks later and that no student or staff personal ID data was breached.
- Added district context, including approximate enrollment.
- Clarified that the district has not publicly detailed a specific malware type or ransom demand.
Hudson School District in New Hampshire dealt with a cyber incident in June 2024 that disrupted network access and phone service, the New Hampshire Union Leader reported.
The Union Leader reported that district officials told families the disruption interfered with end-of-year work, including finalizing grades and distributing report cards, and that the district brought in outside help as it worked to restore systems.
The district said it was working with professional incident response support and would provide another update once systems needed for grading were available again, according to the Union Leader’s account.
Later reporting offered a clearer picture of operational impact. In a Feb. 4, 2025 story on school cyber risks, WMUR quoted Superintendent Dan Moulis as saying the district’s firewall was “hit,” prompting shutdown of the student information system and disrupting telephones, financial operations and building air systems.
Moulis told WMUR there was no indication student or staff information was breached in connection with the incident.
Separately, the school board’s Aug. 5, 2024 meeting minutes described a “cybersecurity event” as still being resolved and said the district had found no breach of student or staff personal ID data.
The district enrolls about 2,900 K–12 students, according to a 2024–25 enrollment projection report. Public descriptions have focused on disruption and restoration, without publicly identifying a specific malware strain or confirming whether ransomware was involved.