Security audit

Vercel

Security checks across malware telemetry and agentic risk

Overview

This is a transparent Vercel CLI reference skill, but it can affect live projects and secrets if used carelessly.

Install only if you want an agent to help manage Vercel. Before production deploys, rollbacks, removals, team switching, env pulls, token use, or any command with --yes, verify the project, team scope, working directory, and exact target, and avoid exposing Vercel tokens or .env.local contents in chat.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

Confidence: 85% confidence
Finding: The skill description uses broad trigger terms like 'deploy' and 'vercel project', which can cause the skill to activate in situations where the user did not clearly intend Vercel-specific actions. In a tool that can deploy to production, modify domains, and manage environments, unintended invocation increases the risk of running sensitive operations in the wrong context.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The documentation exposes destructive and sensitive commands such as production deploys, rollback, project removal, domain removal, environment variable access, and team switching without any safety guidance or confirmation requirements. In an agent setting, this omission can normalize high-impact actions and lead to accidental deletion, secret exposure, or production changes without sufficient user intent verification.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.