MFA Fatigue 2025:
Protect Your Accounts with Passwordless Authentication

MFA Fatigue 2025: Protect Your Accounts with Passwordless Authentication
📜 Reading Invitation

« Traditional MFA is bypassed by sophisticated attacks like MFA bombing and AiTM phishing. Discover 2025 statistics, its history, how it works, and why passwordless solutions (FIDO2, Passkeys) are the future. Protect yourself without throwing everything away. »

📋 Key Points 2025

🔴
MFA Fatigue

Harassment hacking that pushes you to make mistakes. Striking example: the Uber breach.

🟠
AiTM Phishing

Pro-grade technique intercepting everything in real time, even your OTPs ("EvilProxy" kits).

🔵
FIDO2 & Passkeys

The end of phishing? Passwordless authentication emerges as the new standard.

🟣
SIM-Swap

Line hijacking costing millions. SMS codes must now be phased out completely.

🟢
MFA: The Basics

What it is, who it's for, how it works: key fundamentals decrypted clearly.

🟡
Active Vigilance

Why you must never disable MFA despite its recognized architectural weaknesses.

⚫
2025 Plan

The ultimate chronological checklist to safeguard all your critical accounts.

📜 Preamble

MFA, does that ring a bell? This acronym is everywhere in our digital world. Your banking app, your email, your online stores, your administrative access... it's there, lurking in the shadows, demanding a code or validation. Sometimes, it annoys us with its incessant notifications. But did you know that this Multi-Factor Authentication, this essential shield, could also "fatigue"? And when it fatigues, your security can falter.

🎯 1. Introduction

  • An outdated paradigm: Traditional MFA is no longer an infallible barrier against cyberattacks.
  • Emerging threats: Techniques like MFA bombing (notification fatigue) and AiTM phishing exploit its weaknesses.
  • Real impact: "MFA Fatigue" attacks show a global increase of 2.75x (i.e., +175%) for ransomware attacks in 2024, leading to heavy fines (e.g., T-Mobile, $33M fine in 2025).
  • The response: Moving to robust standards like FIDO2 and using Passkeys constitute the new frontier of authentication.
  • Our goal: To provide you with clear analysis and practical solutions to strengthen your account security.

🛡️ 2. Fundamentals: MFA, An Essential Shield (But Perfectible)

📖 2.1. MFA: The Basics - What is it, who is it for, how does it work?

Multi-factor authentication (MFA) is based on a simple principle: requiring multiple distinct identity proofs to access an account. These proofs are divided into three categories:

Something you know

A password, a PIN code.

Something you have

Your phone (to receive an SMS or notification), a physical security key.

Something you are

A fingerprint, facial recognition (biometrics).

The process is standardized: entering credentials → request for a second proof → validation → access granted. According to Microsoft, this method blocks over 99% of automated attacks.

⏳ 2.2. A Brief History of MFA

  • 1984: Invention of the first physical tokens (RSA SecurID)
  • 2000s: Standardization with the OATH initiative (HOTP, TOTP)
  • 2010s: Democratization following mega data breaches (Yahoo, Adobe)
  • 2020+: Era of "passwordless" with FIDO2/WebAuthn

👥 2.3. Its Daily Use: For Whom, For What?

Individuals

Protection of email (gateway to all accounts), online banking, social networks

Businesses

GDPR compliance, protection of cloud access (Office 365, AWS), securing customer data

📊 2.4. Where to Find MFA? The 2025 Ecosystem

CategoryExamplesSecurity Level
Web AppsGoogle, Microsoft, AWSMedium (vulnerable to AiTM)
Mobile AppsBanking apps, AuthenticatorsHigh (fatigue risk)
HardwareYubiKey, Google TitanVery High (anti-phishing)
Social NetworksX (Twitter), Facebook, LinkedInBasic (upgrade recommended)
EnterprisesSalesforce, SAP, corporate VPNAdvanced (conditional policies)
IoT / EmergingNest, Ring, connected carVariable (in development)

⚔️ 3. Modern Attacks That Bypass Classic MFA

💣 3.1. MFA Fatigue: The Harassment That Pushes You to Make Mistakes

MFA bombing exploits human weakness rather than technology. The attacker, after obtaining your credentials (through phishing or data leaks), triggers dozens of login attempts. Your phone then receives an avalanche of notifications "Do you want to approve this login?" Exhausted or distracted, you end up pressing "Approve" to stop the spam, forcing access to the hacker.

Statistics

+175% attacks in 2024 (Microsoft)

Real example

Attack against Uber in 2022 where an employee gave in to fatigue

🎣 3.2. AiTM Phishing: The Pro Technique That Intercepts Everything

Adversary-in-the-Middle (AiTM) is a sophisticated phishing technique using an invisible proxy. When you enter your credentials on a fake site, they are relayed in real time to the real site. When the latter requests MFA, the proxy forwards the request to you and intercepts your code or session cookie. The hacker can thus impersonate your session without ever having your credentials.

Available kits

EvilProxy, Tycoon 2FA (Phishing-as-a-Service)

Consequence

Makes SMS and TOTP codes obsolete

📱 3.3. SIM-Swap: The Line Hijacking That Costs Millions

SIM-swap specifically targets SMS MFA. The hacker persuades your carrier to transfer your number to their own SIM card. They thus intercept all your SMS validation codes, potentially emptying your bank accounts or stealing your identity.

2024 Figures

$26 million in losses in the USA (DeepStrike)

2025 Figures

$33 million (T-Mobile conviction, DeepStrike)

Global statistics

+1055% unauthorized attacks in the UK in 2024 (Cifas)

Recent example

Leak of 850,000 customer data at Orange Belgium in 2025

📋 3.4. Summary Table of MFA Threats in 2025

AttackMechanismVulnerabilityExample
MFA FatigueNotification floodingHuman weaknessUber (2022)
AiTM PhishingInterceptor proxyTrust in websitesEvilProxy kits
SIM-SwapFraudulent portingSMS dependencyOrange Belgium (2025)

👁️ 3.5. Visualizing Attacks: Explanatory Diagrams

Visually understanding different attack scenarios helps better grasp risks. Here are three diagrams illustrating respectively: the normal authentication process, an attack targeting an individual, and a sophisticated attack targeting an SME.

Diagram legend:
Malicious entity or attacker's action
Failure point or victim's action
Legitimate system

🔒 3.6. Secure Authentication Process

Secure Authentication Process

This diagram illustrates the normal flow of a secure MFA authentication, without any attack. Note the multiple verifications and the creation of a secure session.

👤 User (Legitimate)
🌐 Web Browser
🔑 Authentication Server
🛡️ Application / Website

🟢 Phase 1: Secure Login Initiation

1User ➔ Browser
Accesses official URL
2Browser ➔ Website
HTTPS request (GET /login)
3Website ➔ Browser
Returns login form
4Browser ➔ User
Displays login page

🟠 Phase 2: Authentication (Credential Verification)

5User ➔ Browser
Enters credentials (Login + Password)
6Browser ➔ Auth Server
Sends credentials (encrypted TLS channel)
7Auth Server ➔ Auth Server
Verifies password (secure Argon2/bcrypt hash)
8Auth Server ➔ Browser
1st factor validated + Triggers MFA challenge

🔵 Phase 3: MFA Verification (Double Guarantee)

9Browser ➔ User
Displays MFA code field
10User ➔ Trusted Device
Generates TOTP code or approves FIDO2 push notification
11User ➔ Browser
Enters 2nd factor verification proof
12Browser ➔ Auth Server
Sends MFA proof for cryptographic validation
13Auth Server ➔ Auth Server
Validates cryptographic signature or time-based token

🟣 Phase 4: Session Establishment

14Auth Server ➔ Website
Authentication successful confirmed
15Website ➔ Website
Creates encrypted user session
16Website ➔ Browser
Access granted + Session cookie HttpOnly, Secure, SameSite=Strict
17Browser ➔ User
Redirects to secure dashboard

🟡 Phase 5: Continuous Interaction (Secure)

18User ➔ Browser
Browses protected site
19Browser ➔ Website
Sends session cookie with each authenticated request
20Website ➔ Website
Verifies session cookie and authorization
21Website ➔ Browser
Returns requested data
22Browser ➔ User
Displays secure content

