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 IIS Worker Process Spawning Command Shell Reconnaissance
Possible Citrix ShareFile Unauthenticated Upload Path Traversal Webshell (CVE-2023-24489) (via webserver)
Possible Unauthenticated Admin Creation in Dynamicweb CVE-2022-25369
Possible DotCMS Path Traversal Webshell Upload via content API CVE-2022-26352
Possible Avaya Aura Device Services WebDAV PHP Webshell Upload via PhoneBackup (via webserver)
Possible DotCMS Arbitrary File Upload and JSP Webshell Drop via api content (via webserver)
Malicious Dynamicweb Unauthenticated Administrator Creation via Setup Default.aspx (via webserver)
Possible PHP Webshell Access After Malicious ZIP Upload (via webserver)
Possible Oracle Opera CGI Webshell Command Execution via operabin
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.