Possible Telegram Bot API Command and Control Traffic

PremiumReviewedSigma · Low · v1
Category
proxy
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

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 detects requests to the Telegram Bot API sendDocument and getUpdates methods which the Dark Pink APT uses to exfiltrate stolen files and receive commands through api.telegram.org. Routing C2 over a trusted messaging service blends malicious traffic with legitimate flows. It matters because it can reveal data theft hidden inside allowed cloud services.

Related detections9 linkedT1071.001 — drag to rearrange
SquidLoader C2 Beacon via Kubernetes-Themed URI and Legacy Trident User-Agent (via proxy)
Malicious Fake Converter Beacon Command-and-Control to confetly Endpoints (via proxy)
Malicious Matanbuchus C2 Beacon via Spoofed Skype User-Agent (via proxy)
IDAT Loader C2 Notification via sendNotification.php (via proxy)
EtherRAT C2 Beacon via Fixed GUID Query Parameter (via proxy)
Suspicious Kimsuky C2 Retrieval via list.php query Pattern (via proxy)
APT28 Roundcube XSS Beacon via zJ2w9x Telemetry Endpoint (via webserver)
Masquerading jQuery-Masquerading C2 Request with Spoofed Referrer via proxy (via proxy)
IDAT Loader Connectivity Check via Short racon User-Agent (via proxy)
Possible Telegram Bot API Command and Control Traffic
Pivot detection · T1071.001 · 9 related

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