huntrule

Windows Windefend: Defender Restored File from Quarantine (EventID 1009)

Alerts on Windows Defender Windefend events indicating an item was restored from quarantine (Event ID 1009).

FreeReviewedSigma · High · v2
Product
windows
Service
windefend
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-12-06
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows Microsoft Defender (Windefend) events where the antimalware platform restored an item from quarantine. Attackers and defenders both may trigger this when artifacts are moved back to active locations after being quarantined, so repeated or unexpected restorations can indicate defense impairment or operational recovery. It relies on Windefend telemetry, specifically EventID 1009, to identify the restore action.

Reporting behind it

Related detections9 linkedT1685 — drag to rearrange
Suspicious SELinux Enforcement Disabled via Setenforce Command Line (via process_creation)
Suspicious SELinux and Firewall Disabling on Linux by Cryptominer (via process_creation)
Suspicious Windows Defender Exclusion of User Profile via PowerShell (via process_creation)
Malicious Vulnerable Driver Service Creation for BYOVD (via process_creation)
Malicious Microsoft Defender Disabled via Registry DisableAntiSpyware (via process_creation)
Suspicious Termination of Defender Tray Process via Taskkill
Malicious Windows Defender Disablement via MpCmdRun RemoveDefinitions
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Windows Windefend: Defender Restored File from Quarantine (EventID 1009)
Pivot detection · T1685 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.