Windows Process Execution via WorkFolders.exe Launching control.exe

Alerts when WorkFolders.exe spawns a non-standard control.exe instance on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Maxime Thiebaut (@0xThiebaut) (SigmaHQ), DRL 1.1
Published
2021-10-21
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation where WorkFolders.exe is the parent process and it spawns control.exe. An attacker could abuse this relationship to execute a system utility with a chosen control.exe instance, blending execution into legitimate Windows binaries. The detection relies on process creation telemetry, specifically parent and child process image paths, and matches when the child is a control.exe path that does not equal the standard C:\Windows\System32\control.exe.

Related detections9 linkedT1218 — drag to rearrange
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Malicious regsvcs LOLBin Loading Ransomware DLL from UNC Path
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Suspicious Extexport DLL Side-Loading Execution
Malicious ClickFix Execution Chain Spawning MSHTA via Pcalua on EtherRAT Infection
Suspicious TALONITE Certutil LOLBIN Decode and Download Abuse (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Windows Process Execution via WorkFolders.exe Launching control.exe
Pivot detection · T1218 · 9 related

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