Quick answer
MFA fatigue, or push bombing, is an attack in which someone who already has a user's password sends repeated MFA push notifications until the user approves one to make them stop, or is persuaded to approve by a caller posing as IT support.
On this page
How It Works
The attacker obtains a password through phishing, credential stuffing or an infostealer, then triggers sign-in attempts over and over, often late at night. Many push-based MFA apps show a simple Approve button. A tired or confused user eventually taps it, sometimes after a message or call from someone claiming to be the help desk. Several high-profile breaches have started this way.
Why It Matters
Organizations often consider MFA the end of the account takeover problem. Push approval without context turns MFA into a social engineering target, giving attackers a valid session.
How to Test for It
- Check which MFA methods are allowed and whether simple push approval is still enabled.
- Review sign-in logs for bursts of MFA prompts and denied pushes followed by an approval.
- Test help desk procedures for resetting MFA and verifying callers.
- Run an authorized exercise to see whether staff would report unexpected prompts.
- Confirm alerts fire on repeated MFA denials.
How to Reduce the Risk
Turn on number matching and sign-in context in push apps, limit prompts per period, alert on repeated denials, move administrators and high-risk users to phishing-resistant methods such as FIDO2 keys or passkeys, and train staff that an unexpected prompt means their password is compromised.
Regulatory and Framework Context
For US organizations, CISA recommends phishing-resistant MFA and number matching as an interim step for push-based MFA.
Latest intel on this topic
Updated hourly from the daily briefing.
Common questions
What is number matching?
A push MFA setting that requires the user to type a number shown on the login screen into their app, so they cannot approve a sign-in they did not start.
What should staff do if they get unexpected MFA prompts?
Deny them, report it immediately and change their password, because someone already knows it.
For testers: finding write-ups
How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.
Change log
- November 13, 2026First published.