Skip to content
Cybersecurity

MFA Fatigue Attacks: What They Are and How to Stop Them

BPro TechnologiesNovember 13, 20264 min readUpdated November 13, 2026
Person holding a phone showing a sign-in code screen in front of a laptop

/ Key takeaways

  • What is an MFA fatigue attack?
  • What staff should do
  • How to stop MFA fatigue

What is an MFA fatigue attack?

An MFA fatigue attack, also called push bombing, is when an attacker who already has someone's password sends repeated sign-in approval requests to their phone until they tap Approve, by accident or just to make it stop. CISA describes attackers generating hundreds of prompts in a short time. One approval is enough to let them in.

The important point: the prompts only appear because the password has already been stolen, often through password spraying, a breach of another website or phishing.

What staff should do

  • Never approve a sign-in you did not start, however many times it appears.
  • Report unexpected prompts to IT straight away; they mean your password is known.
  • Do not trust a phone call or message that says "just approve the request"; real IT staff never ask that.
  • Change your password through the normal route once IT confirms it is safe.

How to stop MFA fatigue

ControlWhat it doesStrength
Number matchingThe user must type the number shown on the sign-in screen into the app, so a blind tap cannot approveStrong interim fix; CISA recommends it where phishing-resistant MFA is not yet possible
Phishing-resistant MFA (passkeys, FIDO2 security keys)Sign-in is tied to the real website and device, so prompts cannot be pushed to the userStrongest; CISA's preferred option
Investigating denied promptsA denied prompt is treated as a sign the password may be compromisedCatches attacks early
User trainingStaff learn to recognise and report prompt spamNeeded alongside technical controls

Microsoft states that number matching is enabled for all Microsoft Authenticator push notifications, and users cannot turn it off. Businesses on Microsoft 365 with Authenticator push already have it; check that other MFA tools you use have an equivalent, such as Duo Verified Push.

Close the gap that made it possible

Because the attacker already has the password, also check for reused passwords, enable sign-in risk alerts where your licence includes them, and make sure denied prompts reach someone who will investigate. Our guide to fake IT support calls covers the social engineering that often accompanies these attacks.

Frequently Asked Questions

What is an MFA fatigue attack?

An attack where someone who already has a user's password floods their phone with sign-in approval prompts until the user approves one, by mistake or to stop the notifications. It is also called push bombing.

How do you prevent MFA fatigue attacks?

Use phishing-resistant MFA such as passkeys or FIDO2 keys where possible. Otherwise enable number matching, train staff to never approve prompts they did not start, and investigate denied prompts, as CISA recommends.

Does Microsoft Authenticator protect against MFA fatigue?

Microsoft states that number matching is enabled for all Authenticator push notifications, which stops a blind tap from approving a sign-in. Users must type the number shown on the sign-in screen.

/ Choose the next step

Move from article guidance to a practical review path.

Pick the route that best matches the issue behind the article so the next conversation starts with the right scope.

Security

Check your account and device protection

Tell us which sign-in methods and devices you use today. We identify the gaps that matter most first.

Use this when you want a clearer starting point before work is scoped.