T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned npm Package Executes with Access to a Wallet Private Key
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its escrow purpose, but it asks users to run unpinned npm code with a wallet private key capable of signing onchain transactions.
Review carefully before installing. Use only a dedicated low-value testnet key, avoid production or reused wallet keys, pin the npm package version if possible, and require explicit human review before any state-changing escrow transaction.
SKILL.md:31Unpinned npm Package Executes with Access to a Wallet Private Key
The skill instructs users to execute an unpinned package directly with npx, which will fetch the latest published version at runtime. In a security-sensitive escrow skill that requires a blockchain private key, a compromised maintainer account, malicious update, or dependency hijack could immediately lead to key theft or unauthorized onchain transactions.
The documentation shows PRIVATE_KEY=0x... inline and in config without any explicit warning about secret-handling, key scoping, or exposure risks. In a crypto payment skill, this is especially dangerous because users may paste real wallet keys into shell history, config files, logs, or shared agent settings, enabling theft of funds and impersonation of the signer.
The MCP configuration also launches the server via unpinned npx, creating the same supply-chain risk but in a more persistent agent/plugin context. Because this skill is designed to hold a PRIVATE_KEY in environment variables, an unexpected upstream package update could exfiltrate credentials or submit transactions without user intent.