T09 · Insecure Skill Coding Practices
- Location
SKILL.md:26- Finding
FoxReach API Key Exposure Through Command-Line Arguments and Inline Scripts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent for managing FoxReach, but it deserves review because it controls live outreach data and campaigns while giving unsafe API-key examples.
Install only if you intend the agent to manage a real FoxReach workspace. Use environment variables or a secret manager for the API key, avoid pasting keys into commands or scripts, and require explicit confirmation before deletes, account changes, or starting campaigns that send email.
SKILL.md:26FoxReach API Key Exposure Through Command-Line Arguments and Inline Scripts
The invocation guidance says to use the skill for specific FoxReach tasks 'or anything related to the FoxReach API.' That catch-all phrase is ambiguous and lacks clear boundaries, which could cause unintended activation for loosely related requests.
The skill explicitly says to never hardcode API keys, but then provides example code with a literal api_key value embedded in source. Even if shown as a placeholder, this trains operators or downstream agents to place secrets directly in scripts, shell history, logs, and transcripts, increasing the chance of credential exposure.
The one-liner shell example embeds an API key literal directly in the Python command, contradicting the stated guidance. This is dangerous because command-line literals are commonly exposed via shell history, process listings, debugging output, and agent logs, making accidental credential disclosure likely.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| Setting | Value |
|---------|-------|
| Base URL | `https://api.foxreach.io/api/v1` |
| Auth Header | `X-API-Key` |
| Key Prefix | `otr_` |
| Rate Limit | 100 requests/minute |
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| Setting | Value |
|---------|-------|
| Base URL | `https://api.foxreach.io/api/v1` |
| Auth Header | `X-API-Key` |
| Key Prefix | `otr_` |
| Rate Limit | 100 requests/minute |
The delete example performs an irreversible lead deletion with no warning, dry-run, or confirmation guidance. In an agent skill context, examples are often copied directly into automations, so this increases the chance of accidental destructive actions against real customer/prospect data.
The full campaign setup culminates in starting a campaign, which activates outbound email sending, but the example does not clearly warn that this triggers real outreach. In this skill's cold-email context, copied example code could immediately send messages to leads using assigned accounts, causing unauthorized outreach, compliance issues, and reputational damage.
This markdown file lists multiple DELETE operations, including soft-deleting leads and deleting campaigns, templates, and email accounts, but provides no cautionary note about data loss, reversibility, or operational impact. Under the markdown-file criteria, descriptions should warn about behaviors that could affect user data or system integrity.
Detected: suspicious.exposed_secret_literal