Suspicious AddInProcess32 Outbound Connection after Process Hollowing

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 dotnet AddInProcess32 utility initiating outbound network connections which is highly unusual. Ande Loader hollowed 0bj3ctivity Stealer into AddInProcess32 so its C2 and exfiltration traffic run under a signed process. External connections from this rarely used binary indicate injected stealer activity.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
Suspicious Network Connection from fsutil or Defender Client via network_connection
Suspicious SearchIndexer Outbound Network Connection after Injection
Suspicious Bash Reverse Shell via Dev TCP Redirection
Malicious TeamPCP antv Backup C2 Domain m-kosche (via dns_query)
Malicious Axios npm Compromise C2 Beacon to sfrclak and callnrwise (via dns_query)
Malicious TeamPCP durabletask C2 git-service and m-kosche (via dns_query)
Possible PowerShell Empire Default C2 URI Beaconing
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Pivot detection · T1071.001 · 9 related

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