Cli

Pay merchants and file payment disputes on the x402r refundable payments protocol

This CLI appears to do what it says, but it uses and persists private keys and will send payment metadata to an arbiter server and (optionally) to Pinata. Before installing or using it: 1) Do not supply your primary/production private key — use a disposable test key for evaluation. 2) Review and set the arbiter URL and pinata JWT only to endpoints you trust (default is localhost). 3) Inspect ~/.x402r/config.json and ~/.x402r/*.json after running and remove any private keys you don't want persisted. 4) Be cautious about running the included e2e test — it explicitly writes a merchant private key into last-payment.json in the test mode. 5) If you need the agent to use this skill autonomously, consider the additional risk of stored credentials and restrict invocation or use ephemeral keys. If you want more certainty, provide the maintainer/source (homepage/repo) and a provenance check so I can re-evaluate with higher confidence.

Type: OpenClaw Skill Name: x402r-dispute Version: 0.1.3 The skill is classified as suspicious due to significant file system vulnerabilities. Specifically, `src/commands/pay.ts` allows writing arbitrary HTTP response bodies to user-specified paths via the `--output` option, and `src/commands/dispute.ts` allows reading arbitrary files as evidence via the `--file` option. These flaws could enable arbitrary file write/read if an attacker can control the input paths. Additionally, the skill handles private keys, which are stored on disk in `~/.x402r/config.json`, and makes numerous external network calls to arbiter/court URLs (e.g., `https://www.moltarbiter.com/arbiter`) and Pinata, which are high-risk operations, though necessary for its stated web3 payment dispute purpose. There is no evidence of intentional malicious behavior like data exfiltration or persistence.