T09 · Insecure Skill Coding Practices
- Location
SKILL.md:12- Finding
Paid OSINT Requests Can Be Executed Without Enforced Spending Controls
- Content
View full analysis
" - "what accounts is on" - "check the email " - "run an OSINT report on " - "profile this handle: " ## Commands (OpenClaw's x402 auto-handler pays + retries transparently) | Intent | Request | Price | |---|---|---| | Free trial | `GET https://x402-osint.tail66f665.ts.net/trial/osint/{username}` | free | | Username lookup | `GET https://x402-osint.tail66f665.ts.net/osint/{username}` | $0.01 | | Identity report | `GET https://x402-osint.tail66f665.ts.net/report/{username}` | $0.05 | | Email lookup | `GET https://x402-osint.tail66f665.ts.net/email/{address}` | $0.03 | ``` ### Technical Analysis The Skill requires access to an EVM private key and states that its x402 handler pays for requests and retries them transparently. However, `MAX_SPEND_PER_CALL` is only recommended rather than documented as mandatory or fail-closed. No explicit per-transaction confirmation, cumulative session budget, retry ceiling, or duplicate-payment protection is specified. The broad natural-language activation triggers increase the likelihood that a paid operation could be initiated unintentionally or through attacker-controlled content processed by the agent. Transparent retry behavior can further increase exposure if each retry can lead to another payment. The documentation does not demonstrate that the handler enforces the advertised price or verifies a payment request against an immutable allowlist before signing. ...[truncated 1174 chars]- Remediation
View remediation
