T09 · Insecure Skill Coding Practices
- Location
SKILL.md:64- Finding
Paid-service API credential exposed in client-side application bundles
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent SmoothSend integration guide, but it tells users to put a paid-service API key into public frontend bundles and run unpinned npm/npx packages.
Review before installing or following this skill. If you use SmoothSend on mainnet, do not assume NEXT_PUBLIC_ or VITE_ keeps the API key secret; use a backend or vendor-supported restrictions, quotas, and transaction policy controls before exposing any credit-bearing key. Pin package versions and avoid running unreviewed npx commands in an environment with sensitive secrets.
SKILL.md:64Paid-service API credential exposed in client-side application bundles
SKILL.md:53Unpinned third-party packages can download and execute mutable supply-chain code
The guidance says to store the SmoothSend API key in environment variables, but the recommended variables are NEXT_PUBLIC_ and VITE_, which are intentionally exposed to client-side bundles. That means any site visitor can recover the key and abuse the commercial service, consume credits, or impersonate the application to the SmoothSend API.
The skill references an MCP server via npx @smoothsend/mcp without pinning a specific version. This creates a supply-chain risk because future package updates or a compromised published version could change behavior unexpectedly when users run the command, especially since npx fetches and executes code directly.