Security audit

Telegram Phone Checker

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it says, but it is a privacy-sensitive Telegram lookup tool that encourages checking phone numbers without clear consent or authorization limits.

Install only if you have a legitimate reason to check the phone numbers involved and can obtain consent or authorization where required. Expect phone numbers and returned Telegram profile data to be sent to apipick; avoid using it for broad enumeration, stalking, profiling, or storing raw lookup results unnecessarily. Protect the APIPICK_API_KEY like any other credential.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Natural-Language Policy Violations

High

Confidence: 98% confidence
Finding: The skill explicitly promotes checking whether someone uses Telegram and finding a Telegram username by phone number without any consent, ownership, or lawful-use restriction. This enables account enumeration and privacy-invasive lookups of third parties, which can support stalking, harassment, social engineering, or doxxing.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The README explicitly markets checking whether arbitrary phone numbers are registered on Telegram and retrieving associated profile data through a third-party API, but it provides no warning about consent, lawful basis, or privacy obligations. This enables misuse for enumeration, stalking, doxxing, or unauthorized profiling of third parties, and the skill context makes the issue more dangerous because the primary advertised use is inspecting someone else's phone number rather than managing the caller's own account.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The skill sends a phone number to a third-party service and returns account/profile data, but it does not warn users that sensitive personal data is being transmitted off-platform. This creates a privacy and consent risk because users may unknowingly submit another person's phone number and receive identifying Telegram information from an external API.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The API reference documents sending a phone number to a third-party service and receiving account/profile data, but it does not warn users about the privacy implications, consent requirements, or sensitivity of the returned identifiers and names. In this skill’s context, the omission is more dangerous because the stated use cases include checking whether someone uses Telegram and finding a username by phone number, which can facilitate privacy-invasive enumeration and doxxing without adequate user awareness.

External Transmission

Medium

Category: Data Exfiltration
Content: ### Example ```bash curl -X POST https://www.apipick.com/api/check-phone-telegram \ -H "Content-Type: application/json" \ -H "x-api-key: YOUR_API_KEY" \ -d '{"phone_number": "+1234567890"}'
Confidence: 84% confidence
Finding: The example explicitly transmits a phone number and API key to an external service, which is a real external data transfer. In this skill’s context, that transfer is the core function, but it is still security-relevant because the data includes a personal identifier and may return additional personal profile information; without clear disclosure and handling guidance, users may unknowingly expose sensitive data to a third party.

Static analysis

No suspicious patterns detected.