Back to skill

Security audit

GitHub Bounty Finder Pro

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
bin/cli.js:67
Finding

Terminal Control-Sequence Injection Through Remote Bounty Data

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
package.json:26
Finding

Non-Reproducible Dependency Resolution Increases Supply-Chain Exposure

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (21)

Credential Access

High
Category
Privilege Escalation
Confidence
93% confidence
Finding

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.

Content

Scanner excerpt · README.md (reported line 16)May include surrounding context.

md
clawhub install github-bounty-finder

# Configure
echo "GITHUB_TOKEN=your_token" > .env
echo "ALGORA_API_KEY=your_key" >> .env

# Scan for bounties

Credential Access

High
Category
Privilege Escalation
Confidence
92% confidence
Finding

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.

Content

Scanner excerpt · README.md (reported line 17)May include surrounding context.

md
# Configure
echo "GITHUB_TOKEN=your_token" > .env
echo "ALGORA_API_KEY=your_key" >> .env

# Scan for bounties
github-bounty-finder scan

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · RELEASE.md (reported line 86)May include surrounding context.

配置

bash
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · RELEASE.md (reported line 87)May include surrounding context.

bash
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY

扫描

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · bin/cli.js (reported line 99)May include surrounding context.

js
```bash
cd skills/github-bounty-finder
cp .env.example .env
# 编辑 .env 添加 GITHUB_TOKEN 和 ALGORA_API_KEY
```

### 扫描

Credential Access

High
Category
Privilege Escalation
Confidence
77% confidence
Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 41)May include surrounding context.

md
### 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**:

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · clawhub.json (reported line 85)May include surrounding context.

json
},
  "requirements": [
    "Node.js 18.0.0 or higher",
    "GitHub Personal Access Token (free)",
    "Algora API Key (free)"
  ],
  "changelog": [

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

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.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · src/scanner.js (reported line 64)May include surrounding context.

js
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}`
        },

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
98% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 25)May include surrounding context.

json
"author": "OpenClaw Skills",
  "license": "MIT",
  "dependencies": {
    "axios": "^1.6.0",
    "chalk": "^4.1.2",
    "commander": "^11.1.0",
    "dotenv": "^16.3.1",

Unverifiable Dependency: axios has 16 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 26)May include surrounding context.

json
"license": "MIT",
  "dependencies": {
    "axios": "^1.6.0",
    "chalk": "^4.1.2",
    "commander": "^11.1.0",
    "dotenv": "^16.3.1",
    "node-fetch": "^2.7.0"

Unverifiable Dependency: chalk has 1 known advisory(ies) (MAL-2025-46969 (Malicious code in chalk (npm))), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 27)May include surrounding context.

json
"dependencies": {
    "axios": "^1.6.0",
    "chalk": "^4.1.2",
    "commander": "^11.1.0",
    "dotenv": "^16.3.1",
    "node-fetch": "^2.7.0"
  },

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 28)May include surrounding context.

json
"axios": "^1.6.0",
    "chalk": "^4.1.2",
    "commander": "^11.1.0",
    "dotenv": "^16.3.1",
    "node-fetch": "^2.7.0"
  },
  "engines": {

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 29)May include surrounding context.

json
"chalk": "^4.1.2",
    "commander": "^11.1.0",
    "dotenv": "^16.3.1",
    "node-fetch": "^2.7.0"
  },
  "engines": {
    "node": ">=18.0.0"

Unverifiable Dependency: node-fetch has 3 known advisory(ies) (CVE-2022-0235 (node-fetch forwards secure headers to untrusted sites); CVE-2022-2596 (node-fetch Inefficient Regular Expression Complexity ); CVE-2020-15168 (The `size` option isn't honored after following a redirect in node-fetch)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.

Content

No source excerpt is available for this finding.