Back to skill

Security audit

Probability Mean Reversion

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only Polymarket trading strategy guide with disclosed trading-risk caveats and no code execution, persistence, or credential access.

Treat this as trading-analysis support, not financial advice. Before using it for live trading, verify market liquidity, recent catalysts, time to resolution, spreads, and position sizing independently.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The invocation guidance is overly broad, using generic trading phrases like 'fade,' 'overreaction,' and 'panic buy' without clear eligibility checks or exclusions. That can cause the agent to apply a speculative strategy in inappropriate contexts, increasing the chance of unsuitable trading recommendations when market structure, liquidity, or catalyst conditions do not actually support mean reversion.

Content

No source excerpt is available for this finding.