Bug Bounty Ideas

Overview

Use the bundled README.md as an index of public bug bounty writeups, then research online sources to turn patterns into safe, authorized testing ideas. The goal is to produce practical hypotheses for a permitted target, not exploit instructions for unauthorized systems.

When to Use

Use this skill when the user asks for:

• Bug bounty ideas, hunting ideas, or vulnerability research inspiration.
• Online research based on the local README.md writeup index.
• Ideas for XSS, CSRF, clickjacking, LFI, subdomain takeover, DoS, authentication bypass, SQLi, IDOR, 2FA, CORS, SSRF, race condition, RCE, buffer overflow, or Android testing.
• Turning public writeups into safe test hypotheses for an authorized program.

Safety Boundary

Before giving target-specific testing advice, confirm the work is within an authorized bug bounty scope. If scope is unclear, ask for the program scope, allowed assets, test accounts, rate limits, and excluded testing. If the user only wants learning or generic inspiration, keep the output generic and non-operational.