Suspicious Assembly Execution via Regasm or Regsvcs From a User Path (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-25
Updated
2026-08-28

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects regasm.exe or regsvcs.exe executing an assembly from a user, temp or ProgramData directory, a signed-binary proxy technique that runs attacker .NET code through a trusted registration utility. Regasm and Regsvcs abuse is a defense-evasion technique in the Red Canary Threat Detection Report. Detecting execution from user-writable paths surfaces trusted-binary code proxying.

Related detections9 linkedT1218.009 — drag to rearrange
Suspicious RegAsm Execution Spawned by Script Interpreter (via process_creation)
Suspicious Proxy Execution via RegAsm or RegSvcs (via process_creation)
Suspicious CloudZ RAT Loader Execution via regasm.exe LOLBin
Malicious CloudZ RAT Persistence via schtasks Running regasm.exe
Suspicious Outbound Connection From CasPol Binary
Suspicious CasPol Execution Spawned by PowerShell for Injection
Suspicious PowerShell Spawning .NET LOLBIN (via process_creation)
RegAsm.exe Process Execution Missing Command-Line and Assembly Path (Windows)
Windows RegAsm.exe Initiates Network Connection to Public IP
Suspicious Assembly Execution via Regasm or Regsvcs From a User Path (via process_creation)
Pivot detection · T1218.009 · 9 related

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