Multi-Factor Authentication Fatigue Attack: Prevention Guide


You enable multi-factor authentication on your accounts because you want better security. But attackers have found a way to turn this protection against you through persistence and psychology.
A multi-factor authentication fatigue attack is a social engineering cyberattack where hackers flood you with dozens or even hundreds of authentication requests until you approve one just to stop the notifications.
The technique works because attackers who already have your username and password repeatedly trigger login attempts that send push notifications to your phone or email. After being bombarded with alerts for hours, many people eventually tap "approve" out of frustration or confusion.
This attack method has compromised high-profile organizations and continues to grow as a threat to identity security. Understanding how these attacks work and what steps you can take to defend against them helps protect both your personal accounts and your organization's cybersecurity.
Key Takeaways:
MFA fatigue attacks overwhelm you with repeated authentication prompts until you approve one to stop the notifications.
You can defend against these attacks by using phishing-resistant authentication methods and monitoring for unusual login patterns.
Organizations must combine technical controls with user training to reduce the risk of unauthorized access through prompt bombing.
How Push Bombing Exploits MFA Approvals

Push bombing turns multi-factor authentication into a weapon by overwhelming users with approval requests until frustration or confusion leads to a single mistaken click. Attackers combine stolen credentials with relentless notification floods to bypass what should be a strong security layer.
The Meaning of MFA Fatigue, MFA Bombing, and Prompt Bombing
MFA fatigue attacks are also called MFA bombing, prompt bombing, push bombing, or MFA spamming. All these terms describe the same technique where attackers flood your device with multi-factor authentication push notifications.
The attack exploits push-based MFA systems that send approval requests to your phone or other registered devices. When you receive dozens or even hundreds of authentication requests in a short time, the constant buzzing and alerts create fatigue.
MFA prompt bombing relies on a simple premise. If you see enough prompts, you might eventually hit "Approve" just to make the notifications stop. This social engineering technique doesn't require breaking encryption or finding software vulnerabilities.
How Repeated Requests Exploit Push-Based Authentication
Push-based multi-factor authentication sends approval requests to your device after you enter your password. You're supposed to deny requests you didn't initiate, but this relies on you paying attention to every single notification.
Attackers flood push approvals to pressure you into clicking through. The requests might arrive every few seconds for minutes or even hours. You could be sleeping, in a meeting, or simply distracted when the barrage starts.
The technique works because it weaponizes your trust in the authentication system. You're conditioned to expect these prompts as part of normal logins. When combined with decision fatigue and the desire to stop annoying interruptions, that trust becomes a liability.
Unlike technical exploits, MFA fatigue succeeds through persistence, not broken cryptography or malware. Attackers only need patience and a set of stolen credentials to launch the attack.
The Typical Attack Chain From Stolen Credentials to Approval
The attack follows a predictable sequence. First, attackers obtain your username and password through phishing, credential stuffing, or data breaches. They might also use infostealer malware that harvests saved passwords from your browser.
Once they have your credentials, the bad actor enters them into a service protected by push-based MFA. This triggers an authentication request to your phone. When you deny it, they simply try again.
The attacker triggers the login process repeatedly, either manually or through automated scripts. Your phone buzzes constantly with repeated multi-factor authentication requests. You might approve one request to silence your device or because you assume it's a system glitch.
After you approve just one prompt, the attacker gains access to your account. They can then move laterally through systems or steal sensitive data before you realize what happened.
Why Some Password Reset Flows Can Trigger Prompts Without a Password
Some authentication systems allow attackers to trigger MFA push notifications even without entering the correct password first. Certain password reset flows or account recovery processes, generate authentication requests before fully verifying the initial credentials.
This design flaw makes MFA bombing easier to execute. Attackers can flood you with prompts without needing to complete credential theft first. They might only need your username or email address to start the notification barrage.
The weakness appears in systems where the MFA prompt is sent as part of verifying your identity during password recovery. Instead of requiring the current password, these flows assume the authentication factors will provide sufficient verification. This creates an opening for social engineering attacks that bypass the need for stolen credentials entirely.
Warning Signs of Fraudulent Authentication Requests

