Suspicious RegAsm Spawned as Process Hollowing Target

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-21
Updated
2026-09-21

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects RegAsm.exe launched as a child of script hosts such as wscript, cscript or powershell, a process hollowing target abused by SwaetRAT and Ande Loader to run injected code under a signed .NET utility. RegAsm normally runs during development, so execution from a scripting parent indicates injection rather than legitimate assembly registration.

Related detections9 linkedT1055.012 — drag to rearrange
Suspicious SearchIndexer Process Started by Non-Service Parent for Hollowing
Suspicious Browser Updater Binary Spawned by AutoIt for Process Hollowing
Suspicious DotNet Utility Spawned by Script Host for Process Hollowing via Command Line
Suspicious Outbound Network Connection from msiexec.exe (via network_connection)
Suspicious Outbound Connection from tracerpt.exe after Process Hollowing (via network_connection)
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
Suspicious DotNet Utility MSBuild RegAsm RegSvcs Network Beacon Indicating Hollowing
Suspicious RegAsm Spawned as Process Hollowing Target
Pivot detection · T1055.012 · 9 related

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