hunt-mfa-bypass

Detect MFA/2FA bypass vulnerabilities across seven web application patterns.

3|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/cmndcntrlcyber/rtpi --skill hunt-mfa-bypass-cmndcntrlcyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-mfa-bypass
Source: https://github.com/cmndcntrlcyber/rtpi/tree/main/knowledge_seed/bug_hunter_skills/hunt-mfa-bypass
Command: npx skills add https://github.com/cmndcntrlcyber/rtpi --skill hunt-mfa-bypass-cmndcntrlcyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill hunts for Multi-Factor Authentication (MFA) and Two-Factor Authentication (2FA) bypass vulnerabilities in web applications.

Core Features & Use Cases

  • MFA Bypass Patterns: Identifies 7 distinct bypass patterns for MFA/2FA, including no rate limit on OTP, OTP replay, and backup code brute force.
  • Detection: Traces authentication flows, checks for MFA enforcement at the middleware or per-endpoint level, and verifies OTP entropy and rate limits.
  • Validation: Ensures that the attacker's session reaches the post-MFA state.

Quick Start

Use the hunt-mfa-bypass skill to check for MFA bypass vulnerabilities in your web application.

Frequently Asked Questions about hunt-mfa-bypass

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

FAQPage Schema
How do I detect MFA bypass vulnerabilities in a web application?

To detect MFA bypass vulnerabilities, you trace authentication flows to check for MFA enforcement at middleware or endpoint levels, verifying OTP entropy and rate limits. This identifies bypass patterns like token replay and backup code brute forcing.

What are common two-factor authentication bypass patterns?

Common two-factor authentication bypass patterns include lacking rate limits on OTP endpoints, OTP replay attacks, and brute forcing backup codes. Detection involves tracing these authentication flows to verify OTP entropy and middleware enforcement.

How do I check if my OTP implementation is vulnerable to brute force attacks?

Checking if an OTP implementation is vulnerable to brute force attacks involves verifying rate limits on authentication endpoints and assessing OTP entropy. Validation ensures an attacker session cannot reach the post-MFA state without proper authorization.

Do I need prior knowledge of authentication flows to audit for auth bypass issues?

You need prior knowledge of authentication flows and rate limits to effectively audit for auth bypass issues. Understanding these processes is required to trace enforcement at middleware or per-endpoint levels and validate post-MFA session states.

What is the best way to test backup code brute force vulnerabilities?

The best way to test backup code brute force vulnerabilities is to trace the authentication flow for backup code endpoints and verify rate limiting enforcement. This validates whether an attacker's session can improperly reach the post-MFA state.

Why does my MFA enforcement fail at the middleware level?

MFA enforcement fails at the middleware level when authentication flows lack proper per-endpoint checks or rate limits. Auditing identifies these gaps by verifying OTP entropy and ensuring unauthorized sessions cannot reach the post-MFA state.