T09 · Insecure Skill Coding Practices
- Location
src/index.js:13- Finding
API Key Exposure Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a narrow read-only trading-signal connector, but it tells users to put an API key directly on the command line, which can expose the credential locally.
Review before installing if you plan to use a real API key. Prefer a safer credential channel if available, rotate any key previously used on the command line, and treat returned trading signals as third-party financial data rather than local-only analysis.
src/index.js:13API Key Exposure Through Command-Line Arguments
The skill advertises network-backed functionality ('signal fetcher', API key usage, external homepage/API) but does not declare any explicit tool scope such as permissions or allowed-tools. This creates ambiguity about what external access the skill expects and weakens policy enforcement, making unintended or overbroad network use harder to review and constrain.
Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.
|:---|:---|:---|
| Free | $0/month | Manual monitoring, basic alerts, 25 API requests/day |
| Pro | $99/month | Real-time signals, 100 API requests/day |
| Enterprise | $499/month | Custom strategies, unlimited API calls |
## Usage
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
|:---|:---|:---|
| Free | $0/month | Manual monitoring, basic alerts, 25 API requests/day |
| Pro | $99/month | Real-time signals, 100 API requests/day |
| Enterprise | $499/month | Custom strategies, unlimited API calls |
## Usage
The README instructs users to pass an API key and interact with a cloud-hosted service, but it does not explicitly warn that requests, identifiers, and possibly trading-related data will be transmitted to a third-party backend. In a finance-related skill, that omission can mislead users about where sensitive data goes and increase the chance of accidental disclosure or inappropriate operational use.
This code performs outbound network calls and sends a bearer token in the Authorization header to a remote endpoint. While the tool's purpose is a connector, the file does not clearly warn users that their provided credential will be transmitted to an external service when commands run.