Back to skill

Security audit

Web3 Yield Automator

Security checks for vulnerabilities and agentic risk

Overview

This skill makes paid DeFi automation claims that are not supported by the shipped code.

Do not rely on this as a real yield automator without auditable implementation, clear wallet-permission boundaries, safety controls, and dependency updates. Treat it as a paid CLI stub that stores configuration locally and prints marketing output, not as reviewed software for managing funds.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (10)

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The skill markets itself as an automated DeFi yield optimizer with on-chain execution, rebalancing, and cross-chain fund movement, but the file only presents installation/setup commands and promotional claims with no evidence of the described functionality. In a financial automation context, this mismatch is dangerous because users may install, trust, pay for, or grant wallet-related access to a product under false assumptions about capabilities, safety controls, and operational behavior.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill describes automated fund movement, rebalancing, and direct smart contract interaction without any prominent warning about the financial and operational risks of unattended on-chain execution. In DeFi, missing safety disclosures can cause users to underestimate risks such as wallet compromise, smart contract loss, bridge failure, liquidation, slippage, and irreversible transactions.

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 supplied analysis identifies as having multiple known security advisories including denial-of-service and proxy-handling issues. In a DeFi automation skill that makes outbound network requests, vulnerable HTTP client behavior is especially risky because it may enable request manipulation, local network access bypass, or service disruption affecting automated fund management.

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
90% confidence
Finding

form-data 4.0.5 is flagged for CRLF injection in multipart field names, which can lead to malformed or attacker-influenced HTTP multipart requests when untrusted input is embedded into form fields. Although this package is transitive via axios and may not always be exercised, any workflow that uploads metadata, proofs, or files to external services could expose request-smuggling or header/body injection risks.

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
94% confidence
Finding

ws 8.17.1 is identified as vulnerable to memory disclosure and memory exhaustion conditions. This matters in a web3 automation skill because ethers commonly relies on WebSocket providers for blockchain event streams, so a malicious or compromised endpoint could leak process memory or crash the automation process, potentially interrupting trading or exposing sensitive runtime data.

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
97% confidence
Finding

This finding indicates the package resolves to a known vulnerable axios version with multiple advisories, including denial-of-service and unsafe handling of nested option/prototype-polluted values. In the context of an automated DeFi yield farming tool, compromise or instability in outbound HTTP handling is more dangerous because it may affect price feeds, protocol interactions, automation decisions, or service availability around financial operations.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
99% confidence
Finding

The skill markets itself as an automated DeFi yield farming tool, but the start command only prints promotional messages and does not perform any automation, monitoring, or on-chain interactions. This is a security-relevant integrity issue because users may trust the tool’s claims and make financial decisions based on nonexistent functionality, especially in a high-risk Web3 context where false automation claims can mislead users about fund management and operational coverage.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
93% confidence
Finding

The comment, command description, and success message all describe the init flow as read-only. However, the code appends the wallet to config.wallets and writes the updated configuration to disk, which is a state-changing side effect that contradicts the documented intent.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

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
92% confidence
Finding

The caret range on axios is materially risky here because the static analysis also reports the resolved dependency as a known vulnerable axios release. In a web3 automation skill that may interact with remote APIs and potentially sensitive financial operations, shipping a vulnerable HTTP client can expose the tool to SSRF-like proxy bypasses, denial of service, or other request-handling flaws depending on usage.

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"