Back to skill

Security audit

Lovefromio Telegram

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only Telegram bot helper skill whose external API use and token handling are expected for its stated purpose.

Before installing, be prepared to handle Telegram bot tokens and webhook secrets securely: keep them out of logs and source control, restrict allowed update types, and review any generated bot code before sending messages or changing webhook settings.

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
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
Content
# 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.
Confidence
50% confidence
Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Missing User Warnings

Low
Confidence
82% confidence
Finding
This markdown file documents a request template containing a `secret_token`, which is credential-like sensitive data used to authenticate webhook requests. The section provides no warning not to hardcode, expose, or share the token, despite the category requiring warnings for behaviors affecting privacy or system integrity.

Static analysis

No suspicious patterns detected.