telegram
Audited by Socket on Aug 24, 2026
2 alerts found:
SecurityAnomalySUSPICIOUS: the skill's core Telegram capabilities align with its stated purpose, and the main dependency path looks conventional. However, it handles a full-account Telegram session, exposes broad private message access, and enables high-impact real-world actions through Bash with only prompt-level confirmation guidance. The data flow mostly matches Telegram use, but the transitive cos-upload handoff and unseen helper-script behavior increase risk. This looks like a high-risk but plausibly legitimate personal-account automation skill, not confirmed malware.
No clear indicators of stealthy intrinsic malware (no obfuscation, no eval/exec, no persistence, and no non-Telegram network exfiltration beyond fetching user-supplied URLs for upload). The dominant security concern is high misuse/impact capability: with TELEGRAM_SESSION_STRING and a correctly supplied --confirm, the tool can perform account-level message and chat actions (including delete/join/leave) and can upload attacker-chosen remote HTTP/HTTPS content into Telegram via send-file. Treat this as a powerful administrative automation utility that requires strict control over who can run it, how arguments are supplied, and how the session string is protected.