Yield Farming Agent
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: yield-farming-agent Version: 1.0.0 The bundle contains a functional and well-documented autonomous yield farming agent for the BNB Chain. It includes modules for blockchain interaction (blockchain-reader.js), deterministic decision-making (index.js), transaction execution (tx-executor.js), and Telegram notifications (notifications.js). While the agent requires sensitive credentials like private keys and Telegram bot tokens to function, the code logic is strictly aligned with its stated purpose of DeFi optimization. The developer includes a 'FINAL_CHECKLIST.md' that explicitly identifies security risks (such as the need for hardware wallet integration and professional audits) before mainnet use, indicating that the current risks are known development-stage limitations rather than intentional malice. No evidence of data exfiltration or unauthorized remote control was found.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could spend gas, compound, withdraw, or rebalance crypto positions without a fresh approval for each transaction.
These are fund-mutating blockchain operations and the docs describe them as automatic, so bad inputs, bad market data, or misconfiguration could directly move assets.
- **Transaction Executor** - Automatic DEPOSIT, WITHDRAW, HARVEST, COMPOUND, REBALANCE actions
Use testnet first, require manual confirmation before broadcasts, set strict amount and vault whitelists, and use small dedicated wallets until independently audited.
If a mainnet private key is supplied or mishandled, funds controlled by that wallet could be lost or moved unexpectedly.
Private-wallet signing gives the skill authority over assets controlled by that wallet, while the registry metadata declares no primary credential or required env vars.
Firma transacciones con wallet privada (ethers.js)
Do not paste a mainnet private key into config files; prefer hardware wallets, KMS, multisig, limited hot wallets, and explicit credential declarations.
After starting the scheduler, the agent may continue acting until stopped, including during market or configuration changes.
The long-running autonomous behavior is disclosed and user-started, but it continues making financial decisions periodically once launched.
- **Autonomous Scheduler** - Run farming decisions hourly without manual intervention
Run it under supervision, keep logs and alerts enabled, define a clear stop procedure, and avoid unattended mainnet operation.
A user may over-trust the skill for mainnet funds before necessary financial safety controls are in place.
This overstates readiness for a financial automation system; other supplied docs say mainnet still needs hardware wallet support, oracle integration, a smart contract audit, and emergency pause mechanisms.
✅ **Production Ready** - Fully tested, documented, and deployable
Treat the project as testnet or experimental unless the missing mainnet controls are implemented and independently reviewed.
Users may run package install or deployment commands from code whose upstream provenance is not clearly established in the registry metadata.
The skill provenance is limited, while the docs instruct package installation and deployment steps; this is common for smart-contract workflows but should be reviewed.
Source: unknown Homepage: none No install spec — this is an instruction-only skill.
Inspect package.json, package-lock files, deployment scripts, and repository provenance before running npm install or deploying contracts.
Telegram alerts may reveal vault IDs, transaction hashes, action amounts, and timing to anyone with access to the bot or chat.
The skill sends operational financial details to Telegram; this is disclosed and purpose-aligned, but it is an external data flow.
Envía alertas vía Telegram bot (HTTPS API) ... Formato: vault_id, action, amount, tx_hash, timestamp
Use a private Telegram chat, protect bot tokens, and avoid sending sensitive account or strategy details unless necessary.