MFA Fatigue Attacks. When Criminals Wear Down Your Staff With Approval Prompts
Multifactor authentication works, but a stolen password plus a stream of approval prompts can still trick a tired employee into saying yes.
An MFA fatigue attack, sometimes called push bombing, starts with a stolen password. The criminal tries to sign in, which triggers an approval prompt on the genuine user's phone. Then they do it again, and again, sometimes in the middle of the night or during a busy working day. The hope is that the user will eventually tap approve, just to make it stop, or will assume it is a glitch. Once approved, the attacker is in.
It works because people are tired, busy and used to tapping yes. Some attackers also add social engineering, contacting the victim by phone or message and posing as IT support, telling them to accept the prompt to fix a problem. These tactics have been seen in real incidents against well known organisations. The lesson is that MFA is far better than no MFA, but not all MFA methods are equally strong.
The most important defence is to choose better methods. In Microsoft Authenticator, number matching means the user must type a number shown on the sign in screen into the app, instead of simply tapping approve, which makes accidental approval much harder. Microsoft has made number matching the standard behaviour for Authenticator push notifications. You can also show the application name and sign in location in the prompt, so users can spot a request from somewhere unexpected.
The strongest option is to move to phishing resistant methods, such as passkeys, Windows Hello for Business or FIDO2 security keys. These do not rely on a prompt that can be spammed or a code that can be handed over, so the whole class of attack disappears. Text message codes are the weakest common method and are best phased out where you can.
You can add technical controls around the edges. Conditional Access can restrict where and on what devices people sign in, so a login attempt from an unmanaged device in another country fails before any prompt is sent. Sign in logs and alerts can warn you when a user suddenly receives many failed MFA attempts, which is a clear signal that their password has been compromised. Finally, teach one simple rule: if you receive an approval prompt you did not start, deny it, do not approve it, and tell IT straight away. The password then needs changing and the account needs checking. A culture where people report this without embarrassment protects the whole business.
Dragonfly IT can strengthen your MFA setup and help staff recognise this kind of attack. Get in touch to find out more.
