T08 · Insecure Dependencies
- Location
clawhub.json:2- Finding
Unpinned Third-Party SDK Receives High-Value Trading Credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is clearly a trading tool, but it asks for high-value credentials and can place live trades using hardcoded market assumptions that do not match the advertised live momentum calculation.
Review before installing. Use only a dedicated low-value wallet and tightly scoped trading API key, do not enable --live until the strategy uses fresh price data, and treat dry-run as non-trading but not fully read-only because it may import markets into the remote platform.
clawhub.json:2Unpinned Third-Party SDK Receives High-Value Trading Credentials
trader.py:98Live Financial Trades Are Derived from Hardcoded and Potentially Stale Market Inputs
The skill declares required environment variables but does not specify any explicit tool scope or permission boundary. In an agent ecosystem, that omission can cause overbroad access to secrets and makes it harder for operators to understand that the skill is credential-dependent and potentially capable of live trading.
The manifest says only SIMMER_API_KEY is required, but later documentation also requires SOLANA_PRIVATE_KEY for live trading. This inconsistency can cause unsafe operator decisions, such as underestimating the sensitivity of the skill or supplying a blockchain private key without prominent warning in the manifest, which is especially risky given the financial-trading context.
The file presents the strategy as a static momentum template while also requiring live trading credentials during setup. That mismatch can mislead users into providing sensitive API and private-key material for a skill they may reasonably expect to be analysis-only or harmless by default, increasing the risk of accidental credential exposure and unintended live-trading capability.
The declared requirements do not match the stated skill description: the description says only SIMMER_API_KEY and simmer-sdk are required, but the manifest also demands a SOLANA_PRIVATE_KEY. This mismatch is dangerous because it obscures the true privilege level of the skill and can mislead users into granting a sensitive credential they did not expect to provide.
The manifest declares use of a private key for an automated trading skill without any visible warning or disclosure about handling a wallet-signing secret. In this context, that omission is especially risky because users may supply a real private key to an autostart-capable trading agent without understanding that compromise, misuse, or unintended transaction signing could lead to direct financial loss.
The manifest requests a SOLANA_PRIVATE_KEY even though the skill is described as a Kalshi/Simmer crypto momentum trader, creating an unjustified request for a highly sensitive signing credential. In an automated trading context, unnecessary private-key access materially increases the blast radius of compromise because the skill could expose or misuse wallet control unrelated to its stated purpose.
The script advertises dry run as "show opportunities, no trades," but run_strategy() still calls discover_and_import() even in dry-run mode, which invokes import_kalshi_market() and changes remote platform state. In a trading skill, users reasonably rely on dry-run mode to avoid any external side effects, so this mismatch can cause unintended account actions, altered watchlists/imported markets, and unsafe automation behavior.
The usage comment explicitly states that --live executes real trades via DFlow/Solana. In the implementation, live trading is performed through SimmerClient(... venue=venue ...) and get_client().trade(...), with venue defaulting to Kalshi; there is no visible DFlow/Solana execution path in this file.