Security Audit

telegram-topic-rename

github.com/openclaw/skills

AI SkillCommit 13146e6a3d46

TRUSTED

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

telegram-topic-rename received a trust score of 90/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.

SkillShield's automated analysis identified 1 finding: 0 critical, 1 high, 0 medium, and 0 low severity. Key findings include Untrusted input used in truncated curl command.

The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.

Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

85%

Behavioral Risk Signals

Network Access

1 finding

Shell Execution

1 finding

Dynamic Code

1 finding

Security Findings1

Severity	Finding	Layer	Location
HIGH	Untrusted input used in truncated curl command The script `scripts/rename-topic.sh` directly assigns untrusted command-line arguments (`$1`, `$2`, `$3`, `$4`) to variables (`CHAT_ID`, `THREAD_ID`, `NAME`, `ICON`). These variables are then intended for use in a `curl` command to interact with the Telegram Bot API. The construction of this `curl` command is truncated in the provided content, making it impossible to verify if these user-controlled inputs are properly quoted and escaped. Without proper sanitization, an attacker could potentially inject arbitrary shell commands by crafting malicious input for `new_name` or `icon` if these variables are used unquoted or in a context that allows shell metacharacters to be interpreted (e.g., within `eval`, backticks, or as unquoted arguments to `curl`). Ensure all user-supplied inputs (`$CHAT_ID`, `$THREAD_ID`, `$NAME`, `$ICON`) are properly quoted and escaped when used in the `curl` command. If constructing a JSON payload, use a tool like `jq` to safely build the JSON. If using form data, ensure `curl`'s `-F` or `--data-urlencode` options are used correctly. Avoid `eval` or direct interpolation of untrusted input into command strings.	LLM	scripts/rename-topic.sh:59

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/8d67d6944dace72e.svg)](https://skillshield.io/report/8d67d6944dace72e)