Skip to navigation

Threat reportRansomwareTL-2026-6348

Wilmington School District 209U (IL) Reports Ransomware Attack and Possible Data Breach

mediumACTIVE

Wilmington School District 209U in Wilmington, Illinois told staff and families on 2026-11-17 that it experienced a ransomware attack that may have involved a data breach. The district suspended district-issued laptops and other Windows devices as a precaution while cybersecurity specialists determine scope.

Key facts

IdentifiersTL-2026-6348
SeverityMEDIUM
First disclosed
Affected productsMicrosoft Windows (district-issued laptops and other Windows devices)
MITRE ATT&CK techniquesT1021 Remote Services, T1059 Command and Scripting Interpreter, T1078 Valid Accounts, T1567 Exfiltration Over Web Service
MotivationFINANCIAL
Target sectorseducation, k-12, public-sector
Target regionsNorth America, united states of america, Illinois
Detection rules9 (1 shown free)
Sources6 cited sources

Detection coverage

As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6348 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Ransomware Recovery Inhibition - Shadow Copy and Backup Deletion (T1490)

Detects commands (vssadmin, wmic shadowcopy, wbadmin, bcdedit, PowerShell Win32_ShadowCopy) that delete volume shadow copies, backup catalogs or disable Windows recovery. This is the pre-encryption step typical of Windows ransomware (T1486 Data Encrypted for Impact, the only technique evidenced for TL-2026-6348, Wilmington School District 209U). The specific family and initial access vector are not public, so this is behaviour-first hunting logic for the Windows fleet, not a family signature.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1490, T1486, T1059
  • Data sources: sysmon, windows_security
  • Severity: high
  • Confidence: high

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h
| eval cmd=lower(CommandLine), img=lower(Image)
| where (like(img,"%vssadmin.exe") AND like(cmd,"%delete%") AND like(cmd,"%shadows%")) OR (like(img,"%wmic.exe") AND like(cmd,"%shadowcopy%") AND like(cmd,"%delete%")) OR (like(img,"%wbadmin.exe") AND (like(cmd,"%delete catalog%") OR like(cmd,"%delete backup%") OR like(cmd,"%delete systemstatebackup%"))) OR (like(img,"%bcdedit.exe") AND (like(cmd,"%recoveryenabled no%") OR like(cmd,"%bootstatuspolicy ignoreallfailures%"))) OR (like(img,"%powershell.exe") AND like(cmd,"%win32_shadowcopy%") AND (like(cmd,"%delete%") OR like(cmd,"%remove%")))
| stats count min(_time) as first_seen max(_time) as last_seen values(cmd) as commands values(ParentImage) as parent_processes by host, User
| convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where (FileName =~ 'vssadmin.exe' and ProcessCommandLine has_all ('delete', 'shadows'))
    or (FileName =~ 'wmic.exe' and ProcessCommandLine has_all ('shadowcopy', 'delete'))
    or (FileName =~ 'wbadmin.exe' and ProcessCommandLine has_any ('delete catalog', 'delete backup', 'delete systemstatebackup'))
    or (FileName =~ 'bcdedit.exe' and ProcessCommandLine has_any ('recoveryenabled no', 'bootstatuspolicy ignoreallfailures'))
    or (FileName in~ ('powershell.exe', 'pwsh.exe') and ProcessCommandLine has 'Win32_ShadowCopy' and ProcessCommandLine has_any ('delete', 'remove'))
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine

Sigma

title: Windows Recovery Inhibition Commands (Shadow Copy and Backup Deletion)
id: 6f1d3c52-8a4b-4e07-9b21-5c3a7e90d101
status: experimental
description: Detects commands commonly run before ransomware encryption to delete volume shadow copies or backup catalogs or to disable recovery. Hunting logic for TL-2026-6348 (T1490, T1486).
references:
  - https://databreaches.net/2026/11/18/il-wilmington-school-district-209u-reports-ransomware-attack-and-possible-data-breach/
author: Threadlinqs Team
date: 2026-11-18
tags:
  - attack.impact
  - attack.t1490
  - attack.t1486
logsource:
  category: process_creation
  product: windows
detection:
  sel_vss:
    Image|endswith: '\vssadmin.exe'
    CommandLine|contains|all:
      - 'delete'
      - 'shadows'
  sel_wmic:
    Image|endswith: '\wmic.exe'
    CommandLine|contains|all:
      - 'shadowcopy'
      - 'delete'
  sel_wbadmin:
    Image|endswith: '\wbadmin.exe'
    CommandLine|contains:
      - 'delete catalog'
      - 'delete backup'
      - 'delete systemstatebackup'
  sel_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'bootstatuspolicy ignoreallfailures'
  condition: 1 of sel_*
falsepositives:
  - Backup or imaging software that prunes shadow copies
  - Administrators resizing shadow storage or reimaging devices
level: high

Known false positives:

  • Backup/imaging agents that delete old shadow copies on a schedule
  • Administrators reimaging or repurposing school laptops with vssadmin or bcdedit

