dfsvc.exe Initiated Network Connection to Uncommon Ports (Windows)

Alerts on dfsvc.exe-initiated outbound connections targeting non-standard ports on Windows, excluding typical 80/443 and IPv6 DNS(53).

FreeReviewedSigma · High · v5
Product
windows
Category
network_connection
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-06-12
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags instances where dfsvc.exe initiates an outbound network connection to a destination port other than 80 or 443. Such behavior matters because dfsvc.exe handling ClickOnce-related functionality could be abused for unexpected external communication. The detection relies on Windows network connection telemetry indicating an initiated connection, the process image path ending in \dfsvc.exe under the .NET directory, and the destination port, with optional handling for IPv6 DNS traffic to port 53.

Related detections9 linkedT1203 — drag to rearrange
Malicious Script Execution from WinRAR Extraction Directory via CVE-2023-38831
Suspicious Execution From WinRAR Temporary Extraction Path via Command Line (via process_creation)
Malicious Shell Execution via Foomatic-rip Print Filter through CUPS Exploit
Suspicious Network Connection From CUPS Foomatic-Rip Child Process
Antivirus signatures matching APT malware naming patterns
Antivirus Remote Access Tool Signature Matches Known RAT Names
Malicious Microsoft Word Spawning Anomalous Child Process via CVE-2023-36884 (via process_creation)
Possible ExifTool CVE-2026-3102 Command Injection via Child Process Spawn (via process_creation)
Malicious Equation Editor Child Process Execution via process_creation
dfsvc.exe Initiated Network Connection to Uncommon Ports (Windows)
Pivot detection · T1203 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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