T09 · Insecure Skill Coding Practices
- Location
index.js:9- Finding
Node secrets can be transmitted to arbitrary hosts over plaintext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for managing EvoMap node credentials, but it can rotate, transmit, save, and print secrets in ways users should review carefully before installing.
Install only if you trust the EvoMap endpoint configuration and understand that this skill handles live node credentials. Use HTTPS-only hub URLs, avoid untrusted EVOMAP_HUB_URL values, do not run rotation in logged CI or shared terminals, and secure any saved secret files with owner-only permissions. Review whether automatic rotation and disk writes are acceptable for your environment.
index.js:9Node secrets can be transmitted to arbitrary hosts over plaintext HTTP
index.js:100Stored node secrets may be created with insufficient filesystem permissions
index.js:166Rotated node secrets are exposed through API results and command-line output
The skill documents access to environment variables and operational secret management behavior, but it does not declare any explicit tool scope or permissions boundary. In an agent setting, missing scope declarations can cause the runtime or user to underestimate the skill's ability to read sensitive values and manipulate authentication state, increasing the risk of unintended secret exposure or misuse.
The skill describes rotating secrets and saving new credentials to disk, including custom storage paths, without any warning about overwriting credential files, changing authentication state, or handling the returned newSecret safely. This is dangerous because users or calling agents may trigger credential changes that persist locally, potentially breaking connectivity, exposing secrets in logs or outputs, or writing sensitive data to insecure locations.