T09 · Insecure Skill Coding Practices
- Location
scripts/searchconsole.py:152- 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 straightforward MyBrandMetrics Google Search Console query helper, but users should avoid putting API keys directly on the command line.
Install this only if you trust MyBrandMetrics with the connected Search Console data. Use `MYBRANDMETRICS_API_KEY` instead of `--api-key`, avoid sharing terminal output that may contain secrets, rotate any key previously pasted into shell history, and install dependencies in an isolated environment.
scripts/searchconsole.py:152API Key Exposure Through Command-Line Arguments
references/configuration.md:24Unpinned Third-Party Dependency Installation
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Security Rules
- Never commit API keys, access tokens, service account files, private keys, or
OAuth credentials.
- Avoid printing keys in terminal logs.
- Redact credentials before sharing command output or screenshots.
The skill advertises use of bash/python, network access, and environment-based API keys, but it does not declare an explicit tool/permission scope such as allowed-tools or permissions. That creates an avoidable trust gap: a runner or reviewer cannot easily constrain what the skill is allowed to access, increasing the chance of unintended network calls or secret exposure if the script or future edits become unsafe.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
BASE_URL = "https://api.mybrandmetrics.com/explorer/query"
DEFAULT_TIMEOUT = 30
No suspicious patterns detected.