Windows: Suspicious Child Processes Spawned by sqlservr.exe

Alerts when SQL Server (sqlservr.exe) spawns suspicious command/system tools on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
FPT.EagleEye Team, wagga (SigmaHQ), DRL 1.1
Published
2020-12-11
Updated
2026-07-30

ATT&CK techniques

Initial Access → Persistence
  1. Recon

  2. Resource Dev

  3. Execution

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows process creation events where the parent process is Microsoft SQL Server (sqlservr.exe) and the child process matches a set of commonly used command execution and system interrogation utilities. Such behavior can indicate attempts to establish access, escalate privileges, or leverage SQL Server execution paths for further activity. It relies on process creation telemetry with parent and child image paths and, in one optional case, command-line context to exclude a specific known pattern.

Related detections9 linkedT1190 — drag to rearrange
Malicious Web Shell Written to SharePoint LAYOUTS Directory by Worker Process (via file_event)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Possible GoAnywhere MFT Exploitation via Tomcat Spawning Discovery Commands
Suspicious Command Shell Spawned by MSSQL Server Process Indicating Webshell
Malicious MOVEit Transfer Exploitation via X-siLock HTTP Headers (via webserver)
Malicious IIS w3wp Worker Spawning Command Interpreter via SharePoint Web Shell
Suspicious Single-Character Named Executable Launched by Web Server Process (via process_creation)
Malicious MOVEit human2.aspx Web Shell Dropped in wwwroot (via file_event)
Malicious IIS Worker Process Spawning PowerShell via Gladinet CentreStack Exploit
Windows: Suspicious Child Processes Spawned by sqlservr.exe
Pivot detection · T1190 · 9 related

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