hunt-business-logic

Identifies business logic vulnerabilities in web and API authentication, payment, and verification flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-business-logic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-business-logic
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/hunt-business-logic
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-business-logic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you discover business logic vulnerabilities where the application makes security- or money-critical decisions based on untrusted inputs, missing server-side verification, or spoofable controls.

Core Features & Use Cases

  • Step-skip and verification bypass hunting: Identify flows where the UI enforces verification or authorization but the underlying endpoints still work when called directly.
  • Payment and webhook integrity testing: Probe checkout, payment initiation, and callback/webhook endpoints for missing server validation and missing/weak signature verification.
  • Rate-limit and trust-boundary probing: Check whether controls can be bypassed by rotating spoofable IP headers or replaying/altering stateful request data.

Use cases: hunting on e-commerce and payment flows, subscription and verification endpoints, marketplace/gig identity gates, and exposed internal/employee surfaces that are reachable without proper access control.

Quick Start

Use the hunt-business-logic skill on the target domain by asking me to enumerate authentication boundaries, verification flows, payment/webhook endpoints, and then draft findings focused on financial impact or unauthorized access.

Frequently Asked Questions about hunt-business-logic

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

FAQPage Schema
How do I find business logic vulnerabilities in payment and checkout flows?

To find business logic vulnerabilities in payment flows, you probe checkout, payment initiation, and callback endpoints for missing server-side validation and weak signature verification. This identifies payment tampering risks where applications trust spoofable client-side controls.

What is a verification bypass and how does it impact API security?

A verification bypass occurs when UI-enforced authorization or verification steps are skipped by calling underlying endpoints directly. It impacts API security by enabling unauthorized access when the server fails to enforce step progression independently.

How do I test for rate limit bypass using spoofed IP headers?

You test for rate limit bypass by rotating spoofable IP headers and replaying altered stateful request data against target endpoints. This probes trust boundaries to check whether access controls can be circumvented without triggering server-side restrictions.

Does this approach work for testing webhook validation and callback endpoints?

Yes, this approach works for webhook validation by probing callback endpoints for missing or weak signature verification. It maps attack surfaces within payment provider integrations to ensure reproducible financial impact from spoofed webhook payloads.

How do I validate authentication bypass findings on exposed internal endpoints?

You validate authentication bypass findings by mapping attack surfaces on exposed internal endpoints and testing server-side step enforcement directly. This ensures the access control vulnerability has reproducible impact within a short workflow.