Suspicious Outbound Connection from sihost Consistent with In2al5d Loader Injection (via network_connection)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-11-10
Updated
2026-11-10

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 an outbound external network connection initiated by sihost.exe, a Windows shell host that does not normally communicate with remote hosts, consistent with the In2al5d loader hollowing sihost to run its injected payload. Adversaries leverage injection into a benign system process so beacon traffic originates from a trusted image, making early detection critical for exposing the loader before its final payload contacts command-and-control.

Related detections9 linkedT1055.012 — drag to rearrange
In-Memory Shadow Vector Process Hollowing Target AddInProcess32 Execution (via process_creation)
In-Memory Ransomware Process Hollowing Target defrag.exe Spawned by Unusual Parent (via process_creation)
WerFault Spawned by Internet Explorer as Cobalt Strike Injection Target (via process_creation)
Suspicious .NET Utility Spawned by Script Host for Process Hollowing
Suspicious MSBuild Spawned by PowerShell (via process_creation)
Suspicious RegSvcs Execution Spawned by Script Interpreter for Process Hollowing (via process_creation)
Suspicious MSBuild Execution Spawned by PowerShell via PhantomVAI Loader (via process_creation)
Suspicious Rundll32 Loading Non-DLL Image Extension File
Suspicious MSBuild Execution Spawned by Command Shell for Process Hollowing (via process_creation)
Suspicious Outbound Connection from sihost Consistent with In2al5d Loader Injection (via network_connection)
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.