huntrule

Windows Registry Set: ServiceDll Path Ending with \CurrentControlSet\Services\wercplsupport\Parameters\ServiceDll

Alerts on Windows registry writes to a specific Services\wercplsupport\Parameters\ServiceDll target path.

FreeReviewedSigma · High · v5
Product
windows
Category
registry_set
Author
Trent Liffick (@tliffick) (SigmaHQ), DRL 1.1
Published
2020-05-14
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 identifies registry modifications on Windows where the recorded target object ends with a specific ServiceDll parameter path under the CurrentControlSet. Attackers commonly use ServiceDll values to influence what code a service loads, enabling persistence or defense evasion. The detection relies on registry set event telemetry that includes a TargetObject field.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Windows WMIC Registry Changes via WMI StdRegProv Write Methods
Windows Persistence Attempt via sc config or wmic COR_PROFILER (Blue Mockingbird)
Lateral Movement via WMIC Remote Process Creation
Malicious Enabling of Restricted Admin Mode via Registry by UAT-8837
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Suspicious Loopback Proxy Server Configured via Registry (via registry_set)
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Malicious UAT-8302 Remote Process Execution via wmic
Windows Registry Set: ServiceDll Path Ending with \CurrentControlSet\Services\wercplsupport\Parameters\ServiceDll
Pivot detection · T1112 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.