Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

AI-powered Automated Concentrated Liquidity Manager for Uniswap v4. Manage liquidity positions, auto-rebalance out-of-range positions, optimize LP fees dynamically, execute limit orders (stop-loss, take-profit), and monitor oracle signals — all from chat. Deployed on Ethereum Sepolia with verified contracts. Use this skill when users ask about DeFi liquidity provision, Uniswap v4 hooks, pool management, LP positions, impermanent loss, or automated market making.

v1.0.0

GhostBot ACLM — AI-powered Automated Concentrated Liquidity Manager for Uniswap v4. Manage liquidity positions, auto-rebalance out-of-range positions, optimize LP fees dynamically, execute limit orders (stop-loss, take-profit), and monitor oracle signals — all from chat. Deployed on Ethereum Sepolia with verified contracts. Use this skill when users ask about DeFi liquidity provision, Uniswap v4 hooks, pool management, LP positions, impermanent loss, or automated market making.

0· 1.6k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (Uniswap v4 ACLM on Sepolia) aligns with the included scripts and contract ABIs: status, pool stats, positions, add-liquidity, and oracle posting are all implemented. The architecture and references match the code’s on-chain interactions. Nothing else in the files attempts to provide unrelated capabilities (e.g., cloud access, system administration) — so purpose and capabilities are coherent.
!
Instruction Scope
SKILL.md instructs running the included Node scripts which call only the Sepolia RPC. However the runtime instructions explicitly state a built-in demo wallet will be used by default; config.mjs indeed embeds a default PRIVATE_KEY and default RPC_URL. That means running the scripts as-is will sign transactions from a key included in the repository (not your wallet). The scripts also mint test tokens and write transactions (post-signal, addLiquidity), so running them will submit on-chain writes using that demo account unless you explicitly provide your own DEPLOYER_PRIVATE_KEY and RPC_URL.
Install Mechanism
There is no install spec beyond 'npm install' in the scripts directory and the project depends only on viem. No downloads from unknown URLs or archive extraction are present. This is low install risk.
!
Credentials
The package declares no required env vars, but the code uses optional RPC_URL and DEPLOYER_PRIVATE_KEY env vars. The real concern is that config.mjs provides default values: a public RPC URL (Alchemy key) and a hard-coded private key string. Embedding a private key in the repo is disproportionate for a convenience demo and is a clear secret-management problem — it can be used to sign transactions (mint tokens, post signals) with no further user consent if the user runs scripts unchanged.
Persistence & Privilege
The skill does not request permanent presence (always: false) and does not modify other skills or system-wide settings. It runs client-side scripts when invoked; no privileged persistence or automatic autonomous behavior is declared in the package.
What to consider before installing
Do not run these scripts as-is on a machine with any valuable keys. The repo includes a hard-coded private key and default RPC URL in scripts/config.mjs — running scripts will sign transactions from that embedded key unless you set DEPLOYER_PRIVATE_KEY and RPC_URL yourself. Before using: 1) Inspect scripts/config.mjs and remove or replace the hard-coded PRIVATE_KEY with a blank default; export DEPLOYER_PRIVATE_KEY to a throwaway Sepolia account you control (with no real value) if you want to test. 2) Verify the deployed contract addresses on Etherscan and confirm the authorized 'bot' address/owner of the oracle/hook to understand what the demo key can do. 3) If you need to post signals or transact, prefer using a throwaway testnet account and check its ETH balance before sending transactions. 4) Avoid reusing any private key from this repo for other purposes and do not run it against mainnet. If you want higher assurance, request the author’s provenance (source repo/homepage) or run the code in an isolated environment with a dedicated testnet key.

Like a lobster shell, security has layers — review code before you run it.

latestvk97erz3x5x6pe51gc23d1btmxx80sy3y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments