MFA Fatigue Attacks: Why Two-Factor Wasn't Enough

SMS one-time codes were defeated by SIM swapping. App-based push 2FA was defeated by MFA fatigue. The next defense — phishing-resistant MFA — is what every Indian SMB should be migrating to before their cyber-insurance renewal asks for it.
How MFA fatigue works
The attacker has the user's password (from a credential dump or phishing). They start a login. The user gets a push notification. They deny it. The attacker tries again. And again. And again. Eventually a tired user — maybe at 11pm, maybe in a meeting — taps "Approve" to make the noise stop. The attacker is in.
It is not a theoretical attack
Uber, Cisco, and Microsoft all confirmed MFA fatigue compromises. Public post-mortems show the technique works against well-trained users in well-run security programs. If it works against them, it works against your accountant.
The phishing-resistant fix
Phishing-resistant MFA binds the second factor to the origin of the login attempt. The most common implementations are FIDO2 / WebAuthn (hardware keys like YubiKey, or platform authenticators like Touch ID, Windows Hello, Android biometric). The hardware key cryptographically refuses to authenticate to a wrong domain — it does not matter how convincing the phishing site looks.
Migration path for SMBs
- Roll out FIDO2 to admin and finance accounts first. These are the highest-blast-radius identities.
- Use number-matching push as an interim — Microsoft, Okta, Google all support it. It defeats the simple "tap to approve" pattern.
- Disable SMS-based MFA except as last-resort recovery. SMS is not MFA in 2026.
- Distribute two FIDO2 keys per user (primary + backup). Enroll both before deactivating push.
What it costs
Hardware keys range from ₹2,000 to ₹6,000 per unit. For a 50-person company, full FIDO2 rollout is ₹3-6 lakh of hardware plus a week of IT effort. Compare that to the average ransomware incident cost of ₹2-5 crore for an Indian mid-market firm and the math is obvious.
If you need help with rollout, our managed IT team handles FIDO2 enrollment campaigns end-to-end.

Further reading
Frequently asked questions
How does an MFA fatigue attack work?
The attacker has the user's password (from a credential dump or phishing). They start a login. The user gets a push notification. They deny it. The attacker tries again.
Have MFA fatigue attacks worked against large companies?
Uber, Cisco, and Microsoft all confirmed MFA fatigue compromises. Public post-mortems show the technique works against well-trained users in well-run security programs.
How should an SMB move to phishing-resistant MFA?
Roll out FIDO2 to admin and finance accounts first. These are the highest-blast-radius identities. Use number-matching push as an interim - Microsoft, Okta, Google all support it.
