T09 · Insecure Skill Coding Practices
- Location
PUBLISH.md:43- Finding
Plaintext ClawHub Access Token Committed to Documentation
- Content
View full analysis
" ``` The repository contains a complete token value beginning with the `clh_` prefix. The credential value is redacted from this report to avoid further disclosure. ### Technical Analysis A ClawHub access token is embedded directly in a tracked documentation file. Because `PUBLISH.md` is distributed with the Skill and may also exist in repository history, anyone who downloads or clones the project can recover the credential without requiring local system access. Environment variables are an appropriate runtime mechanism for supplying credentials, but documentation must use placeholders rather than real values. Committing the token defeats the confidentiality provided by the environment variable. Even if the token is later removed from the current file, it may remain accessible through Git history, package archives, mirrors, caches, forks, or previously published Skill versions. ### Attack Path 1. An attacker downloads the Skill package or clones the public repository. 2. The attacker opens `PUBLISH.md` or searches the repository for token prefixes such as `clh_`. 3. The attacker extracts the plaintext `CLAWHUB_TOKEN`. 4. The attacker submits the token to the ClawHub CLI or API. 5. If the token remains valid, the attacker performs any operations allowed by its assigned scope, potentially including unauthorized package publication or modification. 6. A malicious Skill version could then be distributed to downstream users as a supply-chain attack. ### Impact Assessment If the token is valid, the attacker may obtain the ClawHub account or publication privileges associated with it. The exact privileges cannot be determined from the repository alone and depend on server-side token scope. Potential ...[truncated 447 chars]- Remediation
View remediation
