T09 · Insecure Skill Coding Practices
- Location
scripts/fadnote.js:31- Finding
Sensitive note content exposed through command-line arguments and shell history
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it claims, but it can automatically send highly sensitive secrets to a remote note service and documents unsafe command-line secret handling.
Install only if you are comfortable sending locally encrypted notes to the configured FADNOTE_URL service. Prefer piping content through stdin from a protected source, avoid putting passwords/API keys/private keys directly in command-line arguments, and require explicit confirmation before the agent creates notes for sensitive credentials.
scripts/fadnote.js:31Sensitive note content exposed through command-line arguments and shell history
The skill requires environment access and network communication but does not declare any explicit tool scope such as permissions or allowed-tools. In an agent ecosystem, that omission weakens reviewability and consent boundaries, making it easier for a skill that transmits sensitive user data to run with broader capabilities than users or the host expect.
The description emphasizes security properties but does not clearly warn users that their note content is still transmitted as ciphertext to a remote server endpoint. Even with client-side encryption, omission of that fact can mislead users about data flow, privacy expectations, jurisdiction, metadata exposure, and reliance on a third-party service.
The trigger phrases are broad enough to match ordinary user requests like 'share this securely' or 'secure this API key', which can cause the agent to automatically send highly sensitive content to an external service. Because this skill is specifically designed to handle secrets, overbroad activation materially increases the chance of unintended exfiltration of credentials, keys, or private data.
No suspicious patterns detected.