Suspicious COM Hijack via CLSID InprocServer32 Pointing to Writable Path (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-05-29
Updated
2026-08-28

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 detects a CLSID InprocServer32 registry value being pointed at a DLL in a user-writable directory such as Temp, AppData or ProgramData. VanHelsing hijacks COM objects by redirecting their server registration to attacker-controlled files, so a CLSID handler in a writable path indicates persistence via COM hijacking.

Related detections9 linkedT1546.015 — drag to rearrange
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)
Malicious COM Object Hijack Pointing to IconCache DLL
Windows COM CLSID Hijacking via Registry Default InprocServer32/LocalServer32 Modification
Windows Registry COM InProcServer32 Hijack via PSFactory CLSID Default Value
Suspicious COM Hijack via CLSID InprocServer32 Pointing to Writable Path (via registry_set)
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.