MFA Fatigue: How Attackers Beat Your Push Notifications

We have spent a lot of energy telling businesses to turn on multi-factor authentication, and for good reason — it stops the overwhelming majority of account hacks. So it is jarring to open the news this month and read that attackers walked right past it at companies with serious security teams. The breaches making headlines in September show a technique called MFA fatigue, and it is worth understanding, because the fix is straightforward.

First, the good news: MFA still works

Let's be clear up front. MFA is still one of the best security moves you can make, and nothing here changes that. The attacks in the news did not break the math behind MFA. They exploited the weakest version of it and, more than anything, they exploited human nature. Understanding the trick is how you avoid it.

How MFA fatigue works

The most convenient form of MFA is the push notification: you try to log in, your phone buzzes, you tap "approve," and you are in. Quick and painless. That convenience is exactly what attackers turned against people.

Here is the play. The attacker already has your password — stolen, phished, or bought. When they try to log in, your phone gets a push notification asking you to approve. You did not request it, so you tap "deny." Then it buzzes again. And again. And again. Dozens of times. Late at night. During a meeting. Over and over.

Eventually one of two things happens. Either the person gets so worn down and annoyed that they tap "approve" just to make it stop, or they assume it must be a glitch and approve it to clear it. Either way, the attacker is in. Sometimes the attacker even messages the victim pretending to be IT — "Hi, we're doing some maintenance, please approve the prompt." That extra nudge is all it takes.

The attack isn't aimed at your technology. It's aimed at your patience. They don't need to break MFA — they just need you to give up and tap "approve."

The two breaches everyone is talking about

This is not theoretical. In the last few weeks, two of the most talked-about breaches in the industry came down to exactly this. In one, an attacker reportedly bombarded an employee with login prompts and then messaged them posing as tech support until they approved. In another, attackers ran a broad phishing campaign to capture credentials and MFA codes from companies one after another. Different details, same lesson: the password-plus-simple-approval combo is no longer enough on its own.

How to shut it down

You do not need to abandon MFA. You need to harden it. Here is what actually stops these attacks, roughly in order of impact.

1. Turn on number matching

This is the quickest, highest-value fix, and Microsoft and others have been rolling it out. Instead of a simple "approve/deny" button, the login screen shows a number, and you have to type that number into your phone app to approve. An attacker who is just spamming prompts does not know the number on your screen, so blind tapping no longer works. If your business uses Microsoft Authenticator, ask whether number matching is turned on. If it is not, it should be.

2. Limit the prompts

Many systems can be configured to stop sending endless approval requests — to lock things down after a handful of failed attempts instead of buzzing your phone fifty times. That alone defeats the "wear them down" strategy.

3. Move high-value accounts to phishing-resistant MFA

For your most sensitive accounts — owners, finance, IT administrators — consider a hardware security key (like a YubiKey). These cannot be fatigued and cannot be phished, because they only work on the real website and require a physical tap. No prompt to spam, nothing to approve by accident. For the handful of accounts that would do the most damage if stolen, this is worth the small cost. Getting these protections configured correctly is part of the cybersecurity work we set up for clients.

4. Tell your team the simple rule

Technology aside, your people are the last line of defense, and they can hold it easily once they know the rule: never approve a login prompt you did not personally just trigger. If your phone buzzes with an approval request and you were not actively logging in, that is not a glitch — it means someone has your password. Deny it, and report it. And no legitimate IT person will ever call or text asking you to approve a prompt for them. A two-minute conversation with your staff closes most of this gap, and reinforcing it is part of everyday managed IT support.

What to do this week

  • Check whether number matching is on for your Microsoft 365 or other MFA. If not, turn it on.
  • Tell your team the rule: unexpected prompt equals deny and report.
  • Identify your crown-jewel accounts and look at hardware keys for them.
  • Make sure repeated denials raise an alarm with whoever watches your systems, instead of being silently ignored.

The bottom line

The headlines this month are not a reason to second-guess MFA — they are a reason to upgrade it. The simple tap-to-approve version got too easy to game, but number matching, prompt limits, hardware keys for your most important accounts, and one clear rule for your team shut the door on MFA fatigue. None of it is expensive or complicated. If you would like a hand checking your setup and tightening it up for a business in Pinellas or Pasco County, we are happy to help.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment