Pumpclaw
v2.1.0Revenue infrastructure for autonomous AI agents on Base. Deploy ERC20 tokens with Uniswap V4 liquidity — 80% trading fees to creator, LP locked forever, $0 c...
⭐ 1· 1.9k·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description match the included TypeScript scripts: the code performs token creation, fee claims and swaps on Base via Uniswap V4, which reasonably requires a wallet private key and an RPC endpoint. However, the skill metadata declares no required environment variables or primary credential while the SKILL.md and the code both require BASE_PRIVATE_KEY and a CHAIN.RPC value (imported from a missing shared module). That mismatch is a substantive coherence problem.
Instruction Scope
Runtime instructions explicitly tell users to export BASE_PRIVATE_KEY and run npx tsx scripts; the code will sign and broadcast transactions (createToken, createTokenFor, claimFees, swaps). The scripts also allow creating tokens on behalf of another creator (relayer pattern), so running them with a key could be used to route fees or create tokens that credit a third party. The code imports ../../../shared/contracts.js and ../../../shared/abis.js which are not present in the package; that means execution depends on external host-provided files and values (e.g., CHAIN.RPC), which is unexpected and broadens scope of what will be read/executed.
Install Mechanism
There is no install spec, but package.json and package-lock.json are included declaring viem and its dependencies. Running the suggested commands (npx tsx ...) will fetch/run Node packages (via npm/npx/tsx). This is a moderate risk because it pulls dependencies from npm at runtime; the package does not declare required system binaries (node, npx, tsx) in metadata.
Credentials
The skill requires a private key (BASE_PRIVATE_KEY) to sign transactions — that is expected for a launcher, but the metadata does not declare it. The code also relies on CHAIN.RPC from an external shared module (not included), meaning the skill may use RPC settings supplied by the host environment. Requesting a full private key is sensitive; the SKILL.md does not warn users to use a disposable or gas-only wallet. The relayer option (--creator) allows creating tokens 'on behalf of another creator', which could be misused to divert revenue if not properly audited.
Persistence & Privilege
The skill is not always-enabled, does not request platform-wide persistence, and does not attempt to modify other skills or agent configuration. It runs only when invoked.
What to consider before installing
Do not export your main wallet private key or run the included scripts unless you fully trust and have audited the source and the on-chain contracts. Specific concerns: (1) The SKILL.md and code require BASE_PRIVATE_KEY but the metadata doesn't declare it — that mismatch is a red flag. (2) The scripts import ../../../shared/contracts.js and ../../../shared/abis.js which are not in the package, so execution will depend on host-provided files (including CHAIN.RPC) you can't review here. (3) Running the suggested npx commands will fetch npm packages at runtime. If you still want to test: use a throwaway wallet funded with only a tiny amount of gas, inspect the referenced contracts/ABIs on the GitHub repo (verify factory & locker addresses match on-chain), and run commands in a sandboxed environment. If you require higher assurance, request the missing shared files and a full repo link (or a signed release) and have the smart contracts audited before providing any private keys.Like a lobster shell, security has layers — review code before you run it.
latestvk9769cz18mg80wh415qswhtn3d81f3ra
License
MIT-0
Free to use, modify, and redistribute. No attribution required.