offensive-business-logic skillA
offensive-business-logic is agent-read markdown (skill) from snailsploit/claude-red: Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows, role/tenant boundary violations, time-of-check vs use, anti-automation defeat, fraud-detection evasion, and subscription/quota abuse. Use when scoping an application after surface-.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Business Logic — Offensive Testing Methodology Business logic flaws are the highest-paying class of vulnerability for bug bounty and the hardest for scanners to detect. They live in the gap between what the developer specified and what an attacker can convince the system to accept. ## Quick Workflow 1. Map every multi-step flow as a state machine (states + allowed transitions + side effects) 2. For each transition, ask: who can call it, in what state, with what inputs, how many times 3. Probe each axis (state, identity, input, frequency) for assumptions 4. Combine flaws — single-axis flaws are usually low severity; chains are critical 5. Quantify financial impact per finding (loss-per-attack × scale) --- ## Reconnaissance — Mapping the Logic ### Build the State Machine For each user flow, draw: - **States**: cart, pending payment, paid, shipped, refunded, cancelled - **Transitions**: which API/UI action, which role, which preconditions - **Side effects**: balance change, inventory change, email, webhook Look for transitions that: - Skip intermediate states (`cart` → `shipped` without `paid`) - Are reversible when they shouldn't be (`shipped` → `cart`) …
Read the whole file at its exact version.
How to install
mdr add snailsploit/claude-red/offensive-business-logic@git:20260506.70e0c89mdr add snailsploit/claude-red/offensive-business-logic@sha256:4bd5fbf6bf70f98dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zty3fbnq7jo2azja)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13312 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
snailsploit/claude-red · 6,831 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zty3fbnq7jo2azja GET https://markdownregistry.com/api/v1/resolve?ref=snailsploit/claude-red/offensive-business-logic GET https://markdownregistry.com/api/v1/blob/4bd5fbf6bf70f98d0b11583e41d4d778044212df63576b31212edf34542779aa
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from snailsploit/claude-red
Every file in snailsploit/claude-red