Attackers rely on you missing key red flags during MFA fatigue attacks. Learning to spot suspicious login attempts helps you protect your account before damage occurs.
Unexpected Prompts When You Are Not Signing In
You receive an MFA push notification on your phone, but you're not trying to log in anywhere. This is the clearest sign that someone else has your password and is attempting to access your account.
Legitimate authentication requests only appear when you actively try to sign in. If MFA prompts arrive while you're sleeping, watching TV, or doing anything other than logging into a system, deny them immediately.
These unexpected authentication requests mean an attacker already has your username and password. They're just waiting for you to approve their access. Never approve an MFA prompt you didn't trigger yourself, even if it only happens once.
Rapid Notification Floods and Spaced-Out Requests
MFA bombing attacks send dozens of authentication requests in quick succession. Your phone buzzes repeatedly with approval requests, overwhelming you with notifications.
Some attackers use a different approach. They send spaced-out requests over several hours or days, hoping you'll eventually click "approve" by mistake or just to stop the interruptions.
Both patterns indicate social engineering designed to wear down your resistance. Requests arriving during late evening or early morning hours (11 PM to 4 AM) are especially suspicious. Attackers choose these times because you're more likely to approve requests without thinking clearly.
Fake IT Support Calls Asking You to Approve Access
A phone call from someone claiming to be IT support arrives right after you deny several MFA prompts. The caller asks you to approve the next authentication request so they can "fix your account" or "complete maintenance."
This is vishing, a type of social engineering that combines voice calls with technical attacks. Real IT staff never ask you to approve MFA prompts for them.
Attackers use this tactic after MFA fatigue attacks fail. They hope the phone call adds legitimacy and pressures you into granting access. Hang up immediately and contact your IT department through official channels you look up yourself.
What to Do During an Active Attack

When you receive unexpected MFA push notifications, you need to act quickly to protect your account and prevent an attacker from gaining access. Your response must be immediate and methodical to stop the threat and minimize damage.
Deny Unexpected Requests and Report Through a Trusted Channel
You should deny all fraudulent push notifications you receive when you are not trying to log in. Do not approve any authentication request that you did not initiate.
After denying the requests, report the incident through your organization's official security channels. Contact your IT security team using a phone number or email address you already know is legitimate. Do not click links in emails or messages claiming to be from your security team during an attack.
Monitor your account activity by checking for suspicious login attempts or account changes.
Set up notifications if your system allows it. Keep denying requests even if the attacker sends multiple notifications in a row.
If You Approved a Prompt: Revoke Sessions and Contain Access
If you accidentally approved an MFA request during a fatigue attack, you need to immediately revoke all active sessions on your account. Log out of all devices and locations where you are currently signed in.
Change your account permissions to limit what an attacker can access. Disable or remove any API tokens, application passwords, or connected third-party services that could give the attacker continued access. Check if your account has the ability to view currently active sessions and terminate them individually.
Contact your security team right away to report the account takeover. They can implement additional controls to block the attacker's access from their end. Time matters because the attacker will move quickly to exploit your compromised account.
Reset Compromised Credentials and Review Registered MFA Methods
Reset your password immediately because the attacker already has your current credentials. The fact that they triggered MFA push notifications means they know your username and password.
Choose a strong, unique password that you have never used before on any account. Do not reuse passwords across different services or accounts.
Review all registered MFA methods on your account. Remove any devices, phone numbers, or authentication apps you do not recognize. An attacker may have added their own MFA method to maintain access. Check backup codes and regenerate them if your system allows it.
Enable additional security features like security keys or biometric authentication if available. These methods provide stronger protection against credential compromise than standard push notifications.
Preserve Authentication Logs and Investigate Affected Accounts
Save copies of your authentication logs before they expire or get overwritten. These logs contain critical information about when login attempts occurred, what IP addresses were used, and which devices were involved. Your security team will need this data to investigate the mfa fatigue attack.
Look for patterns in the logs that show when the attacker first gained access to your credentials. Check if any successful logins occurred from unfamiliar locations or devices. Note the exact times of all suspicious authentication requests.
Review what the attacker might have accessed during the time they had control. Check your email sent folder, file access history, and any sensitive data you store in connected systems. Look for signs that the attacker moved laterally to other accounts or systems in your organization.
Document everything you observe about the attack. Record the number of push notifications you received, their timing, and any unusual messages or requests. This information helps your security team understand the attacker's methods and prevent future incidents.
Configuration Changes That Reduce Prompt Abuse

