Short answer: an MFA fatigue attack, also called push bombing or prompt bombing, happens when someone who already has your password triggers dozens of “Approve sign-in?” notifications on your phone, hoping you will tap Approve to make them stop or by mistake. If you receive approval requests you did not start, deny every one, change your password immediately, and report it if it is a work account. The lasting fix is to switch from simple push approvals to number matching, passkeys or security keys.
Push-based multi-factor authentication (MFA) was designed to be easier than typing codes: you get a notification and tap a button. That convenience is exactly what attackers exploit. Push bombing was used in several widely reported corporate breaches in 2022, including the Uber compromise, where an attacker reportedly combined repeated prompts with a message pretending to be IT support. Since then, Microsoft, Okta, Duo and others have added protections, but many accounts still use plain approve/deny prompts.

How an MFA fatigue attack works
- The attacker gets your password, usually from phishing, a data breach, password reuse or info-stealing malware.
- They try to sign in repeatedly. Each attempt sends a push notification to your authenticator app.
- They add pressure. Prompts often arrive late at night or in long bursts. Some attackers message or call pretending to be the IT helpdesk: “We’re fixing a sync issue, please approve the prompt.”
- One tap gives them access. If you approve once, the attacker is in, often with a session that lasts days.
The important point: receiving the prompts means your password is already compromised. MFA is doing its job by stopping the attacker, as long as you do not approve.
Warning signs
- Sign-in approval requests you did not initiate, especially several in a row.
- Requests showing an unfamiliar location, device or browser.
- Calls, texts or chat messages from “IT” asking you to approve a prompt or read out a code.
- Emails about password reset attempts you did not make.
What to do if you are being push-bombed
- Deny every request. Never approve to make the notifications stop. If your app offers “Report” or “This wasn’t me”, use it.
- Change your password for that account from a device you trust, and anywhere else you used the same password.
- Sign out other sessions in the account’s security settings.
- Tell your IT or security team if it is a work account. They can block the attacker, check sign-in logs and see whether other staff are targeted.
- Do not trust callers who reference the prompts. Real IT staff do not need you to approve a login for them.
- If you already tapped Approve, change the password immediately, sign out all sessions, and report it. Speed limits the damage.
Settings that stop push bombing
| Protection | How it helps | Where to find it |
|---|---|---|
| Number matching | You must type a number shown on the login screen, which the attacker would have to give you | Default in Microsoft Authenticator for Entra ID; available in Duo, Okta and others |
| Additional context | Shows the app name and location of the sign-in attempt | Microsoft Authenticator, Duo |
| Passkeys | No password to steal and no prompt to spam | Google, Microsoft, Apple and many other accounts |
| Hardware security keys | Phishing-resistant; requires a physical touch on your own device | Most major platforms |
| Prompt rate limiting | Blocks or locks after repeated denied prompts | Admin settings in identity platforms |
Microsoft enforced number matching for all Microsoft Authenticator push notifications in Entra ID (formerly Azure AD) in 2023, and CISA recommends number matching as an interim step for organisations that cannot yet deploy phishing-resistant MFA. The strongest option, according to CISA, is FIDO-based authentication such as passkeys and security keys. See how to set up a hardware security key.
For organisations
- Enable number matching and additional context on all push-based MFA.
- Move administrators and high-risk staff to phishing-resistant MFA first.
- Set alerts for repeated MFA denials on a single account; that pattern is a strong indicator of compromise.
- Train staff that the helpdesk will never ask them to approve a prompt or share a code, and give them a simple way to report suspicious prompts.
- Use conditional access to block sign-ins from unexpected countries or unmanaged devices.
Why this matters for personal accounts too
Consumer services such as Microsoft accounts, Google accounts and some banking apps use push approvals. The same rules apply: an unexpected prompt means someone has your password. For personal accounts, switching to a passkey is the simplest upgrade. Compare options in 2FA methods compared.

Frequently asked questions
Does an MFA prompt mean I have been hacked?
It means someone entered your correct password. Your account is not yet compromised as long as you deny the request, but you should change the password right away.
Is SMS better than push notifications against this attack?
No. SMS codes can be phished or intercepted through SIM swapping. Number matching, passkeys and security keys are all better choices.
Can I turn off push notifications?
Many services let you choose another method, such as an authenticator code or passkey. Pick the strongest one the service supports.
What if I approved by accident?
Change your password immediately, sign out all sessions and check recent activity. For work accounts, contact IT at once.
Related: credential stuffing explained, what to do in the first hour after a hack, passkeys vs passwords.



