T09 · Insecure Skill Coding Practices
- Location
bin/cli.js:67- Finding
Terminal Control-Sequence Injection Through Remote Bounty Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent bounty-scanning CLI, with expected API-token use and some security hardening gaps users should handle carefully.
Before installing, create dedicated low-privilege GitHub and Algora credentials, keep .env out of source control and shared workspaces, and rotate the keys if they may have been exposed. Treat terminal output and result URLs as untrusted because public issue data is printed directly, and prefer installing from a reviewed package with a lockfile or audited dependency versions.
bin/cli.js:67Terminal Control-Sequence Injection Through Remote Bounty Data
package.json:26Non-Reproducible Dependency Resolution Increases Supply-Chain Exposure
The command writes a GitHub token directly into a .env file from the shell, normalizing local plaintext secret storage and creating a strong risk of credential disclosure. In this skill's context, the token is an access credential for GitHub APIs, so leakage could enable unauthorized API use, repository data access within granted scope, and abuse of the victim's account capabilities.
clawhub install github-bounty-finder
# Configure
echo "GITHUB_TOKEN=your_token" > .env
echo "ALGORA_API_KEY=your_key" >> .env
# Scan for bounties
The README similarly instructs users to store an Algora API key in plaintext within .env without safety warnings or handling guidance. Because this is a monetization-focused bounty scanning tool that depends on external accounts, exposed API keys could be abused for unauthorized service access, quota consumption, billing impact, or account activity under the victim's identity.
# Configure
echo "GITHUB_TOKEN=your_token" > .env
echo "ALGORA_API_KEY=your_key" >> .env
# Scan for bounties
github-bounty-finder scan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
```bash
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY
```
### 扫描
The skill explicitly directs users to create and use GitHub and Algora API credentials, establishing a credential-handling path without accompanying safeguards, scope minimization guidance beyond a single GitHub scope, rotation advice, or warnings about secret storage. In context this is not inherently malicious, but it is dangerous because users may provision unnecessary or poorly protected tokens for a third-party skill, enabling unauthorized API access if the skill, environment, or logs are compromised.
### Getting API Keys
1. **GitHub Token**:
- Go to GitHub Settings → Developer settings → Personal access tokens
- Create a token with `public_repo` scope
2. **Algora API Key**:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
},
"requirements": [
"Node.js 18.0.0 or higher",
"GitHub Personal Access Token (free)",
"Algora API Key (free)"
],
"changelog": [
The README instructs users to place live API credentials into a local .env file without any warning about secure handling, accidental commits, shell history exposure, or least-privilege token scopes. While using .env files is common, omitting safety guidance increases the chance that sensitive GitHub and Algora tokens are leaked through source control, logs, backups, or shared workspaces.
The skill instructs users to provide GitHub and Algora credentials and to query external services, but it does not warn that repository search terms, usage patterns, and authentication tokens will be sent to third-party APIs. This omission can lead users to supply sensitive credentials without understanding the data exposure and trust boundary, increasing the risk of inadvertent credential misuse or privacy leakage.
This manifest is a JSON manifest file, so only SQP-1 and SQP-3 apply directly by file type, but the content also clearly documents required credentials in a user-facing description. It names a GitHub Personal Access Token and Algora API Key as requirements without any accompanying warning about how those secrets are used, stored, or transmitted, which is a meaningful omission for a skill that scans external services.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
try {
// Algora API endpoint (adjust based on actual API)
const response = await axios.get('https://api.algora.io/v1/bounties', {
headers: {
'Authorization': `Bearer ${this.algoraApiKey}`
},
This markdown file contains user-facing natural-language content exclusively in Chinese, including installation, configuration, and warning sections. Under the language/locale policy rule, forcing a specific language without user opt-in or a documented regional justification is a policy concern.
The description says the skill will 'Scan Algora/GitHub for high-value bounties with competition analysis and opportunity scoring' but does not specify when the skill should activate, what exact user intents should invoke it, or any exclusion conditions. In a manifest, this kind of broad capability description can be too general if used for invocation matching and may overlap with common requests about GitHub or bounty searching.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"author": "OpenClaw Skills",
"license": "MIT",
"dependencies": {
"axios": "^1.6.0",
"chalk": "^4.1.2",
"commander": "^11.1.0",
"dotenv": "^16.3.1",
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"license": "MIT",
"dependencies": {
"axios": "^1.6.0",
"chalk": "^4.1.2",
"commander": "^11.1.0",
"dotenv": "^16.3.1",
"node-fetch": "^2.7.0"
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"dependencies": {
"axios": "^1.6.0",
"chalk": "^4.1.2",
"commander": "^11.1.0",
"dotenv": "^16.3.1",
"node-fetch": "^2.7.0"
},
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"axios": "^1.6.0",
"chalk": "^4.1.2",
"commander": "^11.1.0",
"dotenv": "^16.3.1",
"node-fetch": "^2.7.0"
},
"engines": {
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"chalk": "^4.1.2",
"commander": "^11.1.0",
"dotenv": "^16.3.1",
"node-fetch": "^2.7.0"
},
"engines": {
"node": ">=18.0.0"
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.