bounty-hunter

Filters security findings to vulnerabilities reachable by external attackers via entry-point triage.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill bounty-hunter-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bounty-hunter
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/bounty-hunter
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill bounty-hunter-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ast-grep, osv-scanner.

What problem does it solve? Broad security sweeps flood you with findings, but most are unreachable from outside your trust boundary. This Skill narrows a repo-wide security scan down to only the vulnerabilities an external attacker can actually reach, so bug-bounty hunters and security engineers focus remediation effort where it matters. ## Core Features & Use Cases - Remote-Reachability Gate: Statically enumerates entry points (Python, JavaScript, TypeScript, Go, Lua, Solidity), confirms exposure and auth tier once up front, then keeps only findings with a full path from an external tier to the sink. - Three-Tier Auth Model: Tags findings as unauth-external, authenticated-any-user (the IDOR/BOLA tier), or privileged (escalation paths only), dropping local-only and same-trust-tier paths. - CVE Reachability Ranking: Consumes dependency CVE scans (osv-scanner, npm audit, or a same-session code-sec run) and ranks them by whether the vulnerable package sits on an externally reachable path. - Use Case: Before a bug-bounty pass on a web API, run the triage to get a report grouped by attack surface (e.g., POST /api/score (public, unauth)) with severity-ordered reachable findings and a trailing section annotating dropped local-only issues. ## Quick Start Run /bounty-hunter on this repository to show me which vulnerabilities are actually exploitable from outside.

Frequently Asked Questions about bounty-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which vulnerabilities are actually exploitable from outside?▼

Run a remote-reachability triage that enumerates every entry point, confirms exposure and auth tier once, then keeps only findings with a full taint path from an external tier to the sink. Local-only and same-trust-tier findings are dropped and annotated.

How to triage security findings for a bug bounty pass?▼

Group findings by attack surface (one group per external entry point), tag each with the lowest auth tier that reaches it, and rank severity as BROKEN, BLOCKER, default, or LOW. File only reachable findings as SECURITY TODOs.

Does the reachability analysis support TypeScript and Go codebases?▼

Entry-point enumeration supports TypeScript and Go, but the deterministic ast-grep rule pack does not run on .ts, .tsx, .go, .lua, or .sol files. Those languages get a model-only pass, which the report declares as uncovered rather than clean.

Can I run reachability triage in CI without a human present?▼

Yes, the --assume-public flag skips the confirmation prompt and treats every network entry point as external-unauthenticated. It deliberately over-reports as a fail-open conservative default, retaining the enumerator's exposure guess as a sort key.

What are the limitations of static reachability analysis?▼

Static analysis cannot know deployment topology, so exposure and auth tiers must be confirmed by the user once per run. The rule pack covers only certain file extensions, and dependency CVEs are ranked from consumed scans rather than an authoritative scan it owns.