Windows Suspicious Non-Browser Network Traffic to api.telegram.org

Alerts on Windows network connections to api.telegram.org by processes other than common web browsers.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-05-19
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 flags outbound network connections from processes on Windows whose destination contains api.telegram.org when the initiating process is not one of several known browser and web-view executables. Attackers commonly use messaging APIs like Telegram to blend into normal traffic while acting as command-and-control or for data transfer. It relies on Windows network connection telemetry and process image path information to exclude typical browser activity.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Payload Retrieval from Cloudflare Tunnel via LOLBin (via process_creation)
Suspicious Malware Delivery via Discord CDN Attachment
Linux network connections to ngrok tunneling endpoints
Windows Executable Initiating Connections to ngrok Tunnel Domains
Linux: Suspicious curl upload via form or data flags
Windows Process Initiated Connections to Ngrok Domains
Windows: Detect curl.exe upload/data flags indicative of possible exfiltration
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Windows Suspicious Non-Browser Network Traffic to api.telegram.org
Pivot detection · T1105 · 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.