Back to skill

Security audit

Polymarket Whale Copier

Security checks for vulnerabilities and agentic risk

Overview

This Polymarket trading skill asks for a wallet private key and advertises automatic trading/redeeming that the code does not actually implement.

Review carefully before installing. Do not provide a real funded wallet private key to this skill as written, and do not rely on it for automatic copy trading or redemption. If experimenting, use dry-run behavior only, use a separate low-risk wallet/address, and expect local logs plus repeated network calls to Polymarket and Polygon endpoints.

Vulnerability Patterns
  • 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
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/copy_trader.py:42
Finding

Unnecessary transmission of a deterministic private-key-derived identifier

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (7)

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The skill says 'No API keys needed' while instructing the user to export a POLYMARKET_KEY private key, which is materially more sensitive than an API key. This mismatch can cause users to underestimate the sensitivity of the credential they are providing, increasing the chance of secret compromise and unauthorized trading if the key is mishandled by the skill or runtime.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The skill says 'No API keys needed' while instructing the user to export a POLYMARKET_KEY private key, which is materially more sensitive than an API key. This mismatch can cause users to underestimate the sensitivity of the credential they are providing, increasing the chance of secret compromise and unauthorized trading if the key is mishandled by the skill or runtime.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The skill says 'No API keys needed' while instructing the user to export a POLYMARKET_KEY private key, which is materially more sensitive than an API key. This mismatch can cause users to underestimate the sensitivity of the credential they are providing, increasing the chance of secret compromise and unauthorized trading if the key is mishandled by the skill or runtime.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill advertises operational capabilities that would require access to environment variables, files, and the network, but it does not declare any explicit tool scope or permissions boundaries. In a trading skill that handles a private key and automation, missing scope declarations increases the risk of overbroad access, secret exposure, or unintended file/network operations if the skill is executed in a permissive runtime.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The top-level documentation states that the script will copy trades automatically, but the operational code does not perform live execution. In a trading skill, misleading capability claims can directly influence user behavior, causing them to rely on nonexistent automation, hedging, or risk controls while real trades never occur.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill metadata and CLI suggest it can automatically mirror trades, but in live mode the code explicitly refuses to execute and only logs a placeholder. In a financial trading context, this is a security-relevant integrity issue because users may enable what they believe is automated execution and make risk decisions based on false assumptions about market participation and protection.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This code persists trade-related state to state.json and appends runtime details to trades.log, but there is no confirmation prompt or broader user-facing warning that local files containing activity data will be created and updated. For a code file, local file writes that store user-relevant data should have some visible disclosure unless clearly communicated elsewhere.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.