Back to skill

Security audit

Bounty Hunter Agent

Security checks for vulnerabilities and agentic risk

Overview

This skill’s actual script is mostly a GitHub bounty scanner, but its documentation advertises autonomous PR and fix-session behavior without clear scope or approval safeguards.

Use this safely as a scan-only bounty discovery helper. Before relying on any autonomous PR or fix-session behavior, require explicit review before code changes, pushes, or PR creation, use a least-privilege GitHub login, and keep the local state file out of shared or synced directories if bounty activity history is sensitive.

Vulnerability Patterns
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
Findings (1)

Tainted flow: 'state_file' from os.environ.get (line 181, credential/environment) → open (file write)

Medium
Category
Data Flow
Content
"""Persist state to JSON."""
    STATE_DIR.mkdir(parents=True, exist_ok=True)
    state_file = STATE_DIR / "bounties.json"
    with open(state_file, "w") as f:
        json.dump(state, f, indent=2, default=str)
Confidence
84% confidence
Finding
The file write path is derived from `BOUNTY_STATE_DIR`, an environment variable that may be attacker-controlled in some execution contexts. This allows writes to an arbitrary filesystem location accessible to the process, which can overwrite application files, poison state, or interfere with other components if the script runs with elevated privileges or inside an automation platform.

Static analysis

No suspicious patterns detected.