T09 · Insecure Skill Coding Practices
- Location
scripts/run-loop.mjs:174- Finding
API Key Disclosed Through Process Logs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it claims, but it exposes the bot API key in logs and does not enforce that the key is sent only to a trusted HTTPS backend.
Review before installing or running. Only run this with a low-privilege Cubistic bot key, set BACKEND_URL manually to the intended HTTPS backend, avoid running loop mode where logs are retained, and rotate the key if it has already appeared in terminal, CI, or service logs.
scripts/run-loop.mjs:174API Key Disclosed Through Process Logs
scripts/run-once.mjs:145API Key Can Be Sent to an Untrusted or Plaintext Backend in Run-Once Mode
scripts/run-loop.mjs:141API Key Can Be Repeatedly Sent to an Untrusted or Plaintext Backend in Loop Mode
Referenced artifact was not completely inspected
- `scripts/run-once.mjs` — attempt one paint (gentle mode: only paints Void pixels)
Referenced artifact was not completely inspected
- `scripts/run-once.mjs` — attempt one paint (gentle mode: only paints Void pixels)
Referenced artifact was not completely inspected
- `scripts/run-loop.mjs` — repeat politely with backoff
Referenced artifact was not completely inspected
- `scripts/run-loop.mjs` — repeat politely with backoff
The skill instructs users to run Node scripts that use both environment variables and outbound network access, but it does not declare any tool scope or permissions metadata. This creates a transparency and policy-enforcement gap: an agent or reviewer cannot easily constrain or audit the skill’s ability to read secrets like API_KEY and send data to an external backend, which is especially relevant because the skill targets a public external service.
The script logs the full API_KEY at startup via the bot field, which can expose a live credential in terminal history, CI logs, process supervisors, or centralized log aggregation systems. Because this key is used as the X-Api-Key for authenticated actions, anyone who can read those logs may be able to impersonate the bot and perform unauthorized API operations.
Detected: suspicious.env_credential_access