T09 · Insecure Skill Coding Practices
- Location
SKILL.md:18- Finding
Brave API Key Exposed Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a legitimate Brave Search setup guide, but it asks users to handle API keys and make persistent proxy/system changes without enough guardrails.
Review the commands before installing or using this skill. Prefer secret-entry methods that do not put API keys in shell history, use temporary/session-scoped proxy settings first, and avoid the sudo proxychains configuration unless you understand the system-wide file change and have a rollback plan.
SKILL.md:18Brave API Key Exposed Through Command-Line Arguments
SKILL.md:122Brave API Key Exposed in Direct curl Test Command
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Test directly with curl:
curl -s "https://api.search.brave.com/res/v1/web/search?q=test&count=1" \
-H "Accept: application/json" \
-H "X-Subscription-Token: YOUR_API_KEY"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Test directly with curl:
curl -s "https://api.search.brave.com/res/v1/web/search?q=test&count=1" \
-H "Accept: application/json" \
-H "X-Subscription-Token: YOUR_API_KEY"
The skill instructs use of sudo tee to write a system-wide proxychains configuration under /usr/local/etc. Although this is a common administration step, elevated execution increases the risk of unintended system-wide changes, misuse if the pasted content is altered, and broader impact on networking behavior for other tools.
brew install proxychains-ng
# Configure
sudo tee /usr/local/etc/proxychains.conf <<EOF
strict_chain
proxy_dns
[ProxyList]
The skill instructs users to append proxy environment variables to ~/.zshrc, which makes the proxy persistent across future shell sessions and can silently affect unrelated tools and traffic. In a networking/proxy setup skill this is contextually relevant, but the lack of an explicit warning about persistence and broader system effects can lead to misconfiguration, privacy issues, or confusing network behavior.
No suspicious patterns detected.