huntrule

Windows COM CLSID Hijacking via Registry Default InprocServer32/LocalServer32 Modification

Detects registry changes to COM CLSID Default InprocServer32/LocalServer32 values that point to suspicious locations.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-07-16
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  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 Windows registry writes where the TargetObject path contains a CLSID and the Default value under InprocServer32 or LocalServer32 is targeted. Altering these default COM server locations can redirect COM activation to attacker-controlled code, enabling persistence or privilege escalation. It relies on registry_set telemetry, matching the CLSID registry path structure and suspicious value destinations within user-writable or commonly abused locations such as AppData, Temp, Startup, and Perflogs.

Reporting behind it

Related detections9 linkedT1546.015 — drag to rearrange
Malicious SnipBot COM Hijack via InprocServer32 CLSID (via registry_set)
Suspicious COM Hijack via InprocServer32 Pointing to AppData DLL via registry_set
Malicious COM TypeLib Hijack via Persistence CLSID Registration
Malicious COM Hijacking via Twinapi CLSID InprocServer32 Registration
Suspicious Child Process Spawned by Control Panel DCOM Surrogate
Suspicious MDaemon WorldClient CgiBase6 Extension Registration by Careto
Malicious APT-C-60 COM Hijack via CLSID 566296fe InProcServer32 (via registry_set)
Malicious DarkMe COM Object Execution via rundll32 CLSID
Malicious Sednit COM Hijacking Persistence via InprocServer32
Windows COM CLSID Hijacking via Registry Default InprocServer32/LocalServer32 Modification
Pivot detection · T1546.015 · 9 related

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