👤 3.7. Attack on an Individual (AiTM Phishing)

Attack on an Individual (AiTM Phishing)

This attack typically targets personal accounts (email, social networks, banking). The attacker uses an invisible proxy to intercept credentials and MFA code in real time.

👤 Victim (Individual)
🚨 Malicious Proxy (EvilProxy / AiTM)
🛡️ Real Service (Gmail, Facebook...)

🟥 Phase 1: Lure & Identity Theft

1Victim ➔ AiTM Proxy
Clicks on phishing link
URL looks legitimate to the naked eye (e.g., gmail-security.com)
2AiTM Proxy ➔ Real Service
Relays request in real time to the genuine site
3Real Service ➔ AiTM Proxy
Returns genuine login page
4AiTM Proxy ➔ Victim
Displays page (visually identical to genuine portal)

🟧 Phase 2: Credential Theft

5Victim ➔ AiTM Proxy
Enters confidential credentials
Thinking they are on the genuine website
6AiTM Proxy ➔ AiTM Proxy
Intercepts and stores stolen credentials
🚨 Stolen Credentials
7AiTM Proxy ➔ Real Service
Injects stolen credentials into genuine login endpoint

🟨 Phase 3: MFA Bypass

8Real Service ➔ AiTM Proxy
Demands second-factor MFA validation
9AiTM Proxy ➔ Victim
Forwards MFA input challenge to victim
10Victim ➔ AiTM Proxy
Enters MFA code (valid for 30-60 seconds)
11AiTM Proxy ➔ Real Service
Injects MFA code in real time into genuine session
🚨 Active 2FA Bypass

🟪 Phase 4: Session Theft (Critical Failure Point)

12Real Service ➔ AiTM Proxy
Authentication successful + Issues authenticated session cookie
13AiTM Proxy ➔ AiTM Proxy
Captures and exfiltrates live session cookie (session hijacking)
🚨 Session Cookie Hijacking
14AiTM Proxy ➔ Victim
Redirects victim to fake error or maintenance page
Victim suspects a minor technical glitch and remains unaware

⬛ Phase 5: Complete Account Takeover

15Attacker ➔ Real Service
Injects stolen session cookie directly into attacker browser
16Real Service ➔ Attacker
Full, persistent, and silent access to victim's complete account
Attacker can read emails, modify security settings, and exfiltrate data without triggering additional MFA

🏢 3.8. Attack on an SME/Company (Targeted)

Attack on an SME/Company (Targeted)

This sophisticated attack targets companies with more serious consequences. The attacker uses social engineering to target specific employees and access internal systems.

👤 Employee (Victim)
🚨 Malicious Proxy (Advanced AiTM)
🏢 Corporate Server (VPN, OWA, SSO)

🟥 Phase 1: Targeted Social Engineering

1Employee ➔ AiTM Proxy
Clicks on spear-phishing link impersonating vendor, colleague, or IT helpdesk
Highly authentic corporate pretext with urgent action required
2AiTM Proxy ➔ Corporate Server
Relays request to corporate authentication endpoint
3Corporate Server ➔ AiTM Proxy
Returns genuine corporate SSO login page (Microsoft Entra / Okta)
4AiTM Proxy ➔ Employee
Displays replicated corporate login page with perfect branding

🟧 Phase 2: Professional Access Theft

5Employee ➔ AiTM Proxy
Enters enterprise Active Directory / SSO domain credentials
6AiTM Proxy ➔ AiTM Proxy
Intercepts corporate enterprise domain credentials
🚨 Stolen Corporate Credentials
7AiTM Proxy ➔ Corporate Server
Injects enterprise credentials into genuine SSO gateway
8Corporate Server ➔ AiTM Proxy
Requests corporate 2FA / push prompt validation

🟨 Phase 3: Enterprise MFA Bypass

9AiTM Proxy ➔ Employee
Displays forwarded MFA prompt to employee
10Employee ➔ AiTM Proxy
Approves push notification or enters authenticator code
11AiTM Proxy ➔ Corporate Server
Injects live MFA token into corporate authentication cluster
🚨 Enterprise MFA Bypass

