PolyClaw Pro

Trade on Polymarket via split + CLOB execution. Browse markets, track positions with P&L, discover hedges via LLM. Includes automation tools: live portfolio...

This skill is not obviously malicious, but it has multiple red flags you should resolve before trusting it with a real private key: - Do not supply your main wallet private key. Instead test with an expendable account funded with minimal funds. - Ask the author to explain why there are hard-coded wallet addresses (0x2aacf9...) and a funder address in multiple files. If those are sample/demo addresses, they should not be hard-coded in production code. - Confirm and require OPENROUTER_API_KEY (and any other API keys) to be declared in the skill metadata if the LLM hedge feature is used. - The code uses absolute root paths (/root/.openclaw/...). Run the skill in an isolated container or non-root account, and update config paths to be relative to the skill install directory. - Review cron/job recommendations carefully before adding them; scheduled scripts will repeatedly use the private key to sign transactions. - Verify the 'uv' brew formula source before installing; ensure 'uv sync' actually installs the Python dependencies (or run a venv and pip install from the included pyproject.toml yourself). - If you need automation, prefer short-lived or constrained keys (e.g., delegate with a smart-contract-based allowance or use a hot wallet with limited funds) and perform a code audit for any network endpoints or unexpected external calls. If the author cannot satisfactorily explain the hard-coded addresses, root paths, and undeclared env vars, treat the package as unsafe to run with any significant funds.

Type: OpenClaw Skill Name: polyclaw-pro Version: 1.0.0 This skill is classified as suspicious due to its inherent high-risk capabilities, although these appear to be aligned with its stated purpose as a Web3 trading bot. Key indicators include the direct handling of a user's EVM private key (`POLYCLAW_PRIVATE_KEY`) from environment variables for signing and sending blockchain transactions (e.g., in `auto_redeem_check.py`, `discipline_scanner.py`), which is explicitly acknowledged as a security risk in `SKILL.md` and `README.md`. The skill also employs network proxies (Tor via `httpx[socks]` and `curl-cffi`) for Cloudflare bypass, and utilizes `subprocess.run` in `polyclaw_api.py` to execute other scripts (e.g., `swap.py`), which presents a potential Remote Code Execution (RCE) vulnerability if an AI agent were to be prompt-injected into passing malicious arguments. While these functionalities are necessary for a trading bot, their combined risk profile warrants a 'suspicious' classification rather than 'benign'.