Simple adjustments to your MFA settings can block most prompt bombing attempts without adding extra software or hardware. These configuration changes limit how many requests reach users, add verification steps that require attacker interaction, and apply context-aware policies that flag suspicious login patterns.
Replace Simple Approvals With Number Matching and Sign-In Context
Your first priority is eliminating blind approval prompts. Number matching reduces approval abuse immediately by displaying a two-digit code on the login screen that users must select or enter in their authentication app. This forces attackers to communicate the code to victims through social engineering, adding friction that stops most automated attacks.
Microsoft Authenticator now includes number matching as a default option for new deployments. You can enable it for existing tenants through the Microsoft Entra admin center under Authentication Methods > Microsoft Authenticator. Okta offers similar functionality through Okta Verify with number challenge.
Add contextual information to every prompt. Your users should see the IP address, device type, browser, location, and timestamp for each request. This context helps them spot suspicious login attempts from unfamiliar locations. When you combine number matching with rich context, users can't mindlessly tap approve because they must actively engage with both the login screen and their phone.
Apply Rate Limiting and Authentication Throttling
Limiting authentication attempts to three to five prompts within a specific timeframe prevents attackers from overwhelming users with dozens of notifications. Most enterprise MFA platforms include rate limiting as a standard configuration option that you can adjust based on your risk tolerance.
Set your throttling rules to account for legitimate retry scenarios. Users occasionally mistype passwords or dismiss prompts accidentally. A limit of three attempts per 15-minute window balances security with usability. After hitting the limit, lock the account temporarily or require a password reset through a verified channel.
Configure alerts when users hit rate limits repeatedly. This pattern often indicates credential compromise even if no approval occurred. Your security team should investigate these events within the hour and contact affected users to verify their passwords haven't been stolen.
Use Conditional Access and Risk-Based Authentication
Conditional access policies let you require stronger MFA methods when risk signals suggest an attack. You can configure Microsoft 365 conditional access to demand phishing-resistant FIDO2 authentication when users log in from new devices, unfamiliar locations, or countries where your organization doesn't operate.
Risk-based authentication evaluates multiple factors simultaneously. Your system can analyze device fingerprinting data, network reputation, time of day, and user behavior patterns to calculate a risk score. When users see prompts less frequently, they pay more attention to each one.
Set up adaptive authentication rules that skip MFA entirely for low-risk scenarios. If a user logs in from their registered laptop at headquarters during business hours, no prompt is needed. But if that same user attempts access from a new device in another country at 3 AM, require number matching plus manager approval. This approach reduces both MFA fatigue and prompt bombing success rates.
Review Push, Recovery, and Fallback Settings in Microsoft
Authenticator and Okta
Disable legacy authentication methods that bypass modern MFA security. Both Microsoft Authenticator and Okta support multiple verification options, but not all provide equal protection. Remove simple push notifications as the primary method and replace them with number matching or biometric verification.
Check your recovery options because attackers often exploit these as backdoor entry points.
SMS and email recovery codes are vulnerable to interception. Configure your systems to require in-person identity verification or manager approval for MFA resets on sensitive accounts. In Okta, navigate to Security > Authenticators and review the enrollment requirements for each method.
Audit your fallback authentication settings monthly. Some organizations accidentally leave unrestricted fallback methods enabled, letting users switch to weaker options when they claim their primary authenticator isn't working. Require help desk approval before allowing fallback to SMS or voice calls.
Why Phishing-Resistant Authentication Is the Stronger Defense

