T09 · Insecure Skill Coding Practices
- Location
SKILL.md:128- Finding
Potential Disclosure of Sensitive Content to a Third-Party Classification Service
- Content
View full analysis
", "criteria_text": "" } ``` The documented Data Guard use case explicitly includes potentially secret-bearing content: ```json { "content_text": "", "criteria_text": "Contains hardcoded secrets (API keys with real values not placeholders like 'your-key-here', private key PEM blocks, database URLs with real passwords, excludes type definitions and process.env references)" } ``` Other documented inputs include complete skill files, private messages, and shell commands. ### Technical Analysis The Skill instructs the agent to submit arbitrary content to `https://ironclaw.io/api/v1/label` for remote classification. This network access is related to the declared threat-classification functionality, and the audit found no evidence of covert transmission or executable exfiltration code. In particular, the phrase at `SKILL.md:204` concerning “data exfiltration via fetch/HTTP” is classifier criteria rather than malicious code. Nevertheless, the remote-classification design creates a confidentiality risk. The `content_text` field may contain API keys, private keys, passwords, database URLs, private messages, proprietary skill source code, or sensitive shell commands. The documentation does not require local redaction, data minimization, informed per-request approval, or exclusion of credentials before transmission. It also does not state the remote service's retention, logging, secondary-processing, or deletion behavior. The Data Guard workflow is especially proble ...[truncated 1879 chars]- Remediation
View remediation
