PolyClaw Pro
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
PolyClaw Pro looks like a real Polymarket trading tool, but it mixes private-key trading with hard-coded wallet addresses, missing helper modules, and automated financial actions that need review before use.
Do not connect a funded Polymarket wallet until the hard-coded wallet addresses are removed or explicitly configured, all referenced trading modules are provided, and automated sell/redeem jobs are reviewed. If you test it, use a fresh wallet with only small funds, avoid enabling cron at first, and verify the displayed wallet address before any approval or trade.
Findings (6)
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 skill may show balances, positions, or CLOB state for a fixed wallet rather than the wallet the user intended, and private-key operations could be bound to the wrong account context.
The API bridge combines the user's configured private key with a fixed funder wallet address, rather than clearly deriving the funder/account from the user's key or an explicit user config.
pk = os.environ.get("POLYCLAW_PRIVATE_KEY", "") ... wallet_addr = "0x2aacf919270Ae303fD3FE8e27D96CBA250936B9F" ... ClobClient(host, key=pk, chain_id=chain_id, signature_type=0, funder=wallet_addr)Remove hard-coded wallet addresses, derive the address from POLYCLAW_PRIVATE_KEY or require an explicit configured wallet/funder, and display the active address before any trade or approval.
Positions may be sold automatically based on the scanner's threshold and available bid, which can realize gains or losses without the user reviewing each sale at execution time.
The scanner is designed to automatically sell qualifying positions and can post CLOB sell orders when run, including under cron, without a per-position user confirmation in the shown code.
"""Discipline Scanner: Check all positions, sell if up 20%+ WITH slippage protection.\nRun via cron alongside whale_monitor.""" ... result = client.post_order(order, OrderType.FOK)
Add a dry-run default, max sale limits, per-position confirmation for interactive runs, and clear opt-in configuration before enabling automated sells.
If a balance lookup fails, another tool or bot relying on this risk check may be told a trade is acceptable even though the real available balance was not verified.
The risk-check path fails open by substituting a high balance when the CLOB balance check fails, which can undermine pre-trade controls used by an external integration.
except Exception:\n clob_balance = 999 # Fallback: don't block on balance check failure
Fail closed on balance-check errors, return an explicit error state, and require the caller to retry or get manual confirmation before trading.
Important code that may create clients, handle keys, or place orders is not available for review here, so the installed behavior may be broken or differ from the reviewed artifacts.
The scanner imports trading helpers that are not present in the supplied file manifest; other referenced components such as portfolio_tracker and scripts/polyclaw.py are also absent from the provided artifacts.
from trade_tor import patch_httpx_for_tor, get_client
Publish the complete runnable package, including all referenced scripts/modules and a lockfile, before users connect funded wallets or private keys.
If the user installs these cron jobs, the skill can keep checking positions and taking financial actions after the original interactive task is over.
The skill explicitly documents scheduled background execution for auto-redeem and take-profit scanning.
# Cron (every 15 minutes) ... auto_redeem_check.py ... # Cron (every 30 minutes) ... discipline_scanner.py
Only enable cron jobs intentionally, keep small funds in the wallet, monitor logs, and document exactly how to disable the scheduled tasks.
Any external bot or SSH principal allowed to call this bridge could access sensitive portfolio information or potentially trigger high-impact actions depending on available commands.
The API bridge is intended to be callable by an external Telegram-bot-style integration over SSH and can expose portfolio, balance, risk, and other trading-related functions.
PolyClaw API Bridge — CLI interface for Wells TG Bot integration.\nCalled via SSH from Wells TG Bot to interact with portfolio_tracker + trade systems.
Restrict SSH access, use a dedicated low-privilege account, log all invocations, and avoid exposing trade or swap commands to untrusted integrations.