T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Global Package Installation Can Retrieve Unaudited Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This paid DeFi automation skill makes strong financial automation claims, but the inspected code is only a local configuration stub and does not perform the advertised on-chain monitoring or fund management.
Review carefully before installing or paying. This artifact does not appear to steal keys or move funds, but it also does not deliver the advertised DeFi automation, has unclear financial-risk disclosure, stores wallet metadata locally, and has install/dependency reproducibility problems. Do not rely on it for portfolio protection, yield optimization, or automated exits unless the publisher provides reviewed implementation evidence and safer pinned installation instructions.
SKILL.md:32Unpinned Global Package Installation Can Retrieve Unaudited Code
index.js:1Imported CLI Dependency Is Missing from the Manifest and Lockfile
index.js:58Advertised Financial Automation and Safety Controls Are Not Implemented
The skill markets itself as a premium autonomous DeFi yield optimizer, but the described setup and observed behavior do not substantiate the claimed on-chain automation, rebalancing, or APY-driven fund movement. In a financial/web3 context, this mismatch is dangerous because users may pay for the product, make risk decisions, or expose wallets under false assumptions about what the software actually does.
The skill advertises autonomous on-chain execution and multi-wallet management without prominent warnings about transaction authority, custody risk, bridge/protocol risk, liquidation or slippage risk, and the consequences of automated fund movement. In the DeFi context, omission of these warnings materially increases the chance that users will grant trust or permissions without understanding that losses can occur rapidly across multiple chains and wallets.
The skill’s metadata and runtime output market automated DeFi yield farming, cross-chain rebalancing, and premium automation, but the implementation only prints placeholder messages and performs no actual automation. In a financial/web3 context, this is dangerous because users may rely on false capabilities, make asset-management decisions based on misleading claims, or be socially engineered into a future paid upgrade or follow-on component that requests wallet access.
The lockfile pins axios to 1.16.0, which the provided analysis reports as affected by multiple HIGH-severity advisories including denial of service, prototype-pollution-adjacent behavior, and proxy bypass issues. In a DeFi automation skill that likely makes frequent outbound RPC/API requests and may process untrusted response or config data, these flaws can increase exposure to service disruption, request-routing abuse, or unsafe handling of attacker-controlled inputs.
form-data 4.0.5 is reported vulnerable to CRLF injection via unescaped multipart field names/filenames. If this skill ever constructs multipart requests from user-controlled or external data, an attacker may be able to smuggle crafted headers or alter request structure, which is especially risky when interacting with third-party APIs or signing/upload workflows.
ws 8.17.1 is flagged for memory disclosure and memory-exhaustion denial of service. Because ethers commonly uses WebSocket providers for blockchain event streams and this skill is designed for automated multi-chain yield operations, a vulnerable WebSocket stack could expose sensitive process memory or allow remote peers to destabilize long-running automation by exhausting resources.
The file includes axios at a version identified by the scanner as having multiple known advisories, including denial-of-service and proxy-handling issues. In a cross-chain DeFi automation context that likely depends on external APIs and network routing, vulnerable HTTP behavior can disrupt automation, expose internal network assumptions, or amplify the impact of malicious responses.
The init command claims to operate in 'read-only mode' but persists wallet addresses to config.json, which is a state-changing action involving sensitive financial metadata. While wallet addresses are public on-chain, silently storing them locally under a misleading 'read-only' label can violate user expectations, expose portfolio associations on shared systems, and erode trust in a tool already positioned for DeFi automation.
The dependency is version-ranged with a caret, which allows automatic installation of newer minor/patch releases that may change behavior or introduce malicious or vulnerable code through the supply chain. In a DeFi automation tool that can potentially handle wallets, RPC interactions, and fund movement, dependency drift increases the risk of compromise and makes builds non-reproducible.
"license": "PROPRIETARY",
"private": false,
"dependencies": {
"ethers": "^6.0.0",
"axios": "^1.6.0"
},
"engines": {
Using a caret range for axios permits unreviewed dependency updates, which is a supply-chain risk and can unexpectedly pull in vulnerable releases. Because this package is a publicly installable DeFi automation skill, any compromised or flawed HTTP client dependency could affect remote data fetching, transaction logic, or secrets handling.
"private": false,
"dependencies": {
"ethers": "^6.0.0",
"axios": "^1.6.0"
},
"engines": {
"node": ">=18.0.0"