T09 · Insecure Skill Coding Practices
- Location
SKILL.md:57- Finding
Server-Controlled Payment Requirements Lack an Explicit User Approval and Local Validation Gate
- Content
View full analysis
` header. 8. Parse the JSON response and `X-PAYMENT-RESPONSE` header. ``` Related behavior at `README.md:16`: ```markdown This skill is automatically invoked by your OpenClaw agent when a matching task is detected. ``` ### Technical Analysis The documented workflow directs an agent to obtain a payment requirement from a remote HTTP 402 response and then transfer the remotely specified `maxAmountRequired` to the remotely specified `payTo` address. The instructions do not require: - Explicit user confirmation immediately before payment. - Validation of the recipient against a locally trusted allowlist. - Enforcement of the advertised `$0.25` per-request maximum. - Independent validation of the selected chain, asset, and amount. - Rejection of unexpected or changed payment requirements. Because the skill can be automatically invoked for matching tasks, an agent with wallet or transaction-signing capabilities could proceed from an ordinary documentation request to a financial operation without a mandatory consent gate. HTTPS protects transport confidentiality and integrity but does not protect against a compromised, malicious, or misconfigu ...[truncated 2088 chars]- Remediation
View remediation
