Kelp Forest
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
Review carefully: this skill asks you to run mainnet crypto scripts with your wallet private key, grant a very large token allowance, and deposit tokens into staking contracts.
Install only if you understand the DeFi and smart-contract risks. Verify the contract addresses from an independent source, use a new limited-balance wallet, reduce approvals to the exact amount needed, monitor or stop any keeper loop, and revoke allowances when finished.
Findings (4)
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.
If the script, dependency, or contract is wrong or compromised, the wallet can sign transactions that affect real funds.
A raw wallet private key grants broad signing authority over the wallet, not just the single staking action. This is high-impact financial authority, especially because the registry metadata declares no primary credential or required environment variable.
**Prerequisites:** A wallet private key with MOLT tokens on Base. ... `WALLET_KEY=0xYourPrivateKey node kelp-agent.mjs`
Use a fresh wallet with only the amount you intend to risk, verify all contract addresses independently, and avoid providing a private key for a wallet holding unrelated assets.
The approved contract may be able to move far more MOLT than the user intended until the allowance is revoked, and the deposit transaction uses real funds and gas.
The script approves the staking contract to spend nearly one billion MOLT while the configured stake is 1000 MOLT, then deposits funds once the script is run. That approval is materially broader than the immediate action requires.
const STAKE_AMOUNT = '1000'; ... const tx = await molt.approve(FOREST, parseUnits('999999999', 18)); ... const tx = await forest.deposit(POOL_ID, amount);Change the approval to the exact stake amount, confirm each transaction manually, and revoke allowances after use if they are no longer needed.
A continuously running keeper may spend gas, submit transactions at unexpected times, or interact with other users' harvestable positions.
The skill discloses a long-running keeper loop. This is aligned with the stated purpose, but it would continue making on-chain interactions with the configured wallet while it runs.
## Keeper Loop (Earn Fees) ... `// kelp-keeper.mjs - Auto-harvest loop that earns keeper fees`
Run the keeper only when supervised, set clear limits if available, and stop it when you no longer want autonomous transactions.
A dependency or version mismatch could affect a script that signs real blockchain transactions.
Installing ethers is expected for an Ethereum script, but the artifact does not pin a version or provide a lockfile/source verification. This matters more because the script handles wallet signing.
`npm install ethers`
Use a trusted environment, pin the ethers version, and review the copied script before running it with any funded wallet.