hunt-captcha-bypass

Tests web applications for six CAPTCHA bypass patterns including field omission, token replay, and missing server-side validation.

1|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-captcha-bypass-marcboggs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-captcha-bypass
Source: https://github.com/marcboggs/BMAD-AppSec-Orchestrator/tree/main/.claude/skills/hunt-captcha-bypass
Command: npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-captcha-bypass-marcboggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During authorized penetration tests and bug bounty hunts, CAPTCHA mechanisms are often the only gate protecting login, registration, and password reset endpoints from automation. This Skill provides a structured methodology to verify whether CAPTCHA validation is actually enforced server-side or can be bypassed. ## Core Features & Use Cases - Six Bypass Patterns: Covers CAPTCHA field omission, empty/null values, token replay, cross-endpoint token reuse, rate-window gaming, and reactive CAPTCHA thresholds. - Concurrency Guidance: Explains how to satisfy sliding-window rate checks by firing concurrent requests rather than slow sequential ones. - Impact Chaining: Maps CAPTCHA bypass findings to downstream attack chains like brute force, account farming, and token flooding for accurate severity assessment. - Use Case: While testing a registration endpoint, intercept a successful submission, remove the g-recaptcha-response field, and replay the request — if the account is still created, you have confirmed missing server-side CAPTCHA validation. ## Quick Start Intercept a successful form submission with a CAPTCHA, resend it with the CAPTCHA field removed, and report whether the action still succeeds.

Frequently Asked Questions about hunt-captcha-bypass

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

FAQPage Schema
How do I test if a CAPTCHA is validated server-side?▼

Intercept a successful form submission, remove the CAPTCHA field entirely (e.g. g-recaptcha-response), and replay the request. If the action still succeeds, the server never validates the CAPTCHA and the bypass is confirmed.

How to test CAPTCHA token replay attacks?▼

Solve one legitimate CAPTCHA challenge, capture the token, then submit a second request reusing the same token. If the second submission succeeds, the token is not single-use and can be shared across automated requests.

Can CAPTCHA bypass testing work against reCAPTCHA and hCaptcha?▼

Yes, but only for validation-logic flaws like field omission, replay, and cross-endpoint reuse. Programmatically solving real reCAPTCHA or hCaptcha challenges via OCR or audio bypass requires external services and is out of scope for basic automated testing.

Why does sequential request testing fail against rate-based CAPTCHA triggers?▼

Sliding-window counters require N requests within a short time window, which slow sequential requests cannot satisfy. Fire requests concurrently so they arrive simultaneously and trip the counting middleware.

What severity is a CAPTCHA bypass vulnerability?▼

Standalone CAPTCHA bypass is typically Medium severity since it enables automation of rate-limited actions. It escalates to High or Critical when it removes the only gate protecting login brute force, registration farming, or password reset flooding.