bug bounty

Security Community

Skill notes

THE ONLY QUESTION THAT MATTERS

"Can an attacker do this RIGHT NOW against a real user who has taken NO unusual actions -- and does it cause real harm (stolen money, leaked PII, account takeover, code execution)?" If the answer is NO -- STOP. Do not write. Do not explore further. Move on.

Theoretical Bug = Wasted Time. Kill These Immediately:

Pattern · Kill Reason "Could theoretically allow..." · Not exploitable = not a bug "An attacker with X, Y, Z conditions could..." · Too many preconditions "Wrong implementation but no practical impact" · Wrong but harmless = not a bug Dead code with a bug in it · Not reachable = not a bug

CRITICAL RULES

READ FULL SCOPE FIRST -- verify every asset/domain is owned by the target org NO THEORETICAL BUGS -- "Can an attacker steal funds, leak PII, takeover account, or execute code RIGHT NOW?" If no, STOP. KILL WEAK FINDINGS FAST -- run the 7-Question Gate BEFORE writing any report Validate before writing -- check CHANGELOG, design docs, deployment scripts FIRST One bug class at a time -- go deep, don't spray

AUTH-AWARE HUNTING (when bugs live behind a login)

Anonymous recon misses the bugs that pay most. IDOR, BOLA, mass-assignment, privilege escalation, auth bypass, SSRF behind login, and most LLM/agent bugs are invisible until you log in. Load auth once at session start and every downstream tool (httpx, katana, ffuf, nuclei, dalfox, the SQLi / SSTI / upload PoC verifiers) sends those headers automatically.

A->B BUG SIGNAL METHOD (Cluster Hunting)

When you find bug A, systematically hunt for B and C nearby. This is one of the most powerful methodologies in bug bounty. Single bugs pay. Chains pay 3-10x more.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
84 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@shuvonsec · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Required · GitHub
Operating systems
Linux · Windows · Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview bug-bounty.preview
# Real Examples

A: S3 bucket publicly listable (Low alone)
B: JS bundles contain OAuth client credentials
C: OAuth flow missing PKCE enforcement
Result: Full auth code interception chain

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.