HackingEducationEducationData ExfiltratedCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDFinancial accountHealth (basic)EmploymentMediumActive

Edmonds School District

bd_9957884c9a34dc64 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jan 31, 2023

Filed

May 15, 2023

To disclose

15 weeks

Affected

75state residents only

Linked

7 filings

Confidence

64%

Full breach record for Edmonds School District →4 incidents on file

Edmonds School District notified affected individuals of a data breach where unauthorized access occurred between Jan 16-31, 2023. Suspicious activity was detected on Jan 31, 2023. Data at risk included names, SSNs, driver's licenses, DOBs, financial accounts, and medical info. The district engaged forensic specialists and offered 12 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 15 days

discovery → filing · 15 weeks / 104 days

Jan 16, 2023

Begins

Jan 31, 2023

Discovered

May 15, 2023

Filed

vs. sector median

+6 wks slower

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

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Siteakirabd_946936f7fcb626ad2023-08-24 · +102dVerified by operator
Leak Siteakirabd_a3c1da9ae24ac5232023-01-31 · +104dVerified by operator

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_eadbb7a0a4019ca22023-05-15Verified by operator
New Hampshire State AGbd_1b4de5792e8a02632023-05-18 · +3dVerified
New Hampshire State AGbd_8fbc9c1b971a59932023-10-06 · +144dVerified
Washington State AGbd_de1acf46bdc56b2c2023-10-06 · +144dVerified

Name: Edmonds School District
norm: edmonds school district
Domain: edmonds.wednet.edu

Name: Edmonds School District
norm: edmonds school district
Domain: edmonds.wednet.edu
Industry: Educationllm

Discovered: Jan 31, 2023
Breach occurred: Jan 16, 2023 – Jan 31, 2023
Undetected for: 15 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 15, 2023
Affected individuals: 75state-resident count only
Data types: Identity (basic)Government IDFinancial accountHealth (basic)Employment
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External

During the incident: Launched an investigation
Conducted with the assistance of third-party forensic specialists
Undertaking a comprehensive review of the data at risk
Implemented additional safeguards related to data privacy and security
Providing you with access to twelve (12) months of credit monitoring and identity protection services through IDX at no cost to you
Changes made: Securing its network by disabling internet access
Deploying additional protections across its network
Conducting a diligent investigation to confirm the nature and scope of the incident
Working with third-party specialists to strengthen the security of its systems
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 4 states

View merged incident ↗

Massachusetts State AGMay 15 · first

Montana State AGMay 15 · first · this page

New Hampshire State AG+3d

New Hampshire State AG+144d

Washington State AG+144d

Pattern: first filing May 15 (MA), last Oct 6 (WA) — a 144-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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-278.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 15, 2023
Raw hash: 1c0e1cd1e02cad6d389a7f5373801c1ae5ba1202232a56bceacd64aa39f13247

Linked disclosures

Ransomware claims (2)

Regulatory filings (4) · sorted by filing gap

Reporting entityEdmonds School District

Victim entityEdmonds School District

Incidentdiscovered Jan 31, 2023

Stated responseLaunched an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov