Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-mfa-bypassWeb and bug bounty

web-mfa-bypass

⁨Defeat a second authentication factor — OTP/TOTP, SMS, push, or backup codes. Load when login has a 2FA/MFA step and you want to reach the account without the factor, on "2FA bypass", "OTP brute", "MFA", or during account-takeover work. Signals: an OTP/verification screen after password, a "verify y⁩

v2026.10.14-ee0e0c54 installs+4 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-mfa-bypass

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
KrbQBvqpe7…j5GVEqBg==The CLI checks the SHA-256 and the signature before it writes a file.
Packaged819d3b8…eaeaab90
d819d3b88ee8…b87eeaeaab901 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-mfa-bypass@ee0e0c5

When it applies

Authentication has a second step after the password. MFA is only as strong as its enforcement — the common flaws are in the flow, not the crypto, and each is worth a quick check before assuming the factor is solid.

Why it works

The second factor is usually bolted onto a stateful flow, and the server often trusts the client to follow it. Skip the step, replay a state, or brute a short code with no rate limit, and the factor never actually gates access.

Method — work the checklist

  1. Missing server-side enforcement: complete step 1, then request a post-auth endpoint directly (forced browsing) or reuse the step-1 session — if it works, 2FA is cosmetic.
  2. No rate limit on the code: brute the 6-digit OTP (Turbo Intruder); watch for missing lockout, or a lockout you can reset by re-triggering send. Also test code reuse and non-expiry.
  3. Response/flag manipulation: flip "mfa_required":true→false, verified:false→true, or a 200/302 the client trusts to advance.
  4. Flow/logic: change the account/email between step 1 and 2 (bind your factor to their session), downgrade to a factor you control, or use password-reset to skip MFA entirely.
  5. Backup/remember: weak/guessable backup codes, a "remember this device" cookie that's static or forgeable, or OAuth/SSO paths that skip MFA.

Gotchas

  • Account lockout can burn the test account — throttle and use your own accounts.
  • Distinguish "reached the OTP screen" from "reached the account" — only the latter is the bypass.
  • Some apps enforce MFA at sensitive actions, not login — test the step-up too.

Verify success

You reach the authenticated account (or perform the MFA-gated action) without presenting a valid second factor, reproducibly from a clean session with test accounts.

References

PortSwigger 2FA bypass labs; OWASP Authentication Testing (OTP/MFA); OWASP ASVS auth requirements.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5d819d3b8Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login