ClawHub
Back to skill

Security audit

Openclaw Telegram Setup

Security checks across malware telemetry and agentic risk

Overview

This is a manual Telegram setup guide for OpenClaw with expected bot-token handling risks but no hidden code or deceptive behavior.

Install only if you intend to connect Telegram to OpenClaw. Treat the Telegram bot token like a password, restrict allowedChatIds to trusted chats, keep ~/.openclaw/config.yaml out of version control, rotate the token if it was exposed, and use webhook mode only on infrastructure and HTTPS settings you control.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The guide instructs users to obtain and handle a Telegram bot token, but does not clearly identify it as a secret credential that must never be shared, logged, or committed. Bot tokens grant control of the bot API, so disclosure could let an attacker read updates, send messages as the bot, or reconfigure integrations depending on the plugin behavior.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The documentation tells users to place the bot token directly into a local YAML config file without any guidance on file permissions, encryption, or safer secret storage. Storing long-lived credentials in plaintext increases the chance of exposure through backups, shared machines, misconfigured home directories, or accidental repository commits.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.