Suspicious RegAsm or AppLaunch Outbound Connection after Injection

PremiumReviewedSigma · High · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-09-20
Updated
2026-09-20

ATT&CK techniques

Priv Esc → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. Exfiltration

  11. Impact

What it detects

This rule detects the RegAsm or AppLaunch dotnet utilities making outbound internet connections. AsyncRAT was injected into these signed binaries so its RC4 encrypted C2 traffic originates from a trusted image. Neither utility normally reaches external hosts so outbound traffic indicates injected malware beaconing.

Related detections9 linkedT1055.012 — drag to rearrange
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious Network Connection from fsutil or Defender Client via network_connection
Suspicious SearchIndexer Outbound Network Connection after Injection
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 DotNet Utility MSBuild RegAsm RegSvcs Network Beacon Indicating Hollowing
Suspicious SearchProtocolHost Network Connection Indicating Process Hollowing
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
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.