Windows Process Creation: Execution of Renamed curl.exe via PE Metadata

Alerts on Windows process launches whose PE metadata matches curl.exe even when the executable image is renamed.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-09-11
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 executions where PE metadata indicates the OriginalFileName is "curl.exe" and the process image contains "\curl", suggesting an impersonation or renamed binary. Attackers may rename legitimate utilities like curl.exe to blend into normal tooling while still leveraging its functionality. The detection relies on process creation telemetry that includes PE metadata fields (OriginalFileName and Description) and the created process image path.

Related detections9 linkedT1059 — drag to rearrange
Windows Execution of Renamed NirCmd.exe (nircmd.exe/nircmdc.exe) via PE OriginalFileName
Windows: Detect renamed PingCastle binary execution via PE metadata and scanner command-line
Windows: Detect ftp.exe Executed With -s or /s for Script-Based Command Execution
Windows Renamed ftp.exe Execution via OriginalFileName PE Metadata
Windows: Detect Runscripthelper.exe executing PowerShell scripts with 'surfacecheck'
Windows Process Creation: Outlook EnableUnsafeClientMailRules Security Setting Enabled
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Windows Process Creation: Execution of Renamed curl.exe via PE Metadata
Pivot detection · T1059 · 9 related

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