Spraay Openclaw

Payment infrastructure for AI agents. Batch crypto payments, x402 micropayment gateway, agent-to-agent USDC settlement, multi-chain payroll, Bitcoin PSBT tra...

What to consider before installing: 1) Verify and lock SPRAAY_GATEWAY_URL — only set it to the official gateway URL (https://gateway.spraay.app) unless you fully trust an alternative endpoint. An attacker-controlled gateway URL would let the skill send any data (including local files) to that endpoint. 2) Treat SPRAAY_API_KEY carefully — although optional, confirm whether the gateway uses it; don't provide private keys or wallet secrets to this skill. 3) The script's ipfs-pin reads and base64-encodes a local file and transmits it — avoid using ipfs-pin with sensitive files. 4) The script calls endpoints that may require x402 payment headers; confirm whether payments require your wallet or the gateway negotiates payments server-side before sending funds. 5) Small inconsistencies to confirm: the script uses base64 (not listed in required binaries) and doesn't use the optional API key header; ask the publisher for clarification and for source code or audits of the gateway service before routing real payments. 6) If you plan to allow autonomous agent invocation with this skill, limit its scope (test on a non-production account, use small amounts, and monitor network traffic). If you want more definitive guidance I can: (a) point out exact places to change the script to avoid accidental exfiltration, (b) generate a minimal wrapper that whitelists endpoints/filenames, or (c) produce questions to ask the publisher to increase confidence.

Type: OpenClaw Skill Name: spraay-openclaw Version: 1.0.0 The Spraay skill bundle provides extensive payment and API gateway capabilities but includes high-risk functionality and security vulnerabilities. The `ipfs-pin` command in `scripts/spraay.sh` allows the agent to read local files, base64-encode them, and transmit their full content to the remote gateway (`gateway.spraay.app`), which serves as a potential data exfiltration vector. Additionally, the script lacks input sanitization when constructing JSON payloads for `curl` commands (e.g., in the `ai` and `batch` cases), making it vulnerable to JSON and shell injection. While these features are consistent with the stated goal of providing an IPFS and payment infrastructure, the lack of safeguards around file access and input handling poses a significant risk to the host environment.