🟪 Phase 4: Lateral Access & Escalation

12Corporate Server ➔ AiTM Proxy
Issues Kerberos / PRT token / corporate session cookie
13AiTM Proxy ➔ AiTM Proxy
Steals Primary Refresh Token (PRT) and session cookies
🚨 Corporate PRT Token Hijacked
14AiTM Proxy ➔ Employee
Simulates maintenance error or silently loops back to intranet

⬛ Phase 5: Lateral Movement & Exfiltration

15Attacker ➔ Internal Network
Breaches internal VPN / network perimeter with stolen token
16Attacker ➔ Internal Network
Conducts lateral movement and privilege escalation toward domain admins
17Attacker ➔ Cloud Exfiltration
Exfiltrates confidential corporate databases, proprietary files, and emails
Enables ransomware deployment, double extortion, and enterprise-wide breach

🔑 4. The "Passwordless" Era: Advanced Solutions to Counter MFA Bypasses

Faced with emerging threats like MFA Fatigue and AiTM phishing, the challenge is not to abandon multi-factor authentication, but to evolve it towards resilient methods. This section explores robust alternatives that protect against phishing while offering an optimized user experience.

🛡️ 4.1. FIDO2 & Passkeys: Phishing-Resistant Authentication

The FIDO2 standard uses asymmetric cryptography to eliminate vulnerabilities of traditional methods. During registration, your device generates a unique key pair: a public key shared with the service, and a private key stored locally. Authentication relies on cryptographically signing a "challenge" sent by the site.

Why FIDO2 is unbreakable?

Domain binding: The private key works only with the legitimate site, making technical phishing impossible. No shared secret: There's nothing to intercept (no SMS code, no password). Only a cryptographic exchange takes place.

Passkeys: Democratization of FIDO2

Private keys backed up in the cloud (Google, Apple, Microsoft) and synced across your devices. +20% adoption in 2025 according to Microsoft. Easier to use with 20% higher success rate for logins (FIDO Alliance).

🗝️ 4.2. Physical Security Keys: Ultimate Protection

Hardware devices (USB, NFC) storing your FIDO2 keys, offering maximum protection against malware and data exfiltration.

✅ Advantages

Maximum security: Immune to malware targeting software solutions. Multiple protocols: Supports U2F, HOTP, TOTP and OpenPGP. Professional adoption: 50% in enterprises vs 10% among individuals.

⚠️ Disadvantages

Cost: €20 to €70 per unit. Loss risk: Requires a backup key configured. Logistics: Physical device management.

🎯 For whom?

Cybersecurity professionals, critical administrative accounts, high-risk individuals (journalists, activists).

🧠 4.3. AI and Behavioral Biometrics: Proactive Detection

Contextual analysis systems integrated into identity platforms (Microsoft Entra ID, Okta, Google) to detect abnormal behaviors.

🔍 How it works?

Contextual analysis: Device, location, network, time. Behavioral biometrics: Typing rhythm, browsing patterns. Accuracy: 95% anomaly detection (Okta 2025).

🚀 Advantages

Transparency: Enhanced security without user friction. Proactive detection: Blocks suspicious logins before compromise. Adoption: 25% of SMEs in 2025 (Gartner).

⚠️ Limits

Cost: €1,000 to €10,000/year (enterprise solutions). Privacy: Extensive collection of behavioral data. False positives: 5 to 10% risk of legitimate blocking.

⚠️ Privacy & Transparency

These systems analyze behavioral patterns; check your provider's privacy policy to understand what data is collected and how it's used.

🎛️ 4.4. Adaptive Authentication: Contextual Security

Dynamic approach adjusting authentication requirements based on the risk level of each attempt.

⚙️ Operation

Real-time assessment: Risk score based on 10+ factors. Adaptive response: Additional factor, blocking or direct access. Transparency: Smooth experience for legitimate logins.

📋 Implementations

Google Advanced Protection Program, Microsoft Conditional Access, IAM solutions (Okta, Ping Identity).

⚖️ Advantages & Limits

