Suspicious Network Connection from fsutil or Defender Client via network_connection

PremiumReviewedSigma · Medium · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-09-17
Updated
2026-09-17

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 outbound network connections from fsutil.exe or the Defender client rmclient.exe, processes that do not normally initiate network traffic. The REMCOS watchdog component injects into these binaries to maintain a covert command-and-control channel. Such connections indicate likely process injection and should be investigated.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
Suspicious SearchIndexer Outbound Network Connection after Injection
Suspicious .NET Utility Spawned by Script Host for Process Hollowing
Malicious Agent Tesla Loader Malformed User-Agent in HTTP Traffic (via proxy)
Malicious Interlock RAT FileFix Download-Cradle via PowerShell WebClient with PowerShell User-Agent (via ps_script)
Suspicious Cobalt Strike Malleable Profile Beaconing via Legacy MSIE9 User-Agent and IE Compatibility URIs (via proxy)
Malicious Cobalt Strike Default Named Pipe Activity
Suspicious Network Connection from fsutil or Defender Client via network_connection
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.