Telegram Login Helper

• Outcome: Review
• Latest audit: May 29, 2026 at 9:38 PM UTC
• Version:
  1.0.0

Overview

This is a coherent Telegram login helper, but it normalizes reusing and copying live personal-account session state without enough safeguards.

Install only if you are managing Telegram accounts you own or are explicitly authorized to access. Treat TDLib state directories and Telegram API credentials like passwords: do not share them casually, keep them out of logs and transcripts, use restrictive file permissions and secure transfer, and know how to revoke or clean up sessions afterward.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (4)

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The skill explicitly recommends copying an existing TDLib state directory to authenticate another namespace, but it does not warn that this state is effectively a live session artifact that can grant access to a personal Telegram account. In a security-sensitive login helper, normalizing session transfer without ownership checks, storage protections, or revocation guidance materially increases the risk of account takeover, unauthorized reuse, and accidental credential leakage.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The skill instructs users to supply TELEGRAM_API_ID and TELEGRAM_API_HASH for MTProto login but gives no guidance on secure handling, such as avoiding hardcoding, logs, shell history, or repo storage. In an operational runbook, omission of basic secret-handling controls can lead to credential exposure and downstream abuse of the Telegram application credentials.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The runbook explicitly instructs operators to copy an existing TDLib state directory to reuse a logged-in Telegram personal-account session, but it provides no warning that this directory contains highly sensitive session material equivalent to account access. In this context, copying state between namespaces or machines can enable unintended account takeover, lateral movement, or long-lived unauthorized access if the files are mishandled, retained, or shared.

Missing User Warnings

Low

• Confidence: 80% confidence
• Finding: The runbook references TELEGRAM_API_ID and TELEGRAM_API_HASH as fallback requirements without any handling guidance, which normalizes use of secrets in an operational flow but omits basic protections. In an agent skill context, operators may paste, log, persist, or expose these values through shells, transcripts, or shared automation, increasing the chance of credential leakage and abuse of Telegram API access.

VirusTotal

63/63 vendors flagged this skill as clean.