+ Balances security/experience
+ Protection against abnormal travel
- Bypassable by context imitation
- Dependent on data quality

💡 4.5. Best Practices: Strengthening Traditional MFA

Immediate measures to secure your access while awaiting full adoption of passwordless solutions.

📱 Authenticator Apps (TOTP)

Prefer Google Authenticator or Authy over SMS. Eliminates 95% of SIM-swap risks (DeepStrike).

🛡️ Disable Automatic Approvals

Require manual code entry. Neutralizes 80% of MFA bombing attacks (Proofpoint).

🎓 User Training

Raise awareness about suspicious notifications. According to Verizon DBIR 2025, training remains a major pillar of risk reduction.

🏢 Conditional Access (Enterprise)

Restrict access to approved devices/locations. Blocks 90% of suspicious attempts.

📊 4.6. Detailed Comparison Table of MFA Solutions in 2025

SolutionBombing ResistanceAiTM ResistanceSIM-Swap ResistanceEase of UseApproximate CostAdoption 2025For whom?
SMSLowLowLowVery EasyLowDecliningBeginners (avoid)
Authenticator App (TOTP)Medium (manual entry)MediumHigh (vs SMS)EasyLow~80%Everyone (transition)
FIDO2 Physical KeyHigh (no push)High (phishing-resistant)High (no SMS)Medium€20-70~20% (FIDO Alliance)Experts, Pros
PasskeysHigh (biometrics/PIN)High (FIDO2-based)High (no SMS)Very EasyLow (OS integrated)+20% (Microsoft)Everyone
Behavioral AIHigh (anomaly detection)Medium (complement)High (contextual)Transparent€1k-10k/year~25% SMEs (Gartner)Enterprises
MFA Best PracticesMedium (disable push)Low (vulnerable to proxies)Medium (TOTP > SMS)High (immediate)Free to low cost~80%All audiences
Open-Source Authenticator (e.g., Aegis) High (manual entry) Medium (vulnerable to proxies) High (vs SMS) Easy Free ~15% (tech-savvy niche) Tech users, concerned about auditability

🚀 5. Your Pragmatic Action Plan for 2025

🎯 5.1. Prioritization by account/user type

Individuals
  • Top priority: Passkeys for primary email.
  • Authenticator apps for banking and critical accounts.
  • Awareness of unsolicited notifications.
Professionnels/Freelancers
  • FIDO2 physical keys for administrative access and critical cloud services.
  • Authenticator apps as secondary solution.
  • Configure "manual denial" for MFA notifications.
Large Enterprises
  • Phased deployment of physical keys for at-risk teams.
  • Implementation of adaptive authentication (Conditional Access).
  • Ongoing employee training on new threats.
  • Regular audit of MFA configurations.

📅 5.2. Progressive migration guide

PeriodSubjectAction
Week 1SecureSecure primary email account with a Passkey.
Week 2SMS MFAReplace SMS MFA with an authenticator app on banking accounts.
Week 3DisableDisable "automatic push approvals" on all authenticator apps.
Week 4+PasskeysExtend use of Passkeys or physical keys to other important services (GitHub, PayPal, etc.).
MonthlyReviewAccount review and verification of recovery methods.

✅ 5.3. Immediate Action Checklist

🛑 DO NOT DISABLE MFA!

It remains essential against 99% of automated attacks

🔐 Top Priority: Protect Your Primary Email Account

Replace MFA with a Passkey (Gmail, Outlook, Apple)

⚙️ Optimize Your Authenticator Apps

Disable the "Approve" option → Force manual entry of 6-digit code

📱 Ban SMS as Second Factor

Switch to authenticator apps (Google Authenticator, Authy)

👀 Vigilance: An Unsolicited Notification = Red Alert

Signals someone has your password → Change it immediately

🔄 Switch to Passkeys Gradually

Enable them on each important service (Amazon, GitHub, PayPal)

🛡️ For critical accounts:

Consider purchasing a FIDO2 physical security key.

🏢 6. How businesses can protect their teams

Mandatory MFA Policy

Make MFA (preferably TOTP or FIDO2) mandatory for all administrative access and sensitive systems.

