Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Polymarket Whale Copier
v1.0.0Copy trade winning Polymarket wallets automatically. Track whale wallets, mirror their bets at configurable percentages, with built-in risk management. No API keys needed.
⭐ 1· 1.2k·3 current·5 all-time
byCassh@cassh100k
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill advertises automatic copy-trading and 'No API keys needed', yet the SKILL.md Quick Start tells users to export POLYMARKET_KEY (a private key). The registry metadata lists no required environment variables or primary credential, which is inconsistent with the code and instructions. Also the code logs and monitors trades but does not implement real order placement (execute_trade only logs a placeholder), so the claimed capability to 'place matching orders' is not implemented.
Instruction Scope
Runtime instructions tell the agent/user to set a private key (POLYMARKET_KEY) and run copy_trader.py; the code reads that env var and derives a wallet locally. auto_redeem.py expects POLYMARKET_WALLET (different env var name). The scripts perform network calls only to public Polymarket data-api endpoints and polygon-rpc.com, and write local files (trades.log, state.json). There is no other file-system or system-wide access, but the mismatch of required env vars and ambiguous guidance is problematic.
Install Mechanism
No install spec — instruction-only with bundled scripts. Nothing is downloaded at install time; included files are plain-text Python and shell scripts. This is the lowest install risk.
Credentials
Registry declares no required credentials, but SKILL.md and copy_trader.py rely on a secret private key in POLYMARKET_KEY to derive an 'our' wallet and check balance. auto_redeem.py expects POLYMARKET_WALLET. Requesting a private key (a high-value secret) should have been declared explicitly; the absence in metadata is a red flag. The code does not exfiltrate the key, but it does perform on-host use and persists logs/state locally.
Persistence & Privilege
always:false and no system-wide configuration changes. The skill can be run in background via screen scripts, and writes its own log and state files under its script directory. It does not modify other skills or agent configuration.
What to consider before installing
This package is 'suspicious' rather than clearly malicious: it mostly contains readable code and only talks to Polymarket and a Polygon RPC, but it has several inconsistencies you should consider before installing or running with real funds. Key points:
- Do not export or paste your real private key into POLYMARKET_KEY unless you fully trust and understand the code. The registry did not declare any required secret, but the Quick Start and copy_trader.py expect a private key.
- The skill advertises automatic order execution and auto-redeem, but the code's execute_trade is a placeholder and auto-redeem only prints instructions; live trading / signing is not implemented. Do not assume it will place or redeem trades for you.
- The code derives a wallet address by hashing the private key (not a correct eth derivation) — this is a poor implementation choice and suggests the author cut corners; prefer software using a standard web3 library for signing.
- Network activity is limited to data-api.polymarket.com and polygon-rpc.com; there is no obvious exfiltration endpoint, but lack of declared credentials and inconsistent env var names (POLYMARKET_KEY vs POLYMARKET_WALLET) reduce transparency.
Recommended actions:
- If you want to try it, run only in dry_run mode (config.json default) and on an isolated/test environment with a throwaway wallet funded with minimal funds.
- Inspect and, if necessary, replace the wallet-derivation and signing code with a standard, audited web3 library before attempting live trades.
- Ask the publisher to update the registry metadata to declare the required credential(s) and to clarify differences between POLYMARKET_KEY and POLYMARKET_WALLET; request implementation of real signing/placement or remove misleading claims.
- Prefer open-source tools that explicitly disclose how they handle keys (e.g., local signing only, never transmitted) and that implement signing with well-known libraries.
If you are not comfortable auditing code yourself, do not provide your private key and avoid enabling live trading.Like a lobster shell, security has layers — review code before you run it.
latestvk971shbanjmgg2ppfmrmpzz7nh80zppe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.