Phishing-resistant MFA uses cryptographic keys that bind to specific websites, making it impossible for attackers to steal or replay credentials even if users interact with fake sites.
Unlike traditional MFA methods that rely on codes or push notifications, phishing-resistant authentication eliminates the core vulnerabilities that enable MFA bypass attacks.
How FIDO2 and WebAuthn Bind Authentication to the Legitimate Site
FIDO2 authentication creates cryptographic keys that are permanently tied to the exact domain of your legitimate website. When you try to sign in, WebAuthn verifies that the domain matches before allowing authentication to proceed.
This binding is what stops phishing attacks. If an attacker creates a fake login page at a different domain, the cryptographic key simply won't work there. The authentication request will fail automatically.
The process happens without any user decision-making. You don't need to check URLs or verify certificates. WebAuthn handles the verification at the protocol level, blocking adversary-in-the-middle (AiTM) phishing attempts before they can capture any credentials.
Traditional MFA methods like SMS codes or authenticator app codes work on any site where you enter them. FIDO2 credentials only work on the specific domain where they were registered.
Choosing Passkeys and FIDO2 Security Keys
Passkeys are FIDO2 credentials stored on your devices or in cloud-synced password managers. They work across your phone, laptop, and tablet without requiring separate hardware.
Hardware security keys are physical devices you plug into USB ports or tap with NFC. They store FIDO2 credentials in tamper-resistant chips that never expose the private key.
Your choice depends on your security needs:
Method | Best For | Trade-offs |
Passkeys | Most users and remote workers | Requires a device with biometric or PIN |
Hardware keys | High-value accounts and compliance | Need to manage physical distribution |
Platform authenticators | Windows Hello, Touch ID | Tied to specific devices |
Organizations implementing phishing-resistant MFA often deploy both options. You might use passkeys for daily access and hardware security keys for privileged accounts.
Why Number Matching Reduces Risk but Is Not Phishing-Resistant
Number matching requires you to enter a number shown on the login screen into your authenticator app. This stops simple MFA fatigue attacks where attackers just spam approval requests until you accidentally tap yes.
The number matching creates friction that forces you to look at both screens. Attackers can't get in by overwhelming you with notifications anymore.
But number matching doesn't prevent phishing. An attacker using an AiTM proxy can capture the number you see and immediately enter it on the real site. The session token still gets stolen.
It's a useful upgrade from basic push notifications, but it's not cryptographically bound to the legitimate domain. The number works wherever it's entered, unlike FIDO2 credentials that only function on their registered domain.
Protecting Enrollment, Recovery, and Fallback Methods
Your attack surface includes every method users can invoke to gain access. Attackers target weak enrollment and recovery flows to bypass strong primary authentication.
Temporary Access Pass (TAP) provides time-bound credentials for onboarding new users or recovering locked accounts. Set TAP to expire within hours, not days.
Video-based identity verification with liveness detection confirms the person enrolling matches their identity document. This prevents attackers from using stolen credentials during the initial registration process.
Key protections for fallback methods:
Disable SMS and email OTP recovery for privileged accounts.
Require help desk verification before issuing recovery credentials.
Log all fallback authentications for security monitoring.
Block legacy authentication protocols that bypass modern MFA.
You should also migrate service accounts to workload identities or certificate-based authentication. User accounts running automation often have weak MFA or none at all.
Detecting Prompt Abuse With Authentication Telemetry

