Back to skill

Security audit

Goldrush X402

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only skill for GoldRush x402 paid API access, with wallet-payment behavior disclosed but requiring careful wallet and budget controls.

Install only if you intend to let an app or agent make wallet-paid x402 requests. Use a dedicated low-balance or testnet wallet, store the private key in a secrets manager, pin/review the npm dependencies, and add explicit spend limits, endpoint allowlists, and request-rate controls before autonomous use.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Vague Triggers

Medium
Confidence
84% confidence
Finding
The skill description contains very broad routing cues such as any agent needing blockchain data, autonomous access, no-signup access, or x402 mentions. In an agent ecosystem, overly broad invocation criteria can cause the skill to be selected in situations where users did not explicitly intend to authorize wallet-based paid requests, increasing the chance of unintended external calls and charges.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The example instructs users to supply a wallet private key via environment variable to a client that automatically handles payment and request retries. Even though using environment variables is common, the combination of secret handling plus automatic paid network actions without prominent warning can lead to accidental fund usage, misuse in shared environments, or unsafe copy-paste adoption by less experienced users.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The documentation instructs users to provide a wallet private key to an automated client that will sign payments transparently, but it does not prominently warn that every qualifying request may trigger real blockchain spending. In an AI-agent context, this is riskier than ordinary API auth because autonomous or mis-scoped requests can repeatedly drain wallet funds, especially when retries and dynamic pricing are involved.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.