T09 · Insecure Skill Coding Practices
- Location
scripts/xerolite.mjs:56- Finding
API Credential and Trading Data Can Be Sent to an Arbitrary or Plaintext HTTP Endpoint
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill openly provides Xerolite/Interactive Brokers trading commands, but it exposes live order execution and trading credentials with too little local safety control.
Review this skill carefully before installing. Use it only with a tightly scoped Xerolite credential, prefer localhost or HTTPS-only trusted endpoints, avoid the --api-key flag, and require a human confirmation or paper-trading workflow before any live order command.
scripts/xerolite.mjs:56API Credential and Trading Data Can Be Sent to an Arbitrary or Plaintext HTTP Endpoint
scripts/xerolite.mjs:148Command-Line API Key Option Exposes Trading Credentials Through Process and Logging Surfaces
The skill explicitly supports placing live Interactive Brokers orders from natural language or automation, but it does not present a clear warning that these actions are financially irreversible and could cause immediate loss. In this context, the absence of a strong confirmation and risk warning is especially dangerous because accidental, ambiguous, or prompt-influenced requests could trigger real trades.
The skill declares environment and network capabilities via metadata and documented API usage, but it does not define an explicit tool scope such as permissions or allowed-tools. That increases the chance an agent can invoke broader capabilities than intended, especially because the skill handles API keys and can perform live trading actions over the network.
The API reference documents a live order-placement endpoint that can execute real trades, but it does not warn users that actions are financially consequential and potentially irreversible. In an agent skill context, this increases the chance that an automated system or operator invokes the endpoint without sufficient confirmation, safety checks, or environment separation from production trading.
Detected: suspicious.env_credential_access