T09 · Insecure Skill Coding Practices
- Location
references/aionmarket-polymarket.md:5- Finding
Reusable Polymarket Credentials Are Transmitted to a Third-Party Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is openly for live Polymarket trading, but it asks agents to handle wallet private keys and reusable trading credentials in ways that could expose funds or accounts.
Review before installing. Use this only if you understand that it can support live financial trading. Prefer pre-signed orders or an external wallet/signer, do not paste a wallet private key into chat, avoid storing private keys in environment variables, confirm the exact Aionmarket endpoint before sharing credentials, and require a final review of market, side, size, price, wallet, and live environment before any order is submitted.
references/aionmarket-polymarket.md:5Reusable Polymarket Credentials Are Transmitted to a Third-Party Service
clawhub.json:39Configurable Base URL Can Redirect Authentication Secrets to an Attacker-Controlled Host
assets/trade-request-template.md:5Workflow Solicits Raw Wallet Private Keys Through Chat or Environment Variables
The template explicitly asks the user to provide extremely sensitive secrets, including an Aionmarket API key, Polymarket API secret/passphrase, and especially a wallet private key, directly in conversational workflow text. Collecting these values in plain skill prompts creates a high risk of credential exposure through logs, prompt history, analytics, or unintended model handling, and the trading context increases severity because compromise could directly enable unauthorized trades or theft of funds.
The document recommends falling back to a live trade submission endpoint for order execution but provides no warning that this can trigger real, irreversible financial transactions. Because this skill is specifically designed to place Polymarket trades, the lack of execution-safety guidance materially increases the chance of accidental or unauthorized order placement, especially if an agent proceeds without clear confirmation, environment checks, or transaction review.
The skill enables live trading, wallet credential registration, and order submission, all of which are state-changing and can cause direct financial loss or irreversible account effects. While the procedure mentions confirming simulation versus live trading, it does not require an explicit user-facing risk warning or a strong confirmation gate immediately before performing these sensitive actions.
This reference material instructs the agent to collect and submit highly sensitive Polymarket API credentials without any warning about secrecy, storage minimization, redaction, or safe handling. In the context of an agent skill that explicitly accepts wallet credentials and private trading material, omission of these safeguards increases the risk of credential exposure through logs, prompts, transcripts, or unsafe persistence, which could enable unauthorized trading or account takeover.
No suspicious patterns detected.