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 SearchIndexer Outbound Network Connection after Injection
Suspicious Data Exfiltration Channel to Telegram or Discord via dns_query
Malicious C2 Domain Beacon To Akamaitechnologies Masquerade via DPRK Python Intrusion
Malicious WmRAT C2 Beacon via excerorderslist Endpoint (via proxy)
Malicious DarkGate C2 Communication via Synapse User-Agent (via proxy)
Suspicious APT29 Zulip C2 Communication via curl User-Agent (via proxy)
Suspicious PowerShell Interaction with ProgramData SysInt Log via Process Creation
Malicious NPM Backdoor C2 Beacon to Injective Telemetry Endpoint via Proxy
Suspicious C2 Beacon with Legacy MSIE User Agent
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.