Topic · Threats
MFA fatigue attack
An MFA fatigue attack repeatedly triggers approval prompts to pressure a user into accepting an attacker sign-in.
How it works
An attacker who knows a password bombards a push-based second factor with repeated requests.
What can go wrong
Users may mistakenly approve a prompt to stop notifications or because the request looks routine.
What to check or do
Use phishing-resistant MFA or number matching and investigate repeated uninitiated approval prompts.
How to investigate MFA fatigue attack
- Signal to investigate
- A user receives repeated unexpected approval prompts followed by an unusual sign-in.
- Evidence to collect
- Collect authentication-method events, push approvals, source IP/device signals and help-desk reports.
- Common wrong conclusion
- Having MFA enabled does not mean the approved session is legitimate.
How to interpret the evidence
Attackers may bombard users until one prompt is accepted or socially engineer approval. Number-matching and phishing-resistant methods reduce different parts of this risk.
What to change and how to verify it
Revoke affected sessions, verify the account via a trusted channel and replace weak push workflows with stronger methods.
Put this into practice
Run a focused check, then explore protection if your domain needs it.