x402
Warn
Audited by Gen Agent Trust Hub on May 5, 2026
Risk Level: MEDIUMREMOTE_CODE_EXECUTIONCREDENTIALS_UNSAFECOMMAND_EXECUTIONDATA_EXFILTRATION
Full Analysis
- [REMOTE_CODE_EXECUTION]: The helper script
scripts/x402-pay.mjsutilizes dynamic loading patterns, includingcreateRequireand dynamicimport(), to resolve and load theviemlibrary from the user's current working directory (process.cwd()). Executing code from paths determined at runtime is a risk factor for local code injection if the tool is run in an untrusted directory. - [CREDENTIALS_UNSAFE]: The skill's operational flow relies on reading sensitive private keys from environment files stored in
.radius/wallets/. Thex402-pay.mjsutility script directly accesses these files to retrieve credentials for signing micropayment authorizations. Although the script verifies that file permissions are set to 0600, the programmatic access to raw private keys increases the risk of credential exposure. - [COMMAND_EXECUTION]: The documentation and evaluation test cases utilize various shell commands, including
curl,jq,node, andcast. This involves a workflow that manages sensitive payment data and EIP-712 typed-data payloads within temporary files in the/tmpdirectory. - [DATA_EXFILTRATION]: The
x402-pay.mjsscript performs network requests to transmit signed cryptographic authorizations (EIP-2612 and Permit2 signatures) to external HTTP endpoints. While this is the intended function of the x402 protocol, the script sends these authorizations to any URL provided as a command-line argument, which could lead to the exposure of payment permits to untrusted or malicious servers.
Audit Metadata