Ongoing Training

Regularly educate employees about new attack techniques (MFA Fatigue, AiTM phishing) through cybersecurity briefings.

Clear Security Policies

Document MFA configuration procedures, backup key management, and response to alerts.

Centralized Authentication Solutions

Use IAM (Identity and Access Management) solutions like Azure AD, Okta or Google Workspace to manage and monitor authentication at scale.

Adaptive Authentication

Implement conditional policies (Conditional Access) to limit logins based on context (device, location).

Regular Security Audit

Periodically check MFA configurations of critical accounts and train teams on best practices.

⚠️ 7. Common mistakes to avoid

Never approve an unsolicited MFA notification

This is the main entry point for MFA Fatigue attacks.

Avoid SMS codes for critical accounts

SMS is inherently vulnerable to SIM swaps.

Don't use the same device for all factors

If the device is compromised, all security layers fall.

Ignore platform security alerts

Suspicious login notifications should be taken seriously and investigated immediately.

Don't have a secondary recovery method

Risk of account lockout if primary factor access is lost (lost phone/key).

Don't update devices and applications

Updates often contain crucial security patches.

💎 8. Conclusion

MFA is evolving

MFA is not dead, it's evolving. The time when "any MFA was enough" is over. Faced with adversaries using sophisticated tools, you need to choose the right MFA.

The future is in resistant standards

Traditional solutions (SMS, simple push notifications) show their limits against psychological harassment (MFA bombing) and technical interception (AiTM). The future is in phishing-resistant standards like FIDO2 and Passkeys, offering superior security without compromising simplicity.

Act pragmatically

The goal is not to panic but to act pragmatically: don't throw away your authenticator, but strengthen your protection where needed, starting with your email. Understanding these limits gives you the means to stay safe. By adopting the right solutions, you no longer suffer from cybersecurity, you stay one step ahead.

📖 9. Glossary

AiTM (Adversary-in-the-Middle)
Attack technique where the attacker positions themselves between the user and the service to intercept and relay authentication information in real time.
FIDO2
Open authentication standard developed by the FIDO Alliance, enabling strong, phishing-resistant authentication based on public key cryptography.
CTAP (Client to Authenticator Protocol)
Protocol used by FIDO2 for communication between the client (browser/device) and the authenticator (security key).
MFA Bombing
Attack technique consisting of bombarding a user with authentication notifications until they approve out of fatigue or error.
Passkeys
Consumer-friendly form of FIDO2, enabling passwordless authentication synced in the cloud across all your devices.
Phishing
Deception technique aimed at stealing personal information by mimicking the appearance of a legitimate site or service.
SIM-Swap
Attack consisting of fraudulently transferring a phone number to a new SIM card controlled by the attacker to intercept SMS codes.
TOTP (Time-based One-Time Password)
Algorithm that generates a temporary unique code based on current time, used by authentication apps like Google Authenticator.
WebAuthn
Standardized web API that allows websites to use FIDO2 authentication via the browser.

📚 10. Verified Sources

Organization Type Data Year
What is an MFA Fatigue Attack? Security Report MFA Fatigue attacks 2024
Defend your users from MFA fatigue attacks Usage Study 74% of consumers know about passkeys and 69% of them have activated them FIDO2 keys 2025
MFA Fatigue Attacks: Ultimate Prevention Guide Usage Study 74% of consumers know about passkeys and 69% of them have activated them FIDO2 keys 2025
How MFA Fatigue Attacks Work & 6 Ways to Defend Against Them How MFA Fatigue Attacks Defend Against Them 2024
Security Intelligence Blog Analysis SIM-Swap fraud 2024

🔗 11. SafeITExperts Recommended Reading

Reading Description
2025 Security Guide: Proactive Protection for Linux, Windows, and macOS Protection Linux, macOS and Windows
Smartphone Security 2025: Comprehensive Technical Guide Smartphone, Security
Secure Passwords 2025: 10 Unbreakable ANSSI Secrets (Password, Secure, IT computer)
Bank Card Security Computer under Linux, Windows, ChromeOS, macOS stolen: security guide

👥 Comments

Comment on this article