Skills/PyPI/iflow-mcp-muhammad18557-telegram-mcp

iflow-mcp-muhammad18557-telegram-mcp@0.1.0

CAUTION

Publisher claims: "Telegram MCP Server - A Model Context Protocol server for Telegram" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher pypi · joined 9 days agoInstalls 27Last detonated 2 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-03 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Prompting user to enter sensitive credentials. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.6sprocessdependency install exit 1
0.7sprocessexec /usr/bin/timeout
0.7sprocessexec .venv/bin/telegram-mcp
0.7sprocessexited 127: timeout: failed to run command '.venv/bin/telegram-mcp': No such file or directory
0.7sclaimedno tools/list reply (exit 127)
0.7sprocessscript backend runs setup only

Static findings

HIGH
Access to sensitive file pathstelegram-bridge/config.py:11 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
CRITICAL
Prompting user to enter sensitive credentialstelegram-bridge/main.py:89 · Prompting user to enter sensitive credentials — social engineeringFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03

What would make this Verified

3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Prompting user to enter sensitive credentials≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  2. Unclaimed publisher≈ +8 on the totalClaim pypi: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim pypi