Linux network connections to known malware callback ports

Alerts on initiated Linux outbound connections to specific known suspicious destination ports, excluding local/private IP ranges.

FreeReviewedSigma · High · v3
Product
linux
Category
network_connection
Author
hasselj (SigmaHQ), DRL 1.1
Published
2024-05-10
Updated
2026-07-31

ATT&CK techniques

C2
  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. Exfiltration

  13. Impact

What it detects

This rule flags Linux processes that initiate outbound network connections to specific destination ports associated with known malware callback activity. Attackers use callback ports to establish command-and-control channels and maintain persistent remote access. It relies on network connection telemetry capturing connection initiation status along with destination IP and destination port, excluding local/private address ranges to reduce noise.

Related detections7 linkedT1571 — drag to rearrange
Suspicious Outbound Connection To MoonPeak C2 High Ports
Possible Remcos C2 Connection from eilowutil Process
Malicious UNC4841 SSH Backdoor Persistence via Non-Standard Port and AllowUsers Restriction (via process_creation)
Malicious Reverse Shell via socat
Windows PowerShell Scripts Testing Uncommon Port Connectivity via Test-NetConnection
Windows Network Connections to Known Malware Callback Ports (Suspicious Destination Ports)
Windows Network Connections to Uncommon Ports (8080, 8888)
Linux network connections to known malware callback ports
Pivot detection · T1571 · 7 related

Changelog

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