Detection requires continuous collection of authentication events and correlation of denied prompts with eventual approvals. Your SIEM must ingest sign-in logs, track MFA outcomes, and flag patterns that indicate prompt bombing.
Collect Sign-In Events, Push Outcomes, and Device Context
Your security information and event management platform needs to ingest authentication logs from your identity provider. These logs should include every MFA prompt sent, whether it was approved or denied, the timestamp of each event, and the source IP address.
Azure AD Sign-In Logs capture error codes like 50076 for MFA required and 500133 for incomplete authentication attempts. You should also collect device fingerprinting data, including browser type, operating system, and geolocation. This context helps you distinguish legitimate access from suspicious login attempts.
Microsoft Authenticator logs provide additional telemetry when devices are managed through Intune. You need this granular data to see exactly when push notifications were delivered to the user's device.
Correlate Repeated Denials With a Subsequent Approval
The highest-fidelity indicator of a successful fatigue attack is approval following 3+ prior denials. Your detection logic should track the sequence of MFA prompts per user over a rolling time window.
A user receiving 5+ MFA prompts in 10 minutes represents the push bombing pattern. When one of those prompts is finally approved after multiple denials, you have confirmed compromise. This is the moment when the victim gave in to the fatigue.
Your SIEM query should group authentication events by user identity and correlate denied prompts with any subsequent successful approval from the same source IP. Flag these events as high severity because they indicate identity-based threats that bypassed your MFA controls.
Detect Low-Volume Abuse With Behavioral Analytics
Not all MFA fatigue attacks happen in rapid bursts. Some attackers spread prompts over hours or days to avoid threshold-based detections.
Behavioral analytics can identify users receiving elevated MFA prompt volumes compared to their baseline. If a user typically receives 2-3 prompts per week but suddenly gets 15 in 24 hours, this deviation warrants investigation.
Track unresponded MFA prompts over 30-day windows. Users who routinely ignore unexpected prompts represent a risk even if they never approve one. This pattern suggests ongoing low-and-slow campaigns targeting that account.
Automate Investigation and Containment With Appropriate Safeguards
Your detection workflow should trigger automated response for confirmed fatigue success events. When you detect approval following multiple denials, your SIEM can disable the account and block the attacker IP immediately.
Microsoft Authenticator's Report Suspicious Activity feature lets users mark risky sign-ins, which automatically disables their account. This provides user-initiated containment at the moment of attack.
Build guardrails into your automation to prevent false positives from locking out legitimate users. Users with intermittent mobile connectivity may queue multiple prompts that deliver in rapid succession. MFA enrollment flows also trigger multiple notifications during setup.
Your automated response should notify your security team and the affected user simultaneously through a verified channel like a phone call, not email or chat that the attacker may control.
Training Users and Help Desks Without Shifting the Burden

