Possible Discord Webhook C2 or Data Exfiltration

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-10-05
Updated
2026-10-05

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 detects outbound requests to Discord webhook endpoints which threat actors repurpose as command and control channels and as a destination for exfiltrated data. Because webhooks blend into normal Discord traffic they provide a low cost covert channel for stealing information and receiving operator instructions.

Related detections9 linkedT1567 — drag to rearrange
Windows Suspicious Non-Browser Network Traffic to api.telegram.org
Linux Executable Connecting to ngrok Tunnel Service Endpoints
Windows Network Connections to ngrok Tunnel Domains Initiated by Executables
Windows Process Initiated Connections to Ngrok Domains
Suspicious Miasma npm Credential Exfiltration via Google API Client User Agent (via proxy)
Suspicious Python-Requests Exfiltration to Webhook.site (s1ngularity Aftermath)
Suspicious TeamPCP antv GitHub Commit Search C2 Trigger firedalazer (via proxy)
Malicious prt-scan Campaign Exfiltration Script prt_exfil.sh (via file_event)
Malicious TeamPCP durabletask C2 git-service and m-kosche (via dns_query)
Possible Discord Webhook C2 or Data Exfiltration
Pivot detection · T1567 · 9 related

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