4 MIN READ
MFA push notifications were sold as the answer to the password problem, and for a while they worked. Then attackers learned to bypass them, and the bypass worked because the notification design has a usability problem the threat actor exploits. The 2022 Uber breach, the 2023 Cisco breach, the 2024 MGM breach, the 2025 Snowflake breach. Different industries, different threat actors, the same shape. Phish the credentials, trigger the push, social engineer the user or the help desk into approving it, take the access. The push notification is the attack vector now, not the defence, and the only way out of the hole is to fix the design.
This is what the push gets wrong, what the attacks look like in production, and what a sensible enterprise does about it in 2026.
What the push gets wrong
Three design problems sit at the heart of the issue. The fatigue design runs as the most exploited. The account holder gets the prompt, the prompt asks for approval, and approval has become a friction the holder stops reading. A 2 a.m. login from a location the account has never visited produces a push the holder has been trained to tap through because the alternative is the help desk. The threat actor knows this, and keeps triggering the prompt until fatigue wins. Help desk confusion sits as the second. The account holder gets an unfamiliar push, calls the help desk to ask, the help desk tells the holder to approve the prompt to clear it. The help desk is now part of the social engineering surface, compromised by phone the same way the holder gets compromised by push. The no context problem rounds out the three. The notification does not show what application is asking, what device is asking, what location is asking, just a single “approve / deny” button. The holder is being asked to make a security decision without enough information to make a good call.
What the attacks actually look like
Three patterns account for the majority of MFA push attacks in incident data. The MFA fatigue attack, sometimes called push bombing, sits as the most common. The threat actor phishes the password, then triggers the push prompt repeatedly, dozens of times an hour, until the account holder either approves one to make the prompts stop, or calls the help desk and the help desk tells them to approve. The single approved prompt is enough. Help desk social engineering serves as the second pattern. A phone call to the help desk, the caller pretending to be a locked out holder, with the username and enough personal information from the LinkedIn profile to be plausible. The help desk walks the caller through approving the push that the caller just triggered. The SIM swap rounds out the three. Convincing the mobile carrier to transfer the phone number, the prompt lands on the attacker’s SIM, the attacker approves it. The SIM swap is rarer but harder to recover from because the legitimate holder no longer has the number.
What to do about it
Number matching amounts to the first move. The push prompt shows a number, the account holder has to type the same number on the device they are trying to log in from, and the threat actor who has the password but not the device screen cannot get the number. Microsoft rolled number matching out by default in 2023 and the data showed a measurable drop in MFA fatigue compromises after. Location and device context on the prompt sits as the second move. The holder sees the application, the device, the city, the IP reputation, and has the information to make a real decision rather than a guess. Phishing resistant MFA runs as the third. Passkeys, FIDO2 hardware keys like the YubiKey, Windows Hello. The authenticator cannot be phished, the authenticator cannot be prompt bombed, the authenticator cannot be SIM swapped, because the cryptographic proof binds to the legitimate origin. An enterprise that does those three moves closes the holes that the previous design left open. An enterprise that does not keeps issuing push prompts that the threat actor has learned to turn into an attack surface.
The bottom line
Number matching, device and location context, phishing resistant factors. The push prompt is the attack surface now, not the defence, and the only way out is to replace it with something the threat actor cannot socially engineer.
Sources & Further Reading
All claims in this article are sourced from primary documentation, vendor advisories, and reputable security researchers.
Spotted an error? Email the editor. Corrections are issued with a visible correction note.
Editorial standards. Every article on humanrequired.org is reviewed by a human editor before publication. AI may assist with drafting or research; final editorial control is human. Read the full standards.
