Back to skill

Security audit

Kalshi Crypto Momentum Trader

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed dry-run-by-default trading skill, but live use can place real trades and requires high-value credentials.

Install only if you intend to run an automated trading tool. Start in dry-run mode, use a dedicated low-balance wallet and limited trading API key for live runs, review or pin simmer-sdk, and keep max position and max trades conservative.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Description-Behavior Mismatch

Medium
Confidence
97% confidence
Finding
The manifest requests `SOLANA_PRIVATE_KEY` even though the stated skill purpose is Kalshi crypto momentum trading based on price trends, with no disclosed Solana blockchain functionality. Requesting an unrelated private key expands the skill's access to highly sensitive credentials and creates a plausible path for secret misuse or exfiltration if the entrypoint code consumes it.

Context-Inappropriate Capability

High
Confidence
99% confidence
Finding
A Solana private key is a wallet-signing secret and is far more sensitive than a typical API key. In the context of a Kalshi trading bot, requiring that secret is unjustified by the declared functionality, making the capability suspicious and dangerous because compromise could enable unauthorized blockchain transactions or theft of wallet-controlled assets.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The manifest declares a highly sensitive secret requirement without any user-facing warning, justification, or disclosure of how that key will be used. This reduces informed consent and makes it easier for users to provide a wallet private key to a skill whose description does not prepare them for that level of access, increasing the risk of credential misuse.

Static analysis

No suspicious patterns detected.