Perp Lobster
WarnAudited by ClawScan on May 10, 2026.
Overview
Perp Lobster appears purpose-built for trading, but it would run external GitHub code with a Hyperliquid private key and can place or automate real trades.
Only install if you are comfortable running the external Perp Lobster repository locally and using it to sign real Hyperliquid trades. Use a limited-funds subaccount, inspect and pin the code before setup, never paste keys into chat, and require explicit confirmation for every trade, fee approval, and bot start.
Findings (5)
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 key can authorize trading-related actions; if it is mishandled or used by unsafe external code, the user could lose funds.
The skill requires a wallet/private signing key for Hyperliquid trading. The handling advice is good, but the registry metadata declares no primary credential or env vars, so a highly sensitive authority is under-declared.
Fill in: HL_ACCOUNT_ADDRESS=0xYourWalletAddress HL_SECRET_KEY=your_private_key_hex Do NOT paste your private key in this chat — edit the file directly.
Use only a dedicated limited-funds subaccount or API wallet, never paste the key into chat, and treat any exposure as requiring key rotation.
A changed or compromised repository, setup script, or dependency could run local code that later handles credentials and places trades.
The package contains no reviewed code or install spec, so the actual installer and trading scripts come from an external repository selected by branch/tag rather than a reviewed artifact.
git clone --branch v1.0 https://github.com/ThisNewMark/perplobster.git ... cd perplobster && chmod +x setup.sh && ./setup.sh
Review the repository and scripts before use, prefer pinning to a known commit, and run setup in an isolated environment.
A confirmed command can open or close leveraged positions or approve fee-related actions on the user's account.
Direct shell execution of trading commands is central to the skill and confirmation is required, but these commands can place real orders, close positions, and approve builder fees.
When the user asks you to trade or manage bots, execute the commands directly using your shell tool. Always confirm with the user before placing trades or running setup scripts.
Before every action, verify side, market, amount, leverage, price, account/subaccount, and whether the command is a one-time trade or a persistent bot.
A user may over-trust the setup script or underestimate the network and supply-chain behavior involved in installing dependencies.
The skill instructs the agent to make a definitive safety/privacy claim about an external setup script that is not included in the reviewed artifacts.
Tell the user: "This script creates a Python venv and installs dependencies. No data is sent externally. OK to run it?"
Avoid blanket assurances; inspect the setup script and dependency list, and explain any network access or package installation accurately.
A bot can continue trading and accumulating losses until it is stopped or its limits are reached.
Continuous background trading is disclosed and has stop commands, but it persists beyond a single user prompt and can keep making financial decisions.
For automated trading bots (run continuously in the background): ... cd perplobster && ./start.sh config/my_bot.json ... stop all
Use small limits, subaccounts, stop-loss settings, and regularly verify that bots are stopped when no longer needed.