Windows DHCP Server Loaded Callout DLL via Registry

Flags DHCP Server events where a registry-specified callout DLL is loaded (Event ID 1033), indicating potential persistence or execution.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Dimitrios Slamaris (SigmaHQ), DRL 1.1
Published
2017-05-15
Updated
2026-07-31

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 identifies a Windows DHCP Server event where a specified callout DLL is loaded, based on registry-related configuration. Attackers may use callout DLL loading in the DHCP Server context to persist, execute, or maintain stealthy network-related behavior. Detection relies on Windows System telemetry, specifically an EventID 1033 from the Microsoft-Windows-DHCP-Server provider.

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious Service DLL Hijack of IKEEXT or PrintNotify
Malicious PowerShell Spawned by Masqueraded NVIDIA GeForce Experience Binary
Suspicious msimg32.dll Loaded from Non-System Directory
DLL Side-Loading via Signed Binary Loading Known Malicious Helper DLL
Suspicious DLL Sideloading via msdtc oci.dll Install (via process_creation)
Suspicious wmicodegen.dll Sideload by inetinfo.exe (UAT-8099 Cobalt Strike)
Suspicious LucidRook DismCore.dll Side-Load into Browser Process
Suspicious Encrypted Implant File Creation for DLL Search Order Hijacking (RainyDay Turian PlugX)
Suspicious RoboForm Signed Binary Executed From Non-Standard Path (via process_creation)
Windows DHCP Server Loaded Callout DLL via Registry
Pivot detection · T1574.001 · 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.