Back to skill

Security audit

Smoothsend Gasless

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:64
Finding

Paid-service API credential exposed in client-side application bundles

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:53
Finding

Unpinned third-party packages can download and execute mutable supply-chain code

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
91% confidence
Finding

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.

Content

No source excerpt is available for this finding.