huntrule

Suspicious DNS queries to api.telegram.org for Telegram Bot API traffic

Flags DNS queries to api.telegram.org that may indicate Telegram Bot API usage by bots or malware.

FreeReviewedSigma · Medium · v2
Category
dns
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2018-06-05
Updated
2026-07-31
AnalysisDetection

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

  13. Exfiltration

  14. Impact

What it detects

This rule flags DNS queries for api.telegram.org, indicating potential use of the Telegram Bot API by a bot, script, or application. Attackers can leverage the Bot API for command-and-control or message-based exfiltration while blending in with legitimate bot traffic. It relies on DNS telemetry that records queried domain names and matches the specific host api.telegram.org.

Reporting behind it

Related detections9 linkedT1102.002 — drag to rearrange
Malicious Dropbox Cloud C2 via Spoofed Googlebot User Agent
Suspicious UNC1549 Azure C2 Beacon to News Notifications URI Pattern (via proxy)
Suspicious Project CAV3RN AzureCommunication.dll Load (via image_load)
Suspicious Google API DNS Query From Temporary Directory Process Abused for C2
Malicious OilRig OAuth Application Sign-In via Azure (via azure)
Suspicious Instant Messenger Client Spawning Script Interpreter (via process_creation)
Suspicious Project CAV3RN logAzure.txt Configuration Drop (via file_event)
Windows GitHub Self-Hosted Runner Execution via Runner.Worker and Runner.Listener
Windows Network Connections to azurefd.net Excluding Common Browsers and Known Front Door Hostnames
Suspicious DNS queries to api.telegram.org for Telegram Bot API traffic
Pivot detection · T1102.002 · 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.