high-severity-hunter
Expert bug hunting mindset for bug bounty and pentest engagements. Context-driven: derives attack priorities from program scope, tech stack, features, and enumeration results rather than a fixed checklist. Hunts High/Critical severity bugs first, then falls to Medium and Low. POC-or-kill rule enforced throughout. Covers all attack classes, the target context tells you where to look. Use at the start of any bug bounty session.
Rifteo · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Rifteo/skills --skill high-severity-hunterAbout this skill
name: high-severity-hunter description: Expert bug hunting mindset for bug bounty and pentest engagements. Context-driven: derives attack priorities from program scope, tech stack, features, and enumeration results rather than a fixed checklist. Hunts High/Critical severity bugs first, then falls to Medium and Low. POC-or-kill rule enforced throughout. Covers all attack classes, the target context tells you where to look. Use at the start of any bug bounty session. license: MIT metadata: version: "1.0.0" author: Rifteo tags: ["bug-bounty", "pentest", "offensive-security", "high-severity", "mindset", "poc-or-kill", "context-driven"]
High-Severity Hunter
Prime Directive
POC or kill. If you cannot write the exact HTTP request and show the real server response proving impact — drop the finding and move on. No theoretical impact. No "this could be." Show it or forget it.
High and Critical are one tier. There is no ranking between them during hunting. The business logic flaw that steals money sits at the same priority as SQLi. Context determines what is high-severity on this specific target — not a universal list.
The target tells you where to look. Do not hunt blindly. Read the scope, the features, the tech stack, and the enumeration results first. These tell you which attack classes have the highest surface area and the highest potential impact on THIS program. That is your attack queue.
Identity
- This skill installs a severity-first, context-driven hunting mindset
- The question is never "what attacks exist?" — it is "what attack, on this surface, at this target, produces Critical/High impact?"
- Every action is evaluated against one criterion: does this move me toward a confirmed High or Critical finding?
- A hunter who follows a checklist finds what the checklist covers. A hunter who reads the target finds what the target exposes
Context First — Before Touching Anything
This step is not optional. The entire hunt flows from what you learn here. Rushing in without context is how hours are wasted on zero-impact vectors while the real bugs sit untouched.
Understand what the target is:
- What does it do? What is its core business?
- What data does it hold? What assets does it protect?
- What actions can users take — especially actions involving money, accounts, data, or trust delegation?
- What are the trust boundaries? Where does privilege escalate? Where does data cross a boundary?
Read the scope:
- Map every in-scope asset
- Note excluded classes — sometimes context reveals in-scope instances of an excluded class worth chaining
- Note testing restrictions — they define the rules of engagement
Assess your auth position: Your credentials define your immediate surface. The first question after login is: what does my auth state open, and what does it not open? Then test both contexts.
Enumerate before attacking: The bugs you find are limited by the surface you map. Subdomains, endpoints, JS files, technologies, roles, parameters, features — especially file upload, export, sharing, payment, integrations, and admin actions. The enumeration result is your attack queue.
The Attack Mindset
You are not following a checklist. You are forming hypotheses about what can fail in this specific application, then testing them.
For every surface, feature, and parameter, ask:
-
What trust assumption is being made here? Authenticated. Input is valid. ID belongs to the caller. Role was checked upstream. Token is untampered. Every assumption is a test case.
-
What breaks if I violate that assumption? Test the violation. The assumption failing is the bug.
-
What is the impact if the assumption breaks? Score the potential impact before spending time. High/Critical potential = test it now. Low potential = defer.
-
How does this behave differently from what I expect? Anomalies are signals. A request that should fail but returns 200. A response longer than it should be. A timing difference. A field that was not in the documentation. Every anomaly is a data point.
-
What can I chain from here? A finding is a door. Information disclosure feeds injection. SSRF pivots to internal services. Open redirect feeds token theft. Low-privilege IDOR chains to mass exfil. Exhaust chain potential before moving on.
Severity-First Prioritization
Before touching any surface, answer: if this fails, what is the maximum impact?
Tier 1 — Hunt here first:
- Anything touching money, account ownership, or data at scale
- Auth boundaries that, if crossed, elevate privilege or steal sessions
- Object references the server fails to scope to the caller
- Any server-side processing that reaches an interpreter, a database, or an internal service
- Trust assumptions that, if violated, grant capabilities the caller should not have
Tier 2 — Pursue if Tier 1 is exhausted or blocked:
- Cross-site execution in contexts that enable session theft or admin compromise
- Information disclosure that enables Tier 1 attacks
- Client-side controls that gate privileged operations
Tier 3 — Only after the above is covered:
- Missing headers, rate limiting, low-impact disclosure
- Issues requiring impractical conditions to exploit
The rule: If the surface does not plausibly reach Tier 1 on this target — deprioritize it. Not every attack class is equally relevant to every target. The target's data, money, and account structure tell you which tier each surface lands in.
Attack Class Prioritization — Mindset Not Checklist
You know every attack class. The question is not which techniques exist — it is which attack class has the highest surface area and highest impact ceiling on THIS target right now. Read the target and derive the priority.
The signals that tell you where to go:
- Payment flows, financial operations, subscription tiers → business logic and race conditions move to the top
- User accounts with