Polymarket Alpha Suite

• Outcome: Review
• Latest audit: May 29, 2026 at 9:23 PM UTC
• Version:
  1.0.0

Overview

This trading skill mostly scans markets and records paper-trading signals, but it asks for sensitive wallet/API secrets for live trading that the code does not actually implement.

Review before installing. Treat this as a market scanner and paper-trading signal suite unless you independently verify live order placement. Do not enter a primary wallet private key; use a separate low-balance trading wallet or limited-scope API credentials, keep any .env file out of version control, and assume local data files may reveal your trading interests.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The setup guide explicitly instructs users to export and configure a raw wallet private key for live trading, which normalizes highly sensitive secret handling in a local `.env` workflow. Although the document later includes generic wallet-security advice, it does not place an immediate, explicit warning next to the private-key method that exporting and storing a private key can lead to irreversible wallet compromise and fund loss if the machine, repo, logs, or support channels are exposed.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The skill explicitly instructs users to place live trading credentials and private keys in a `.env` file or environment variables, but it does not warn that these values are secrets that must never be committed, logged, or shared. In a trading tool context, exposure of Polymarket API credentials or a private key could allow unauthorized trading or wallet compromise, making this a real secret-handling weakness even though it is documentation rather than executable code.

Missing User Warnings

Low

• Confidence: 76% confidence
• Finding: The script persistently writes detailed trading activity to a local JSON file without any access control, minimization, or user disclosure. On shared systems this can leak behavioral or financial information to other local users, and persistent state can be harvested or tampered with by malware or other processes.

Missing User Warnings

Low

• Confidence: 76% confidence
• Finding: The script rewrites the trade history file as resolutions arrive, again maintaining persistent local records without warning or integrity protection. This increases the window for local data exposure and tampering, especially in a continuously running watch mode.

Missing User Warnings

Medium

• Confidence: 84% confidence
• Finding: The watch command supports a non-dry 'LIVE' mode and emits actionable BUY signals while persisting them, but it does not require an explicit user acknowledgement of financial risk before running. In a trading skill that markets arbitrage opportunities, this can mislead users into treating output as ready-to-act trading advice and increases the chance of unintended financial loss or regulatory/compliance issues.

VirusTotal

64/64 vendors flagged this skill as clean.