Windows: Unusual Child Process Spawn by dns.exe

Alerts when dns.exe launches an unexpected child process other than conhost.exe.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Tim Rauch, Elastic (idea) (SigmaHQ), DRL 1.1
Published
2022-09-27
Updated
2026-07-31

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 process creation events where the parent process name ends with '\dns.exe' and the child process is not '\conhost.exe'. Spawning unexpected children from dns.exe can indicate malicious activity, including post-exploitation behaviors, and is a useful signal for spotting exploitation or persistence attempts. It relies on Windows process creation telemetry, using parent and image path suffix matching to identify anomalous process trees.

Related detections9 linkedT1133 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Reverse SSH Tunnel Creation with Host Key Verification Disabled (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible PAN-OS CVE-2026-0257 Exploitation via GlobalProtect PoC Artifacts (via network)
Possible RD Web Access Brute Force via Repeated Login POST Requests
Suspicious Security Group Ingress Rule Opened to the Internet via CloudTrail
SplashTop Network
Suspicious SoftEther VPN Hamcore Config Written to ProgramData (via file_event)
SplashTop Process
Windows: Unusual Child Process Spawn by dns.exe
Pivot detection · T1133 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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