Possible Telegram API Command and Control DNS Query

ATT&CK techniques

C2

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
- T1102Web Service
Exfiltration
Impact

What it detects

This rule detects DNS resolution of api.telegram.org, the endpoint used by YoroTrooper for Telegram-based command-and-control and data exfiltration. Multiple threat actors abuse the Telegram Bot API as a resilient web-service C2 channel. Because legitimate applications also use Telegram, this signal is provided at low confidence and should be correlated with other host activity.

Reporting behind it

Related detections9 linkedT1102 — drag to rearrange

Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)

Possible ITG05 Headlace Staging via Mocky and Mockbin Services (via proxy)

PowerShell Remote Download From Bunny CDN Host

Suspicious DNS Query for TryCloudflare Tunnel Abused for Malware Delivery (via dns_query)

Possible Access-Code Validation Beacon to Malware Delivery C2 (via proxy)

Suspicious Payload Retrieval from Cloudflare Tunnel via LOLBin (via process_creation)

Suspicious Malware Delivery via Discord CDN Attachment

Suspicious PowerShell Communication with Dropbox API (via ps_script)

Possible Telegram Bot API Command and Control Channel

Possible Telegram API Command and Control DNS Query

Pivot detection · T1102 · 9 related

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

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →