MalwareEducationEducationRansomwareData EncryptedTargetedIdentity (basic)LowContained

Nashua School District

bd_d356fb91d837912e · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 28, 2023

Filed

Feb 28, 2024

To disclose

44 weeks

Affected

2state residents only

Linked

4 filings

Confidence

62%

Full breach record for Nashua School District →3 incidents on file

City of Nashua School District notified individuals of a ransomware attack occurring between March 30 and April 28, 2023. The incident involved unauthorized access to systems containing personal information (names). The district engaged third-party specialists, rebuilt its environment, and reported the incident to federal law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 29 days

discovery → filing · 44 weeks / 306 days

Mar 30, 2023

Begins

Apr 28, 2023

Discovered

Feb 28, 2024

Filed

vs. sector median

+35 wks slower

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteblacksuitbd_2072f1e4910b73e32023-05-18 · +286dVerified

Regulatory filings (2) · sorted by filing gap

Indiana State AGbd_3df01d72db8cdf602024-02-28Verified
Vermont State AGbd_a42ea78b7e8dde202024-02-28Verified

Name: Nashua School District
norm: nashua school district
Domain: nashua.edu

Name: Nashua School District
norm: nashua school district
Domain: nashua.edu
Industry: Educationllm

Discovered: Apr 28, 2023
Breach occurred: Mar 30, 2023 – Apr 28, 2023
Undetected for: 29 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 2state-resident count only
Data types: Identity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Reported incident to federal law enforcement

During the incident: Working with third-party computer specialists
Rebuilt environment in a safe and secure manner
Conducted comprehensive review of impacted files
Reported incident to federal law enforcement
Notifying individuals and relevant state authorities
Changes made: Reviewing and enhancing existing policies, procedures, and system security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 44 weeks(306 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Indiana State AGFeb 28 · first

Vermont State AGFeb 28 · first

Montana State AGFeb 28 · first · this page

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-1143.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 28, 2024
Raw hash: b8fbf5cc58dbc17fe8d3eac2711ece7d7ec42b9e937a4c1834573906e466712c

Linked disclosures

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Reporting entityNashua School District

Victim entityNashua School District

Incidentdiscovered Apr 28, 2023

Stated responseWorking with third-party computer specialists

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov