Windows Process Creation: wfc.exe Execution for Workflow Command-line Compiler Abuse

Alerts on execution of wfc.exe by matching process image and OriginalFileName in Windows process creation logs.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Christopher Peacock @SecurePeacock, SCYTHE @scythe_io (SigmaHQ), DRL 1.1
Published
2022-06-01
Updated
2026-07-30

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags process creation events where the executed binary is wfc.exe, identified by filename and OriginalFileName. wfc.exe can be abused to execute actions under the guise of a legitimate Windows workflow-related compiler component, which may help attackers blend in with normal software activity. It relies on process creation telemetry containing the process image path and the OriginalFileName field.

Related detections9 linkedT1127 — drag to rearrange
Suspicious Code Compilation via Aspnet_compiler LOLBIN (via process_creation)
ArcSOC.exe Creates Suspicious Script/Executable Files on Windows
Suspicious Child Process of aspnet_compiler.exe on Windows
Suspicious aspnet_compiler.exe Execution from User or Temp Paths on Windows
Windows: Detect kavremover-related LOLBIN command-line usage
Windows node.exe Execution with -e/--eval and suspicious child process usage
Windows: Process creation involving VSIISExeLauncher.exe with -p and -a arguments
Windows Process Creation: Mftrace.exe Child Process Execution
Windows Process Creation: Remote.exe Execution
Windows Process Creation: wfc.exe Execution for Workflow Command-line Compiler Abuse
Pivot detection · T1127 · 9 related

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