Windows Executable Connects to portmap.io Domain Over Network

Alerts when a Windows process initiates a connection to a .portmap.io destination hostname.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-05-31
Updated
2026-07-31

ATT&CK techniques

C2 → Exfiltration
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Impact

What it detects

This rule identifies outbound network connections where a Windows process initiates communication to a destination hostname ending with .portmap.io. Such traffic may indicate command-and-control or data exfiltration attempts, especially when the destination domain is unexpected for the host. Detection relies on network connection telemetry containing the initiating process and the destination hostname.

Related detections9 linkedT1041 — drag to rearrange
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Malicious Vice Society Directory Crawling Script for Data Exfiltration - Via Ps_script (via ps_script)
Malicious PowerShell Exfiltration to webhook.site Following WSUS Exploitation
Suspicious InvisibleFerret C2 Endpoints over Port 1224 (via proxy)
Suspicious CurKeep Backdoor C2 API Endpoints (via proxy)
Suspicious DEEPPOST Data Exfiltration URI Pattern via BrazenBamboo
Suspicious Error 524 Decoy Smishing Phishing Endpoint Access (via proxy)
Suspicious COOKIE SPIDER macOS Data Exfiltration via curl Archive Upload (via process_creation)
Suspicious Watering Hole Exfiltration to Fake wp-includes Endpoint via SilentSelfie
Windows Executable Connects to portmap.io Domain Over Network
Pivot detection · T1041 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.