Windows Registry COM InProcServer32 Hijack via PSFactory CLSID Default Value

Detects suspicious modifications to a PSFactory COM InProcServer32 (Default) registry value that may enable COM-based persistence.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
BlackBerry Threat Research and Intelligence Team - @Joseliyo_Jstnk (SigmaHQ), DRL 1.1
Published
2023-06-07
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 changes to the PSFactory COM CLSID InProcServer32 (Default) registry value. COM in-proc server hijacking can provide persistence by redirecting a CLSID to load an attacker-controlled DLL instead of the expected binary. It relies on registry set telemetry for the specific CLSID path and filters out updates that point to the known ActXPrxy.dll locations.

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 Registry COM InProcServer32 Hijack via PSFactory CLSID Default Value
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.