ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Telegram Telethon CLI

v1.0.0

Manage Telegram via tgctl-telethon CLI (Python/Telethon) - send/forward/edit/delete/pin messages, search, list chats/members, join/leave groups, kick/invite...

⭐ 0· 48·0 current·0 all-time
by@youziyouzishu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
SKILL.md describes a Telethon-based tgctl CLI that requires TELEGRAM_API_ID and TELEGRAM_API_HASH and creates local session files. The registry metadata, however, declares no required env vars or config paths. The install script expects a local 'tgctl' script to be bundled, but that script is not present in the manifest. This inconsistency (missing executable and omitted env vars) does not align with the claimed purpose.
ℹ
Instruction Scope
The runtime instructions are narrow and appropriate for a user-account Telegram CLI: install, set TELEGRAM_API_ID/HASH, login interactively, and store sessions locally. The SKILL.md does not instruct the agent to read unrelated system files or send data to unexpected endpoints. However, because the actual 'tgctl' implementation is not included, we cannot verify that its runtime behavior stays within the documented scope.
ℹ
Install Mechanism
The included installer is a local shell script that creates a per-user venv and pip-installs Telethon (from PyPI), then writes a wrapper into ~/.local/bin. Installing Telethon via pip is expected for a Python tool. There is no external arbitrary binary download. Risk is moderate because pip install executes code from PyPI and the main tool ('tgctl') referenced by the installer is missing from the package.
!
Credentials
The SKILL.md requires TELEGRAM_API_ID and TELEGRAM_API_HASH and stores sessions under ~/.tgctl-telethon/, but the skill metadata lists zero required env vars and no config paths. Declaring no primary credential while the CLI needs API credentials is a clear mismatch. The env access requested by the instructions (API_ID/HASH, session files) is reasonable for the stated functionality, but the registry/package should declare them.
✓
Persistence & Privilege
The skill does not request always: true and does not modify other skills or system-wide configs. The installer writes files under the user's home (~/.local/bin, ~/.tgctl-telethon-venv, and session directory), which is normal for a per-user CLI tool.
What to consider before installing
Do not install this package yet. The installer references a 'tgctl' script that is not included in the package — without that file you cannot verify what will run. Before proceeding, ask the publisher for the missing tgctl source (or a trusted upstream repository) and review it for network endpoints and sensitive operations. Confirm the registry metadata is updated to declare the required TELEGRAM_API_ID and TELEGRAM_API_HASH and the session path (~/.tgctl-telethon/). If you must test, run the installer in an isolated environment (container or disposable VM), inspect the created wrapper and the tgctl script, and verify that network calls go only to Telegram's official endpoints. Remember: this tool performs account-level actions (send/delete/kick/etc.), so a malicious or tampered tgctl could operate as your Telegram user — only install if you can review the executable source or trust the package origin.

Like a lobster shell, security has layers — review code before you run it.

latestvk976avy0dj6ztg1waqzmret8v183wxzw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments