Cybersecurity

What Is MFA Fatigue? How Push Notification Attacks Work

Multi-factor authentication is valuable protection, but repeated approval prompts can be abused when an attacker already has a user's password.

Cybersecurity
What Is MFA Fatigue? How Push Notification Attacks Work

Learn what MFA fatigue attacks are, how repeated push notifications can trick users and how organizations can reduce the risk.

Read →

What is MFA fatigue?

MFA fatigue is an attack technique in which an attacker repeatedly sends multi-factor authentication prompts to a target, hoping the person eventually approves one out of confusion, distraction or frustration. It is also called push bombing in some security discussions.

The technique does not mean multi-factor authentication is ineffective. Instead, it targets the human decision made during an authentication request.

How does an MFA fatigue attack work?

  1. An attacker obtains or guesses a valid username and password.
  2. The attacker starts a login attempt against a service protected by MFA.
  3. The legitimate user's device receives an authentication prompt.
  4. The attacker repeats the process if the prompt is rejected.
  5. The attacker hopes the user eventually accepts a request that they did not initiate.

Why can repeated prompts be effective?

People make decisions quickly when they are busy. A user may receive several prompts and assume the application is malfunctioning. Repetition can also create pressure to approve a request simply to make the notifications stop.

This is why security awareness needs to explain not only how MFA works but also what an unexpected authentication request means.

Warning signs

  • An MFA prompt appears when you are not signing in.
  • You receive several prompts in a short period.
  • A login notification appears from an unfamiliar location or device.
  • A colleague or support contact unexpectedly asks you to approve a prompt.
  • Your account shows unfamiliar sign-in activity.

What should a user do?

Do not approve an unexpected request. Reject it if the service provides a deny option, change the password if compromise is suspected and report the event through the organization's security process. If the same password was reused elsewhere, change it on those services too.

How organizations can reduce the risk

Organizations can reduce MFA fatigue risk by using authentication methods that provide stronger user verification. Number matching, phishing-resistant authentication such as passkeys or hardware-backed security keys, and clear sign-in context can make accidental approval harder.

Organizations should also monitor repeated authentication failures and unusual prompt activity. Security teams can temporarily block or investigate suspicious sign-in attempts instead of treating each prompt as an isolated event.

Is MFA still worth using?

Yes. MFA adds an additional authentication factor and can significantly reduce the risk created by stolen passwords. The important lesson is to choose an appropriate MFA method and train users to treat unexpected prompts as security events rather than harmless notifications.

Frequently asked questions

Can MFA fatigue happen if my password is safe?

The attacker generally needs a way to initiate an authentication attempt, so protecting passwords remains important. Strong authentication can reduce the usefulness of stolen credentials.

Should I approve a prompt if I am not sure why it appeared?

No. If you did not initiate the login, do not approve the request. Verify the account through a trusted method and report repeated unexpected prompts.

What is the strongest protection against MFA fatigue?

Phishing-resistant authentication methods can remove or greatly reduce the usefulness of approval-based prompt abuse. Organizations should also combine strong authentication with monitoring and user education.

Response checklist: an MFA prompt you did not initiate

If an authentication prompt arrives unexpectedly, do not approve it and do not share a one-time code. Repeated prompts may indicate that someone has your password or is trying to pressure you into approving access.

  1. Deny the prompt when possible and stop interacting with the notification.
  2. Open the service directly using its official app or saved address; avoid links in unexpected messages.
  3. Change the account password if compromise is suspected, and review recent sign-ins and active sessions.
  4. Revoke unfamiliar sessions or tokens if the service provides that control, then contact the official support or security team.
  5. Report the time and approximate number of prompts through the approved channel. Do not include passwords or authentication codes in the report.

Controls organizations can test

  • Prefer phishing-resistant MFA, such as supported security keys or passkeys, for high-impact accounts.
  • Use sign-in risk signals and rate limits to detect repeated or unusual prompts.
  • Give staff a simple way to report unwanted prompts and a defined escalation route.
  • Test recovery procedures so users can regain access safely without bypassing identity checks.

MFA remains valuable, but not all MFA methods resist phishing equally. Choose a method appropriate to the account's risk and follow the service provider's secure setup guidance.

Key takeaway

MFA fatigue attacks demonstrate that account security includes both technology and human decisions. Strong passwords, phishing-resistant authentication, prompt reporting and monitoring work together to reduce the chance that an attacker can turn a legitimate security control into an opportunity for social engineering.