hunt-mfa-flow

Validates server-side MFA enforcement, one-time code binding, and step-up authentication on sensitive endpoints.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-mfa-flow-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-mfa-flow
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-mfa-flow
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-mfa-flow-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-factor authentication implementations often fail silently: pre-MFA sessions may access protected resources, consumed recovery codes may be accepted twice, or sensitive actions may skip step-up verification. This Skill provides a structured, evidence-gated methodology to verify that MFA is actually enforced server-side on every endpoint. ## Core Features & Use Cases - MFA Enforcement Verification: Confirms that pre-MFA sessions and tokens are rejected by endpoints that should require a completed MFA challenge. - One-Time Code Binding Checks: Validates that consumed OTPs, TOTPs, and backup recovery codes are invalidated and bound to the correct account without brute-forcing codes. - Step-Up Authentication Testing: Checks whether sensitive operations (password, email, or fund changes) trigger an additional authentication challenge. - Use Case: During an authorized web application assessment, you test whether a session captured before MFA completion can directly access the account dashboard, and whether a used recovery code is accepted a second time. ## Quick Start Ask the agent to run the hunt-mfa-flow route against your authorized test accounts to verify MFA enforcement, recovery code invalidation, and step-up authentication on sensitive endpoints.

Frequently Asked Questions about hunt-mfa-flow

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

FAQPage Schema
How do I test if MFA is enforced server-side on every endpoint?

Establish a pre-MFA session with your own test account, then attempt to access resources that should require a completed MFA challenge. If the protected endpoint returns the resource without MFA completion, enforcement is missing; UI redirects or client-side flags alone do not count as evidence.

How to test backup code and recovery code invalidation?

Consume one of your own recovery codes legitimately, then replay the same code and observe whether it is rejected. A valid finding requires the reused code to be accepted again with an observable permission state change, not just a single anomalous response.

Does this MFA testing approach brute-force OTP codes?

No. The methodology explicitly prohibits OTP guessing or bulk code attempts. It only tests single consumption and binding of correct codes you own, and treats rate limits, CAPTCHAs, and WAF blocks as inconclusive results.

What preconditions are needed for MFA flow security testing?

You need two accounts you own, two separate browser profiles, resettable MFA test factors, and explicit authorization with locked scope. Testing stops immediately if it would touch production administrators, shared users, or cause irreversible side effects.

When should MFA flow testing stop or defer to other routes?

Stop when there is no testable recovery channel, when testing would lock accounts, or when it requires bulk OTP attempts. Rate-limit conclusions are handed to a dedicated rate-limit route and session issues to a session-testing route.