Windows: cmstp.exe Loading DLL/OCX from Suspicious Paths

Alerts when cmstp.exe loads DLL/OCX from suspicious directories on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
image_load
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-30
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  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 identifies executions where cmstp.exe loads a DLL or OCX from paths commonly abused for stealth, such as PerfLogs, ProgramData, Users, and temporary directories. Attackers can leverage the signed cmstp.exe binary as a proxy to load attacker-controlled libraries from unusual locations. The detection relies on image load telemetry that records the loaded module path (ImageLoaded) and the loading process (Image).

Related detections9 linkedT1218.003 — drag to rearrange
CMSTP Execution of an INF Profile (via process_creation)
Suspicious CMSTP Execution With INF Payload via process_creation
CMSTP UAC Bypass via Automatic Install Flag (via process_creation)
Windows Network Connection from Cmstp.EXE (Outbound)
Windows: Command-line execution of cmstp.exe with INF install/silent/autobind flags (UAC bypass pattern)
Windows CMSTP UAC Bypass Attempt via Autoelevate COM Object DllHost Execution
Windows Process Access to cmlua.dll by CMSTP Connection Manager Profile Installer
Windows CMSTP Process Spawning Child Process
Windows Registry Events: CMSTP Execution via cmmgr32.exe TargetObject
Windows: cmstp.exe Loading DLL/OCX from Suspicious Paths
Pivot detection · T1218.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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