hunt-business-logic

Identifies business logic vulnerabilities in web application workflows.

2|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-business-logic-carlos-reyes-utp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-business-logic
Source: https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda/tree/main/.agent/skills/hunt-business-logic
Command: npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-business-logic-carlos-reyes-utp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify business logic vulnerabilities that let attackers bypass verification, tamper with financial decisions, or abuse rate limiting for concrete financial, privacy, or authorization impact.

Core Features & Use Cases

  • Business logic vulnerability hunting across checkout, subscription, verification, webhook, and internal/employee surfaces to locate step-skip and trust-boundary failures.
  • Practical attack-surface signal detection using URL patterns, response/header anomalies, JavaScript hints, and common payment/verification misconfigurations.
  • End-to-end methodology to prove exploitability quickly by checking what an attacker can do, what the victim loses, and whether reproduction is feasible within minutes.

Quick Start

Use the hunt-business-logic skill to systematically test authentication boundaries, verification flows, rate limiting, and payment/webhook integrity for a target you’re assessing.

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 checkout and subscription workflows?

Hunt business logic bugs by enumerating auth and verification boundaries, testing step-skips and replayable tokens, validating server-side enforcement, and checking payment/webhook HMAC signature validation across checkout and subscription workflows.

What is a trust-boundary failure in application workflows?

A trust-boundary failure occurs when state-machine edges in application workflows improperly rely on client-side state, allowing attackers to skip verification steps, replay tokens, or tamper with webhook callbacks for unauthorized access.

How do I test rate limit bypass using spoofable IP headers?

Test rate limit bypass by probing rate-limiting weaknesses via spoofable IP headers, checking endpoints that fail to enforce server-side limits, and verifying if attackers can exceed thresholds to abuse high-traffic consumer platforms.

Does this methodology apply to marketplace and gig app security testing?

Yes, this methodology applies to marketplace and gig apps by targeting exploitable state-machine edges in checkout, verification, and webhook handling to identify unauthorized access, privacy impact, and financial loss vulnerabilities.

How do I validate webhook HMAC signature integrity for payment callbacks?

Validate webhook HMAC signature integrity by checking if payment callbacks enforce server-side signature validation, testing for replayable tokens, and probing for misconfigurations that allow tampering with financial decisions.

What is the best way to prove business logic exploitability quickly?

Prove business logic exploitability quickly by checking what an attacker can do, what the victim loses, and whether reproduction is feasible within minutes using URL patterns, response anomalies, and JavaScript hints.