huntrule

Windows DNS Queries Initiated by Regsvr32.exe

Flags DNS queries made by regsvr32.exe based on the querying process image path.

FreeReviewedSigma · Medium · v2
Product
windows
Category
dns_query
Author
Dmitriy Lifanov, oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-25
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags DNS query activity where the initiating process image path ends with \regsvr32.exe. Attackers may misuse regsvr32.exe to blend into legitimate Windows execution while generating outbound name resolution. The detection relies on DNS query telemetry that includes the requesting process image associated with the DNS event.

Reporting behind it

Related detections9 linkedT1218.010 — drag to rearrange
Windows Regsvr32.exe Initiated Network Connection
Malicious Regsvr32 Loading Masqueraded VPN DLL via Process Creation
Malicious Regsvr32 ShellExec_RunDLL Proxy Execution (via process_creation)
Suspicious DLL Execution via Regsvr32 DllInstall of dat File
Malicious Xctdoor XcLoader Execution via Regsvr32 AppX Path Abuse (via process_creation)
Malicious Office Application Loading a User-Path DLL via Regsvr32 or Rundll32 (via process_creation)
Masquerading SSLoad PhantomLoader DLL Execution via Regsvr32 Silent Load from AppData (via process_creation)
Malicious Kimsuky AlphaSeed Payload Execution via Regsvr32 Loading edge dat (via process_creation)
Malicious Regsvr32 Executing DLL From Windows Temp
Windows DNS Queries Initiated by Regsvr32.exe
Pivot detection · T1218.010 · 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.