Suspicious Data Exfiltration to Telegram Bot API sendDocument (via proxy)

ATT&CK techniques

Exfiltration

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
- T1567.002Exfiltration to Cloud Storage
Impact

What it detects

This rule detects HTTP requests to the Telegram Bot API sendDocument endpoint, the exfiltration channel used by 0bj3ctivityStealer to upload harvested credentials and wallet data as documents to an attacker-controlled bot. Adversaries leverage Telegram as a resilient exfiltration service that blends with legitimate traffic, making detection of bot document uploads useful for exposing data theft.

Reporting behind it

Related detections9 linkedT1567.002 — drag to rearrange

Suspicious Data Exfiltration via Rclone Cloud Transfer (via process_creation)

Suspicious Data Exfiltration to Dropbox via curl (via process_creation)

Suspicious Lambda Function Creation Across Regions in AWS Extortion Operation

Malicious Data Exfiltration via Renamed Rclone Using Masqueraded Configuration

Suspicious Cloud Exfiltration via Rclone

Suspicious Rclone Cloud Sync Execution for Data Exfiltration via Command Line

Suspicious Data Exfiltration via MEGAsync (via process_creation)

Malicious Data Exfiltration via MinIO Client from Windows Temp

Suspicious Data Exfiltration to Backblaze B2 via rclone (via process_creation)

Suspicious Data Exfiltration to Telegram Bot API sendDocument (via proxy)

Pivot detection · T1567.002 · 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 →