Training staff to recognize MFA fatigue attacks reduces risk without making security feel like their personal responsibility. Help desk social engineering remains a common bypass method, so both end users and support teams need clear guidance on what to do when attacks happen.
Teach Users to Approve Only Sign-Ins They Initiated
Users should know that every MFA prompt means someone entered their username and password. If they didn't try to log in, they should deny the request immediately.
Tell your team to never approve authentication requests just to stop the notifications. This is exactly what attackers count on during MFA bombing attacks.
Explain that multiple requests in a short time frame signal stolen credentials. When users spot this pattern, they need to deny all requests and report it right away.
Make it clear that receiving even one unexpected MFA prompt means their password is compromised. They should change it immediately after denying the request. This simple rule helps stop attacks before they escalate.
Practice Recognizing Help Desk Impersonation and Vishing
Attackers often call or message users pretending to be IT support after flooding them with MFA requests. They pressure victims to approve a prompt or share sensitive information over the phone.
Train your team to recognize vishing tactics. Real IT staff will never ask them to approve an MFA request they didn't initiate. Your help desk should never contact users asking them to accept authentication prompts.
Create a verification protocol for suspicious calls. Users should hang up and call IT through official channels listed on your company directory. Attackers excel at creating urgency, so remind staff that legitimate IT issues can wait a few minutes for proper verification.
Share examples of common phrases attackers use, like "We're having system issues and need you to approve this request" or "Your account will be locked unless you approve now."
Make Reporting Simple and Reinforce a No-Blame Culture
Give users a single, memorable way to report suspicious MFA requests. An email alias, dedicated Slack channel, or one-click reporting button removes friction from the process.
Respond to every report quickly, even if it's just to acknowledge receipt. Users who get ignored stop reporting threats. Thank people for reporting and share what happened without identifying individuals.
Never punish users who accidentally approve a fraudulent request. Fear of consequences makes people hide mistakes until damage spreads. Frame accidental approvals as learning opportunities and focus on containment.
Build trust by showing how reports led to specific security improvements. When users see their actions matter, they stay engaged with account security practices.
Pair Security Awareness Training With Technical Safeguards
User education works best when backed by technology that limits damage from human error. Deploy MFA methods that are resistant to prompt bombing, like number matching or biometric verification.
Set policies that limit authentication attempts within a time window. This technical control stops the flood of prompts before users face the decision to approve or deny.
Run simulated MFA fatigue attacks to test your training effectiveness. Track who reports the fake attempts versus who approves them. Use this data to identify who needs additional security awareness training, not to punish anyone.
Include help desk staff in all training programs. They need to recognize when callers are trying to manipulate them into resetting MFA or transferring authentication factors. Your support team represents a high-value target for social engineering attacks.
Business Risks After an Unauthorized Approval
When an attacker successfully bypasses MFA through fatigue tactics, your organization faces immediate security consequences. Compromised employee accounts often lead to data breaches and enable attackers to move through your systems undetected.
Account Takeover and Business Email Compromise
Once attackers gain access to your employee's account, they can impersonate that person across your entire organization. They read emails, send messages, and access files as if they were the legitimate user. This makes detection difficult because the activity appears normal.
Business email compromise becomes a serious threat when attackers control email accounts. They can send fraudulent payment requests to vendors or customers using your employee's actual email address. These scams often target finance departments and result in direct financial losses.
Account takeover in Microsoft 365 environments gives attackers access to OneDrive, SharePoint, and Teams. They can download sensitive documents, review confidential communications, and identify valuable targets for future attacks. Your security tools may not flag this activity because the credentials are valid.
Privilege Escalation, Data Theft, and Ransomware
Attackers rarely stop at the initial compromised account. They use credential compromise as a starting point to explore your network and identify accounts with higher privileges. They look for administrators, IT staff, or executives whose access could unlock more valuable systems.
Unauthorized access allows lateral movement within the network and exposure of sensitive company information. Attackers map your infrastructure, locate databases, and exfiltrate customer records or intellectual property. Data breaches from these attacks can expose millions of records.
Ransomware deployment often follows successful MFA fatigue attacks. Once attackers establish persistent access and identify critical systems, they encrypt your files and demand payment. The combination of valid credentials and network access allows them to disable backups and security tools before launching the attack.
Limiting Damage Through Least Privilege and Identity Governance
You can reduce your attack surface by implementing least privilege access controls. Every account should only have the permissions needed for that person's specific job duties. When attackers compromise a low-privilege account, they cannot immediately access sensitive systems or data.
Identity governance helps you monitor who has access to what resources across your organization. You should regularly review and revoke unnecessary permissions, especially for former employees or changed roles. Strong identity security practices include:
Time-limited access grants for temporary projects or elevated permissions.
Automated deprovisioning when employees change roles or leave.
Regular access reviews to identify and remove unused permissions.
Separation of duties to prevent any single account from controlling critical processes.
Your identity governance program should track all privileged accounts and require additional verification for sensitive actions. This limits how far attackers can progress even after gaining initial access through MFA fatigue.
Lessons From Documented Attacks
Real-world breaches show how attackers combine stolen credentials with MFA fatigue attacks to break into secure systems. These incidents reveal patterns you can learn from to protect your organization.
The 2022 Uber Breach and Reported Lapsus$ Links
In September 2022, an attacker compromised Uber's network after obtaining an employee's credentials. The attacker then bombarded the employee with push bombing notifications until the worker approved one request.
Reports linked this attack method to the Lapsus$ group. This group became known for targeting major companies using similar tactics. The Uber breach showed that even tech companies with MFA can fall victim to these attacks.
The attacker gained wide access to Uber's systems. They accessed internal tools, code repositories, and employee information. This breach proved that MFA alone doesn't stop determined attackers who combine credential theft with psychological manipulation.
Scattered Spider and Help Desk Social Engineering
Scattered Spider took MFA fatigue attacks further by adding help desk manipulation. After push bombing failed, attackers would call IT support pretending to be the targeted employee.
They claimed they couldn't access their account due to the constant MFA prompts. Help desk staff, trying to be helpful, sometimes reset MFA settings or approved access. This combination of social engineering tactics proved highly effective.
The group targeted multiple organizations across different industries. They understood that tired, frustrated employees and helpful IT staff created weak points in security systems.
MITRE ATT&CK T1621 and the Defensive Lessons
MITRE documents this attack pattern as T1621 under multi-factor authentication request generation. This classification helps security teams understand and track these threats.
The technique shows attackers already have valid usernames and passwords before starting the attack. Your defense must address both credential protection and MFA implementation. You need monitoring systems that detect unusual patterns of repeated MFA requests.
Number matching and context-aware authentication help stop these attacks. These methods make it harder for attackers to succeed even when they spam your employees with requests.
How Push Bombing Differs From Other MFA Bypass Techniques
Push bombing targets user behavior through notification overload, while other MFA bypass methods exploit technical vulnerabilities or telecommunications infrastructure.
Understanding these distinctions helps you build layered defenses against multiple attack vectors.
Adversary-in-the-Middle Phishing and Session Token Theft
Adversary-in-the-middle (AiTM) phishing intercepts your authentication session in real-time rather than bombarding you with approval requests. When you enter credentials on a fake login page, attackers capture both your password and the session token created after successful MFA completion.
This technique bypasses MFA entirely without requiring your approval. The attacker positions themselves between you and the legitimate service, relaying your credentials while stealing the authenticated session cookie.
Once they obtain your session token, attackers can access your account directly without triggering new MFA prompts. This creates a critical difference from push bombing, which requires you to actively approve a malicious authentication request.
AiTM attacks succeed even against users who carefully review push notifications. Your legitimate MFA approval goes to the real service, but the attacker captures the resulting session and uses it for unauthorized access.
SIM Swapping and SMS Authentication Risks
SIM swapping transfers your phone number to an attacker-controlled device through social engineering at your mobile carrier. This attack targets the telecommunications infrastructure rather than exploiting your response to authentication prompts.
After controlling your phone number, attackers receive SMS codes sent during login attempts. They don't need to overwhelm you with notifications because they intercept the codes directly.
Push bombing relies on you eventually approving a request, while SIM swapping eliminates your role in the authentication process entirely. The attacker completes MFA challenges using codes sent to the compromised phone number.
This technique creates specific risks when you use SMS as a primary or fallback authentication factor. Organizations that restrict SMS authentication reduce vulnerability to SIM swap attacks but remain exposed to push bombing if they rely on standard push notifications.
Why Credential Stuffing Is Usually an Earlier Attack Stage
Credential stuffing tests stolen username and password combinations across multiple services to find valid accounts. This technique provides the initial access that enables push bombing attacks rather than bypassing MFA directly.
Attackers obtain credentials through data breaches, phishing campaigns, or password leaks from other services. These stolen credentials allow them to trigger login attempts that generate MFA prompts on your device.
Push bombing begins where credential stuffing ends. Without valid credentials, attackers
cannot initiate the authentication requests that create push notifications. The bombing attack specifically targets the MFA layer after credential validation succeeds.
You might reuse passwords across services, making credential stuffing effective at finding accounts where attackers can launch follow-up attacks. Strong unique passwords for each service limit credential stuffing success but don't prevent push bombing if attackers obtain credentials through targeted phishing.
Why Strong MFA Still Requires Layered Account Protection
Phishing-resistant MFA methods like FIDO2 tokens and WebAuthn prevent remote attackers from completing authentication even with valid credentials. These methods require cryptographic proof that standard push notifications cannot provide.
Push bombing exploits authentication factors you can approve remotely from any location.
Hardware tokens and biometric authenticators tied to specific devices eliminate this vulnerability entirely.
Multiple defense layers protect against different bypass techniques:
Number matching prevents automated push approvals.
Rate limiting blocks high-volume bombing attempts.
Hardware tokens eliminate remote phishing risks.
Session monitoring detects suspicious token usage.
No single control addresses every MFA bypass method. Organizations that combine detection of volume-based push notification anomalies with phishing-resistant factors for privileged accounts create defense in depth against both push bombing and AiTM attacks.
Your account security depends on understanding which bypass techniques your current MFA implementation prevents and which require additional controls.
Next Steps for Your RIA or Broker-Dealer Firm:
Secure Wealth IT helps Registered Investment Advisors, broker-dealers, and financial advisors stay secure, compliant, and audit-ready. Explore these free tools and resources:
Free Financial Calculators: calculator.securewealthit.com
Compliance Self-Assessment Tool: regulations.securewealthit.com
Resource Library: Browse free RIA and broker-dealer guides.
Watch on YouTube: Secure Wealth IT YouTube channel.
Talk to a Specialist: Schedule a free consultation.
For more information about this topic, visit us at https://www.securewealthit.com




Comments