botcall

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

Overview

This skill is transparent about managing phone numbers and SMS codes, but it gives an agent sensitive verification-code and billing-related capabilities without clear user-approval boundaries.

Install only if you intentionally want an agent to manage Botcall phone numbers and SMS verification flows. Require explicit approval before any signup, code retrieval or entry, number provisioning or release, plan upgrade, or billing action. Treat BOTCALL_API_KEY and received SMS codes like passwords, and do not use the skill for accounts or services you do not own or have authority to verify.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The skill description is broadly framed for agents to provision phone numbers, receive SMS, and handle verification flows without constraining when this is appropriate or requiring user confirmation. In practice, that makes it easy for an agent to invoke the skill in sensitive account creation or authentication contexts where legal, consent, fraud, and account-integrity risks are significant.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The documentation encourages receiving verification SMS and signing up for services but does not warn about privacy, consent, fraud, billing, or the account-security implications of processing OTPs. Because verification codes are security-sensitive secrets, omitting user-facing warnings materially increases the chance of misuse for unauthorized account creation, bypass of anti-abuse controls, or handling regulated personal data without safeguards.

Ssd 3

High

• Confidence: 96% confidence
• Finding: The core description explicitly normalizes extracting verification codes and using temporary phone numbers for signup and phone verification. This directly supports workflows that can defeat service trust signals, enable mass account creation, or facilitate unauthorized enrollment and authentication steps, making the skill inherently high risk in an agent context.

Ssd 3

High

• Confidence: 98% confidence
• Finding: The example provides step-by-step instructions for obtaining a phone number, waiting for a verification code, and entering it to complete a signup. That operationalizes a risky abuse pattern rather than merely documenting passive capabilities, lowering the barrier for agents or users to automate account creation and verification workflows that many services treat as anti-abuse or authentication controls.

VirusTotal

66/66 vendors flagged this skill as clean.