security-bounty-hunter

Detects remotely exploitable vulnerabilities in repositories for bounty report submission.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill security-bounty-hunter-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-bounty-hunter
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/security-bounty-hunter
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill security-bounty-hunter-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security researchers waste time triaging noisy static analysis findings that bounty platforms reject as out of scope or non-exploitable. This Skill focuses vulnerability hunting on remotely reachable, user-controlled attack paths that qualify for real bounty payouts. ## Core Features & Use Cases - In-Scope Pattern Detection: Identifies bounty-worthy vulnerability classes including SSRF, auth bypass, SQL injection, command injection, path traversal, deserialization, and auto-triggered XSS with CWE mappings. - Noise Filtering: Explicitly excludes low-signal findings such as local-only pickle loads, CLI-only eval, missing security headers, and self-XSS that platforms routinely reject. - Structured Triage Workflow: Guides scope verification, entrypoint discovery, semgrep-based triage, end-to-end code path reading, and minimal PoC validation. - Use Case: A researcher scanning an open-source project for a Huntr submission runs semgrep, filters out test and demo code, traces user input to a SQL sink in an HTTP handler, confirms exploitability, and drafts a report using the provided template. ## Quick Start Scan this repository for remotely exploitable, bounty-worthy vulnerabilities and draft a report for any confirmed findings.

Frequently Asked Questions about security-bounty-hunter

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

FAQPage Schema
How do I find exploitable vulnerabilities in a repository for bug bounties?▼

Start by checking program scope and exclusions, then map real entrypoints like HTTP handlers, uploads, and webhooks. Run semgrep for triage, read the code path end to end, and prove user-controlled input reaches an exploitable sink before reporting.

What vulnerability types qualify for bug bounty reports?▼

Bounty-worthy issues include SSRF via user-controlled URLs, authentication bypass, SQL injection in reachable endpoints, command injection, path traversal, remote deserialization, and auto-triggered XSS. These map to CWE-918, CWE-287, CWE-89, CWE-78, CWE-22, CWE-502, and CWE-79.

Which security findings do bounty platforms usually reject?▼

Platforms typically reject local-only pickle.loads or torch.load with no remote path, eval in CLI-only tooling, shell=True on hardcoded commands, missing security headers alone, self-XSS, and generic rate-limiting complaints without demonstrated exploit impact.

How do I use semgrep for vulnerability triage?▼

Run semgrep with --config=auto at ERROR and WARNING severity with JSON output, then manually filter results. Drop tests, demos, fixtures, and vendored code, keeping only findings with a clear network or user-controlled route to a meaningful sink.

What should a bug bounty vulnerability report include?▼

A report should include a description of the vulnerability, the vulnerable code with file path and line range, a minimal working proof of concept, the attacker impact, and the affected version or commit tested. Verify the issue is not a known duplicate first.