Back to skill

Security audit

Web3 Yield Automator PRO

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (3)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:32
Finding

Unpinned Global Package Installation Can Retrieve Unaudited Code

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
index.js:1
Finding

Imported CLI Dependency Is Missing from the Manifest and Lockfile

Content
View full analysis
=18.0.0" } ``` The lockfile root contains the same incomplete dependency set: ```json "dependencies": { "axios": "^1.6.0", "ethers": "^6.0.0" }, "bin": { "yield-automator": "index.js" } ``` ### Technical Analysis ES module imports are resolved before command handling begins. Because `commander` is neither declared in `package.json` nor represented as a direct dependency in `package-lock.json`, a clean installation cannot reliably resolve the import. Under normal npm dependency isolation, invoking the CLI will fail with a module-resolution error unless an unrelated copy happens to be accessible from the environment. This undermines reproducibility and can encourage users or operators to install an arbitrary package manually to repair the application. Such ad hoc dependency installation bypasses the reviewed dependency graph and can expose users to the wrong package, an incompatible release, or an untrusted source. ### Attack Path 1. A user installs the package according to its documentation. 2. npm installs only the dependencies declared in the manifest and lockfile. 3. The user invokes the `yield-automator` command. 4. Node.js attempts to resolve the startup import of `commander`. 5. The CLI fails because the dependency is unavailable. 6. The user or an automated deployment process attempts to repair the failu ...[truncated 687 chars]
Remediation
View remediation

other

Warning
Location
index.js:58
Finding

Advertised Financial Automation and Safety Controls Are Not Implemented

Content
View full analysis
{ loadConfig(); console.log('🚀 Starting Web3 Yield Automator...'); console.log('📊 Monitoring chains:', config.chains); console.log('🎯 Min APY:', config.minApy + '%'); console.log('⚠️ Risk profile:', config.risk); // Stub for actual DeFi automation logic console.log('\n💡 Premium features unlocked:'); console.log(' - Auto-compound rewards'); console.log(' - Cross-chain rebalancing'); console.log(' - Tax optimization'); console.log('\n⚡ Full automation logic deployed on purchase.'); }); ``` ### Technical Analysis The implementation does not instantiate a blockchain provider, signer, smart-contract client, monitoring loop, pricing or yield data source, or transaction workflow. No API request is issued, and no on-chain transaction is created or submitted. The `start` command nevertheless emits su ...[truncated 1677 chars]
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (10)

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
99% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: axios==1.16.0 — 10 advisory(ies): CVE-2026-67313 (Axios: Excessive recursion in formDataToJSON can cause denial of service); CVE-2026-67319 (Axios: Nested axios option objects can consume polluted prototype values); CVE-2026-67315 (Axios: NO_PROXY bypass for 0.0.0.0 local addresses in axios) +7 more

High
Category
Supply Chain
Confidence
96% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: form-data==4.0.5 — 1 advisory(ies): CVE-2026-12143 (form-data: CRLF injection in form-data via unescaped multipart field names and f)

High
Category
Supply Chain
Confidence
91% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: ws==8.17.1 — 2 advisory(ies): CVE-2026-45736 (ws: Uninitialized memory disclosure); CVE-2026-48779 (ws: Memory exhaustion DoS from tiny fragments and data chunks)

High
Category
Supply Chain
Confidence
93% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: axios==1.16.0 — 10 advisory(ies): CVE-2026-67313 (Axios: Excessive recursion in formDataToJSON can cause denial of service); CVE-2026-67319 (Axios: Nested axios option objects can consume polluted prototype values); CVE-2026-67315 (Axios: NO_PROXY bypass for 0.0.0.0 local addresses in axios) +7 more

High
Category
Supply Chain
Confidence
96% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
87% confidence
Finding

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.

Content

Scanner excerpt · package.json (reported line 19)May include surrounding context.

json
"license": "PROPRIETARY",
  "private": false,
  "dependencies": {
    "ethers": "^6.0.0",
    "axios": "^1.6.0"
  },
  "engines": {

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
90% confidence
Finding

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.

Content

Scanner excerpt · package.json (reported line 20)May include surrounding context.

json
"private": false,
  "dependencies": {
    "ethers": "^6.0.0",
    "axios": "^1.6.0"
  },
  "engines": {
    "node": ">=18.0.0"