Back to skill

Security audit

polymarket-pro

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Polymarket CLI trading guide, but it needs Review because it combines live financial actions, wallet private-key handling, and an unverified remote installer without enough safety controls or warnings.

Review carefully before installing. Prefer the package-manager install or a pinned, verified release over the curl-to-shell command. Do not paste real private keys into chats, shell history, scripts, or environment variables; use a dedicated low-balance trading wallet and understand that order, approval, CTF, and API-key commands can affect real funds or account authority.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T03 · Remote Payload Retrieval and Execution

Error

Unverified Remote Installer Is Piped Directly into a Shell

SKILL.md:35

Remediation

T09 · Insecure Skill Coding Practices

Error

Wallet Private Keys Are Exposed Through Command-Line Arguments and Environment Variables

SKILL.md:48

Remediation

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Chaining Abuse

High
Category
Tool Misuse
Content

Shell Script (All Platforms)

bash
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh

Verify Installation

Confidence
98% confidence
Finding

Piping curl output directly into sh removes any opportunity for inspection and turns a remote content fetch into immediate shell execution. In a skill that also handles wallet setup and trading, this increases the blast radius substantially because a malicious installer could steal credentials, alter wallet configuration, or install persistence.

Missing User Warnings

Medium
Confidence
92% confidence
Finding

The skill explicitly recommends passing a private key via a CLI flag and environment variable without warning that command-line arguments may be exposed through shell history, process listings, logs, or terminal recordings. In a trading skill that directly manages funds, this can lead to credential compromise and full wallet theft rather than a mere usability issue.

Missing User Warnings

Medium
Confidence
96% confidence
Finding

The documented commands include live order placement, cancellation, approvals, CTF operations, and other actions that can spend funds or trigger irreversible on-chain transactions, but the skill does not prominently warn users that these are real-money operations. In this context, an agent or user could execute examples as if they were safe demonstrations and incur unintended losses, approvals, or asset movements.

External Script Fetching

Low
Category
Supply Chain
Content

Shell Script (All Platforms)

bash
curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh

Verify Installation

Confidence
97% confidence
Finding

The skill instructs users to fetch and execute a remote installation script directly from GitHub. This creates a supply-chain risk because any compromise of the repository, branch, hosting path, or transport trust assumptions could result in arbitrary code execution on the user's machine.

Static analysis

No suspicious patterns detected.