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

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  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 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.

Related detections9 linkedT1546.015 — drag to rearrange
Suspicious COM Hijack of ClickOnce Deployment Service CLSID (via registry_set)
Suspicious COM Hijack Via InprocServer32 Modification
Malicious COM Hijacking via TinyTurla CLSID InprocServer32 (via registry_set)
Suspicious dllhost.exe Spawned with CLSID and Anomalous Parent (via process_creation)
Suspicious COM Handler Hijack of MsCtfMonitor CLSID via CharmingCypress
Malicious COM Hijack of PSFactoryBuffer InprocServer32
Malicious APT-C-60 COM Hijack via SpyGlace CLSID InProcServer32 (via registry_set)
Malicious COM Hijack via CLSID InProcServer32 Registry Modification (via registry_set)
Malicious COM Object Hijack Pointing to a User-Writable DLL (via registry_set)
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.