Windows Process Creation: WinAPI Function Names in Command-Line

Alerts on Windows processes whose command lines reference WinAPI functions/modules commonly used for dynamic invocation and memory/process manipulation.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-06
Updated
2026-07-30

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process creation events where the command line contains multiple WinAPI-related function or module names (e.g., kernel32, ntdll, LoadLibrary, GetProcAddress, OpenProcess, VirtualAlloc). Attackers may use these API references to load functions dynamically, manipulate tokens/processes, or perform in-memory operations during execution. The detection relies on process creation telemetry with access to the full command line string.

Related detections9 linkedT1106 — drag to rearrange
Nullsoft Scriptable Installer Script (NSIS) execution
Nullsoft Scriptable Installer Script (NSIS) file creation
Windows PowerShell ScriptBlock keyword match for WinPwn tool usage
Windows process command line matches WinPwn tool execution keywords
PowerShell Scripts Calling WinAPI DLLs on Windows
Windows PowerShell ScriptBlock WinAPI Function Calls
Linux auditd: BPFDoor .pid or .lock file access in /var/run
Windows HandleKatz: Duplicate LSASS Handle via Process Access with Handle Duplication Rights
Windows process access matching Cobalt Strike BOF injection call trace
Windows Process Creation: WinAPI Function Names in Command-Line
Pivot detection · T1106 · 9 related

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