T09 · Insecure Skill Coding Practices
- Location
SKILL.md:49- Finding
Wallet-Signed Payments Lack Approval, Validation, and Spending Limits
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill’s paid NBA data purpose is clear, but it should be reviewed because it can direct an agent to sign repeated wallet payments without built-in approval, cost limits, or payment validation.
Install only if you are comfortable with an agent making paid x402 NBA data requests. Require wallet confirmation before each request or batch, verify the network, recipient, token, amount, and number of calls, set a strict spending cap, prefer testnet or a low-balance wallet, and treat returned API text as untrusted data during synthesis.
SKILL.md:49Wallet-Signed Payments Lack Approval, Validation, and Spending Limits
prompts/analyze-game.md:5Untrusted API Responses Are Inserted Directly into an LLM Instruction Prompt
The skill explicitly directs the agent to make paid x402 requests and sign them with the user's wallet on Base Sepolia or Base mainnet, but it does not require explicit user consent, display cost information, or impose spending limits before payment. That creates a real risk of unauthorized or surprising charges, especially because the workflow encourages multiple paid calls for a single analysis request.