Prompt without a sign-in
An approval request appears when the employee is not actively accessing the named account or application.
MFA Fatigue Attacks Awareness
How to Recognize and Report MFA Fatigue Attacks
An MFA fatigue attack sends repeated authentication prompts in the hope that a user will approve one to stop the disruption or because they assume it is legitimate.
Use this guide to turn the threat into a clear employee decision, a safe practice scenario, and a reporting step your organization can support.
Plain-English definition • Warning signs • Safe simulation ideas • Reporting practice
01Understand the threat
MFA Fatigue Attacks: a practical definition
An MFA fatigue attack sends repeated authentication prompts in the hope that a user will approve one to stop the disruption or because they assume it is legitimate.
The prompt may come from a real authentication system. The suspicious condition is that the employee did not initiate the sign-in or does not recognize the request.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a mfa fatigue attacks message
No single clue proves that a message is malicious. Teach employees to combine the request, sender, business context, destination, and available verification route before acting.
Repeated interruptions
Multiple prompts arrive over a short period, sometimes followed by a call or message claiming to explain them.
Pressure to approve
A supposed support person asks the user to accept a prompt, share a code, or keep retrying.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Reject the unexplained request and report it through the known security or support channel rather than approving it to make the prompts stop. | Publish the authentic contact, application, or reporting route somewhere employees can reach without using the message. |
| When uncertain | Pause the request and report it through the approved channel with enough context for review. | Explain what the response team needs and how employees will know that their report was received. |
| After an interaction | Stop, contact the responsible team promptly, and describe the action taken without hiding the mistake. | Provide a well-known response route and avoid communications that discourage early reporting. |
Source: NIST: Recognizing, verifying, and reporting phishing
04Practice safely
MFA Fatigue Attacks simulation and discussion ideas
Choose one learning objective per exercise. Use fictional people, organizations, accounts, payments, documents, and events, and test the reporting route before sending to employees.
Static prompt example
Use screenshots or a tabletop to practice the reject-and-report decision without generating live prompts.
Prompt plus phone call
Discuss how an attacker might follow repeated prompts with support impersonation.
Reporting walkthrough
Test whether employees know where to report and which account, time, and device details are useful.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the mfa fatigue attacks clue being practiced, the expected action, the authorized audience, and the owner of follow-up.
- 2
Confirm the real process
Test the independent verification route, message-reporting option, response handoff, and employee support path from a representative account.
- 3
Pilot the scenario
Check delivery, links, landing content, accessibility, event records, automated inspection, stop conditions, and the explanation employees will receive.
- 4
Review in context
Reconcile intended recipients, successful deliveries, unique employee events, verified reports, response handling, and completed follow-up before drawing conclusions.
Source: NIST SP 800-50 Rev. 1: Building a Cybersecurity and Privacy Learning Program
06Useful measurement
Evaluate recognition, reporting, and the surrounding process
Record actual counts and denominators for delivery, unique recipient events, reports, and follow-up. Separate automated email inspection and repeat events where the available evidence supports doing so.
A mfa fatigue attacks exercise samples one scenario under one set of conditions. It does not establish an employee's intent, overall security awareness, or likelihood of responding the same way to a real attack.
Use findings to improve the real workflow: clearer verification instructions, easier reporting, faster response handling, better role-specific training, or a business control that reduces reliance on email alone.
Common questions
Common questions about Phishmake's features, onboarding, and support, answered to help you get started with confidence.
What should an employee do with an unexpected MFA prompt?
They should reject it and use the known security or support route to report the event, following the organization's documented instructions.
Why not approve just to stop the prompts?
Approval may authorize a sign-in the employee did not initiate. The safe response is to reject and report rather than interact until the request is understood.
Can mfa fatigue attacks be used in a phishing simulation?
It can be practiced when the scenario is authorized, proportionate, and tied to a real reporting or verification process. Do not create real authentication prompts or intentionally disrupt an employee's account or device. Use fictional examples or a controlled non-production environment.
How should mfa fatigue attacks simulation results be measured?
Review successful delivery, unique employee events, reports, response handling, and completed follow-up. Include scenario difficulty and operating context, and do not treat a click or report as a complete measure of employee risk.
Sources & further reading
Published by Phishmake · Updated
Keep building your program
All resourcesPut it into practice
Turn mfa fatigue attacks awareness into a repeatable response.
Use Phishmake to run controlled employee simulations, review campaign activity, assign relevant training, and keep follow-up records in one workflow.