huntrule

Suspicious COM Hijack Via InprocServer32 Modification

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-09-12
Updated
2026-09-12
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 detects modification of a CLSID InprocServer32 registry value that points to a DLL in a user-writable directory. UAT-5647 hijacked COM objects by rewriting InprocServer32 CLSID keys to load RomCom components for persistence. Redirecting an InprocServer32 default value to an attacker DLL causes trusted applications to load malicious code providing stealthy persistence and execution.

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
Suspicious COM Hijack Via InprocServer32 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.