T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Third-Party Wallet Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent documentation for wallet-paid blockchain API access, but it should be reviewed because its examples give an agent a wallet private key and allow automatic payments without clear local spending controls.
Review this skill before use. Use only a dedicated low-balance wallet, preferably testnet-only, never reuse a wallet that holds valuable assets, store the private key in a secrets manager, pin and audit the x402 dependencies, and add local payment controls for chain, token, recipient, per-request amount, retries, and total spend before allowing an agent to run autonomously.
SKILL.md:30Unpinned Third-Party Wallet Dependencies
SKILL.md:14Automatic Wallet Payments Lack Documented Local Spending Controls
The description says to use this skill whenever the user is 'building an AI agent that needs blockchain data', 'wants wallet-based micropayments', or 'wants no-signup/no-onboarding blockchain data access'. These triggers are expansive and lack clear boundaries or exclusion examples, which could cause the skill to be invoked for many ordinary blockchain data requests where another skill may be more appropriate.
The example instructs users to supply a wallet private key and enables automatic payment handling, but it omits warnings about secret handling, hot-wallet risk, and the fact that requests can spend funds. In an agent context, this can lead to unsafe key exposure or unattended micropayment spending if developers copy the example directly into production workflows.
This markdown file includes a TypeScript example that reads process.env.WALLET_PRIVATE_KEY, which is a sensitive credential. The surrounding text explains how to use the key but does not warn users about securely storing the private key or the risks of exposing it.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All 60+ Foundational API endpoints are available through the x402 proxy. Endpoint paths mirror the Foundational API.
**Base URL:** `https://x402.goldrush.dev/v1` (replaces `https://api.covalenthq.com/v1`)
### Key Data Endpoints
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All 60+ Foundational API endpoints are available through the x402 proxy. Endpoint paths mirror the Foundational API.
**Base URL:** `https://x402.goldrush.dev/v1` (replaces `https://api.covalenthq.com/v1`)
### Key Data Endpoints
No suspicious patterns detected.