Security audit

Telegram Bot Factory

Security checks for vulnerabilities and agentic risk

Overview

This is a simple Telegram bot development guide with disclosed bot categories and no hidden execution, persistence, or data-access behavior in the artifact.

Before using this skill for a real bot, be careful with bot tokens, payment keys, trading credentials, moderation powers, and user analytics data. The skill itself is benign, but the bots it helps create may need explicit user consent, scoped permissions, secure secret handling, and testing before deployment.

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

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
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 (1)

Natural-Language Policy Violations

Medium

Confidence: 95% confidence
Finding: The natural-language content is presented entirely in Traditional Chinese mixed with some English terms, and the file does not indicate that users may choose another language. Under the policy, forcing a specific language without opt-in is a locale/language policy violation unless the restriction is clearly documented and justified.

Static analysis

No suspicious patterns detected.