Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for Polymarket trading, but it documents an unsafe pipe-to-shell installer and weak private-key handling guidance in a real-money wallet context.
Use the Homebrew or reviewed source-build installation path instead of the `curl | sh` command. Do not pass wallet private keys on the command line, avoid exposing them in environment variables or logs, use a dedicated low-balance trading wallet, review approvals carefully, and require explicit confirmation before any trade, approval, cancellation, redemption, wallet reset, or API-key mutation.
SKILL.md:33Unpinned Remote Installation Script Executed Directly by Shell
README.md:33Unpinned Remote Installation Script Repeated in User Documentation
SKILL.md:55Wallet Private Key May Be Supplied Through Exposed Process Arguments
The pipe into 'sh' is the dangerous execution step because it turns untrusted remote content directly into shell commands. In a trading skill context, this is especially sensitive because users may run it on machines holding wallets, API tokens, or financial credentials, increasing the blast radius of any compromise.
Shell script:
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh
Build from source:
The | sh pipeline is especially dangerous because it chains untrusted network content directly into a shell interpreter, eliminating any inspection barrier and making malicious modifications instantly executable. In a trading skill that may later manage wallets, approvals, and API keys, compromise of the host could lead to theft of private keys, unauthorized trades, or broader system compromise.
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
polymarket setup
polymarket wallet create polymarket approve set # needs MATIC for gas on Polygon
Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
- Speed: Place and cancel orders faster than the web UI
- Automation: Script market-making and hedging strategies
- Transparency: See exactly what commands run before execution
- Control: Manage everything from your terminal
- Data: JSON output for programmatic analysis
**What makes this different:**
The README instructs users to fetch and immediately execute a remote install script via curl, which creates a supply-chain and remote code execution risk. If the upstream repository, network path, or referenced script is compromised, users may run arbitrary shell commands on their system without reviewing them first.
Shell script:
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh
Build from source:
The skill instructs users to fetch and execute a remote install script directly with curl ... | sh, which grants immediate code execution to whatever content is served at that URL at execution time. If the upstream repository, network path, or hosting account is compromised, users could run arbitrary attacker-controlled code on their machine without review.
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh
No suspicious patterns detected.