hunt-mfa-bypass

Tests MFA and 2FA implementations for seven bypass patterns during authorized security assessments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aiohttp.

What problem does it solve? MFA implementations often contain logic flaws—missing rate limits, reusable OTPs, client-side-only checks, and workflow skips—that let attackers reach post-authentication state without a valid second factor. This Skill gives security testers a structured checklist of seven distinct MFA bypass patterns with concrete test procedures so no common bypass class is missed during an authorized engagement. ## Core Features & Use Cases - Seven Bypass Patterns: Covers OTP brute-force without rate limiting, OTP replay after use, response manipulation, MFA-step skip via direct navigation, race conditions on OTP validation, backup-code brute force, and remember-device trust escalation. - Ready-to-Run Test Procedures: Includes ffuf commands for OTP fuzzing, Burp-based response manipulation steps, and an aiohttp race-condition script. - Chain Escalation Guidance: Maps each primitive to severity outcomes and links to related skills (hunt-ato, hunt-race-condition, hunt-auth-bypass) for chaining MFA bypass into full account takeover. - Use Case: During a bug bounty hunt on a web app, trace the login flow in Burp, identify whether MFA is middleware-gated or per-endpoint, then systematically test each pattern—e.g., replaying a used OTP or skipping the /mfa route with a pre-MFA cookie—to confirm a Critical auth-flow bypass. ## Quick Start Ask the agent to test the target's MFA flow for bypass using the seven patterns, starting with OTP rate-limit and replay checks against the verify endpoint.

Frequently Asked Questions about hunt-mfa-bypass

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

FAQPage Schema
How do I test MFA for bypass vulnerabilities?▼

Trace the full authentication flow in Burp and check seven patterns: OTP rate limits, OTP reuse after success, response manipulation, skipping the MFA step via direct navigation, race conditions on validation, backup-code brute force, and remember-device cookie trust. Each pattern has concrete test steps with curl, ffuf, or Python.

How to brute force a 6-digit OTP with ffuf?▼

Use ffuf with a wordlist generated by seq -w 000000 999999 against the OTP verification endpoint, filtering 400 and 429 responses. Keep threads low (-t 5) to avoid rate-limit bans, since aggressive rates trigger 429 responses or account lockouts.

What is an MFA race condition attack?▼

An MFA race condition submits the same OTP through many parallel requests before the server marks it used. The skill provides an aiohttp script sending simultaneous verify requests; a single-packet HTTP/2 attack with Turbo Intruder widens the race window further.

When is an MFA bypass rated Critical versus High?▼

Standalone MFA bypass is typically High. It becomes Critical when chained with a password oracle or cookie theft enabling full account takeover, or when the MFA step can be skipped entirely via workflow bypass. Response manipulation indicating client-side-only checks is also Critical.

Can remember-device cookies bypass MFA from a new location?▼

Yes, if the remember-device token is not bound to IP address or user agent. Capture the cookie after completing MFA once, then present it from a different browser or IP; if MFA is skipped, the device trust is portable and enables account takeover from anywhere.