T09 · Insecure Skill Coding Practices
- Location
SKILL.md:136- Finding
Plaintext Credential Storage in JSON Files
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 136
Vulnerability Type: Plaintext sensitive-data storage
Risk Level: MediumVulnerable Code Snippet:
markdown - Store credentials in `credentials/*.json`Technical Analysis
The Skill explicitly recommends storing credentials in JSON files but does not require encryption, restrictive filesystem permissions, repository exclusion, credential scoping, or integration with a secret manager. JSON files provide no confidentiality protection by themselves.
Credentials stored in this manner may be exposed through source-control commits, shared workspaces, backups, diagnostic archives, logs, or access by other local users and processes. Because the Skill directs users to register and operate accounts on several external platforms, exposed credentials could grant access to those accounts and their associated API capabilities.
Attack Path
- An agent follows the Skill and writes third-party API credentials to a file under
credentials/. - The file remains unencrypted and is not protected by an explicitly required restrictive permission policy.
- The file is accidentally committed to source control, included in a backup or diagnostic archive, shared with another agent, or read by another local process.
- An unauthorized party obtains the stored token or credential.
- The party reuses it against the relevant external service to act with the permissions assigned to that credential.
Impact Assessment
Exploitation could permit unauthorized access to affected third-party accounts. The precise scope depends on each exposed credential, but it may include reading account information, creating posts, submitting tasks, publishing content, voting, or performing other API operations available to the account. The issue does not, by itself, demonstrate operating-system privilege escalation or compromise beyond the permissions granted to the exposed c ...[truncated 11 chars]
- An agent follows the Skill and writes third-party API credentials to a file under
- Remediation
View remediation
Remediation Suggestions
- Replace plaintext JSON credential storage with an operating-system, cloud, or dedicated application secret manager.
- If file-based storage is unavoidable, encrypt credentials at rest and keep decryption keys outside the project directory.
- Require restrictive filesystem permissions so only the intended user or service account can read the credential file.
- Add credential paths to
.gitignoreand enforce secret scanning in local hooks and continuous-integration pipelines. - Use narrowly scoped, short-lived API tokens rather than reusable account passwords or broad tokens.
- Prohibit printing credentials in logs, prompts, generated reports, or agent transcripts.
- Document credential rotation and revocation procedures and rotate any secret suspected of exposure.
