ClawHub
Back to skill

Security audit

Telegram

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only Telegram bot workflow skill whose network and token handling are expected for its purpose.

Before using this skill, keep Telegram bot tokens and webhook secret tokens out of logs, commits, and shared prompts, and only send message content to Telegram that your bot is intended to process.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

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)

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/telegram-bot-api.md (reported line 4)May include surrounding context.

md
# Telegram Bot API Field Notes

## 1) Base URL and request style
- Base format: `https://api.telegram.org/bot<token>/<method>`
- Use GET or POST with JSON or form-encoded payloads.
- File uploads use `multipart/form-data` and `attach://` references.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

This markdown file documents a network-facing webhook setup and shows a secret_token field, but it provides no warning that the value is sensitive and should not be hardcoded, shared, or committed. For markdown files, missing disclosures about behaviors affecting privacy or system integrity should be flagged when absent.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.