Gmail Lead Monitor

• Outcome: Review
• Latest audit: May 28, 2026 · 10:49 AM UTC
• Version: 1.0.0

Overview

This skill is a real Gmail-to-Telegram notifier, but it can forward more email content than users may expect and stores powerful credentials in a local plaintext file.

Review before installing. Use only with a mailbox where you are comfortable sending email subjects and snippets to Telegram, preferably through a dedicated private bot and chat. Protect the config file with restrictive permissions, use a dedicated Gmail app password, and consider modifying the script to alert only on keyword-matching emails or to remove body snippets.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Rogue Agent: Self-Modification, Session Persistence
• 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

Findings (4)

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The skill explicitly states it sends sender, subject, and a body snippet to Telegram, but it does not warn users that email content and metadata leave Gmail and are transmitted to a third-party messaging platform. This creates a real privacy and data-handling risk because users may deploy it on sensitive inboxes without understanding that potentially confidential communications will be forwarded externally.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: This code sends email-derived content to the Telegram Bot API, which transfers potentially sensitive message metadata and body snippets to a third-party service. In a Gmail-monitoring skill, that creates a real confidentiality risk because emails may contain personal, financial, or business-sensitive data, and the user is not given an in-band warning, consent flow, or minimization controls at the point of transmission.

Ssd 3

Medium

• Confidence: 95% confidence
• Finding: The alert formatting intentionally includes sender, subject, timestamp, and a body snippet, which creates a built-in exfiltration path from Gmail to Telegram. Because email content is user-provided and often sensitive, forwarding it to a messaging platform expands the trust boundary and may leak confidential data to Telegram infrastructure, bot operators, or anyone with access to the target chat.

Session Persistence

Medium

• Category: Rogue Agent

Content

3. Go to App passwords → Generate new app password
4. Select "Mail" and your device → Copy the 16-char password

### 2. Create Config File

```bash
mkdir -p ~/.config/gmail_monitor

• Confidence: 89% confidence
• Finding: The setup instructs users to store long-lived secrets including the Gmail app password and Telegram bot token in a plaintext config file under ~/.config/gmail_monitor/config.json, which is a form of session/credential persistence. If the local account, backups, logs, or filesystem permissions are exposed, these credentials can be recovered and used to access the mailbox or send/receive bot messages.

Static analysis

No suspicious patterns detected.