business-logic-hunter

Detect business-logic flaws by testing workflow invariants, limits, races, and normalization.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill business-logic-hunter-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-logic-hunter
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/skills/business-logic-hunter
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill business-logic-hunter-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes references (resource) components.

What problem does it solve? Applications often enforce rules only in the UI or in individual requests, so every request looks valid while an unexpected sequence, value, or race violates product rules. This Skill turns product rules into machine-checkable invariants and provides concrete test recipes to prove or disprove real business-logic vulnerabilities without causing harm. ## Core Features & Use Cases - Invariant Modeling: Convert product rules (one-time actions, bounds, ownership, confirmations, sequence, concurrency) into testable statements before probing. - Test Recipes: Ready-made procedures for boundary mutation, fixed OTP values, parent/context swaps, race conditions on one-time actions, Unicode canonicalization bypasses, client-controlled authorization flags, and coupon replay. - Negative Controls: A stop-condition taxonomy (expected behavior, control elsewhere, theoretical without oracle, below impact threshold, duplicate root cause) that prevents filing non-reportable findings. - Use Case: While testing a ride-review endpoint, send an out-of-range rating value, then confirm via an authoritative read-back that the aggregate rating actually changed, proving a committed invariant violation rather than a UI anomaly. ## Quick Start Use the business-logic-hunter skill to model the invariants of this coupon redemption workflow and test whether it can be redeemed twice.

Frequently Asked Questions about business-logic-hunter

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

FAQPage Schema
How do I test for business logic vulnerabilities in a web application?

Model each product rule as a machine-checkable invariant, capture the normal request and authoritative read-back, then change one dimension at a time such as value, order, repetition, or concurrency. Confirm violations through authoritative state, not HTTP status codes alone.

How to test race conditions on one-time actions like coupons?

Establish a serial control first, then send a small synchronized batch of two to five parallel requests to a disposable free entitlement. A positive result means authoritative state grants more than the documented limit; multiple 200 responses with one committed grant are safe behavior.

What is a workflow invariant in security testing?

A workflow invariant is a product rule written in checkable form, such as redemptions per user being at most one or ratings bounded between 1 and 5. Testing changes one dimension of a valid request to see whether the invariant still holds in authoritative state.

When should a business logic finding not be reported?

Do not report when behavior is expected product design, when a downstream control rolls back the provisional success, when no durable impact occurs, or when the root cause is already tracked. Apply the negative-control taxonomy categories before filing any finding.

Can business logic testing be done safely without harming the target?

Yes, use sandbox accounts and reversible zero-value actions only. Never create real orders, consume inventory, sign asset-transferring transactions, brute-force OTPs, or run large concurrency batches, and always clean up test state afterward.