Tuning notes: Allowlist the backup/imaging service accounts and management hosts (SCCM/Intune, imaging servers) by User and ParentImage. Adjust index name to your Sysmon index. Treat a hit on more than one host in an hour as a probable ransomware precursor and escalate immediately.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Password Spray Followed by Successful Logon from One Source (T1078, T1110.003) · unlock with TL Creds
  • Mass File Rename or Creation with Uniform Extension by One Process (T1486) · unlock with TL Creds
  • Exfiltration Tooling and Cloud File-Sharing Endpoints from Non-Browser Processes (T1567.002) · unlock with TL Creds
  • Suspicious PowerShell Execution from Script Host, Office or Remote Service Parent (T1059.001) · unlock with TL Creds
  • Security Tooling Tampering and Event Log Clearing (T1562.001, T1070.001) · unlock with TL Creds
  • Remote Service Installation Consistent with PsExec-Style Lateral Movement (T1021.002, T1569.002) · unlock with TL Creds
  • Ransom Note Drop - Many Note-Named Files Created by One Process (T1486) · unlock with TL Creds
  • Single Account Network Logons to Many Windows Hosts (T1021, T1078) · unlock with TL Creds

Indicators of compromise

As of 2026-11-18, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-6348.

10 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Superintendent Kevin Feeney sent a letter to staff and student families the evening of 2026-11-17 (reported 2026-11-18 by 1340 WJOL at 6:16 AM CST and by DataBreaches.net) stating: 'Today, our district experienced a ransomware attack that may have involved a data breach.' The district is working with its cyber insurance team and outside cybersecurity specialists to determine the incident's scope and extent, and states: 'At this time, we are still determining whether any personal information was accessed or affected.' If the investigation finds information requiring notification or action, the district says it will contact affected individuals directly and provide guidance.

As a containment measure, the district temporarily suspended use of district-issued laptops and other Windows devices. Internet access, Chromebooks and cell phones remain usable, and the superintendent said teaching and learning should continue with most operations proceeding normally, with some technology adjustments as staff adapt classroom activities and daily procedures. No school closures are reported. The impact concentrated on the Windows device fleet, with Chromebooks unaffected, is consistent with a Windows-domain-focused intrusion, but the sources do not state the initial access vector, the ransomware family, or any ransom demand.

EVIDENCE LIMITS: No ransomware group has claimed the attack in any source reviewed. No CVE, malware hash, IP, domain or other technical indicator has been published. The WJOL article does not report the number of people or records affected, the status of phone or email systems, or a restoration timeline. The DataBreaches.net primary source returned HTTP 403 to direct fetch; its content was corroborated via the WJOL report and search-retrieved text. Searches for a leak-site listing (e.g. ransomware.live-style trackers) or a separate district notice returned nothing about this district. Only T1486 is directly evidenced by the disclosure; the remaining MITRE mappings (T1567, T1078, T1021, T1059) are unconfirmed hunting hypotheses reflecting a typical Windows ransomware lifecycle and a possible data breach, not findings. The IOC list contains entity and platform context drawn from the reporting, not malicious network or file indicators.

MITRE ATT&CK techniques by tactic:

Lateral Movement

T1021 Remote Services

Execution

T1059 Command and Scripting Interpreter

Initial Access

T1078 Valid Accounts

Exfiltration

T1567 Exfiltration Over Web Service

Remediation

Immediate actions

  • Isolate and suspend affected Windows endpoints until forensic triage is complete
  • Engage incident response and cyber insurance carrier; preserve logs and disk/memory images
  • Reset credentials (especially domain admin and service accounts) and review MFA coverage
  • Verify offline/immutable backups are intact before any restoration

Workarounds

  • Use unaffected Chromebooks and web-based services for instruction while Windows devices are suspended

Longer-term hardening

  • Segment student, staff and administrative networks
  • Deploy EDR with behavioral ransomware detection on Windows fleet
  • Maintain tested offline backups and an incident response plan

Affected and fixed versions

  • Microsoft — Windows (district-issued laptops and other Windows devices)

Timeline

  • Superintendent Kevin Feeney sends a letter to staff and student families disclosing the incident and stating most operations and teaching and learning should continue.
  • District reports working with its cyber insurance team and outside cybersecurity specialists to determine scope and whether personal information was accessed.
  • District temporarily suspends use of district-issued laptops and other Windows devices as a precaution; internet access, Chromebooks and cell phones remain usable.
  • District states that 'today' it experienced a ransomware attack that may have involved a data breach (exact start time and initial access not disclosed).
  • As of reporting, the district is still determining whether any personal information was accessed; it will contact affected individuals directly if notification is required.
  • DataBreaches.net publishes a report on the attack and possible data breach; no ransomware group, ransom demand or leak-site claim is identified.
  • 1340 WJOL publishes the district's disclosure at 6:16 AM CST; no ransomware group, ransom demand, affected-record count or restoration timeline is reported.

Sources cited

Previous and next in ransomware

Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats