Push bombing exposes the weakness in legacy MFA controls

At a glance

What this is: This is an analysis of push bombing, also known as MFA fatigue, and the article’s central claim is that repeated approval prompts remain exploitable in legacy push-based MFA.

Why it matters: It matters because identity teams still rely on approval prompts as a second factor, and that assumption breaks when attackers can manipulate users into granting access.

Context

Push bombing is a user-driven MFA bypass technique, not a protocol flaw. The attacker already has credentials and then overwhelms the target with repeated push requests until one approval slips through, which means the control fails at the point where human attention becomes the security boundary.

For IAM programmes, the issue is not authentication in the abstract. It is the governance assumption that a user can reliably act as the final gate under pressure, in the middle of a phishing or social-engineering campaign. Once that assumption is weakened, push-based MFA becomes an approval workflow attackers can game.

The article frames this as a practical weakness in legacy MFA posture rather than a niche tactic. That is consistent with how push bombing behaves in the field: it scales through user fatigue, not technical sophistication.

Key questions

Q: What breaks when push-based MFA is the main control for privileged access?

A: Push-based MFA breaks down when attackers can flood users with prompts or impersonate support staff into approving one. The control still works technically, but the human approval step becomes the weak point. For privileged access, that means attackers can convert authentication into persuasion, which is not a stable assurance model for high-value accounts.

Q: Why do repeated MFA prompts increase breach risk instead of proving stronger security?

A: Repeated prompts increase risk because they create fatigue, normalise approval behaviour, and turn authentication into a pressure test. A system that depends on a user to reject every hostile request can be worn down, especially when the attacker already has valid first-factor credentials and only needs one mistake.

Q: How can security teams tell whether adaptive MFA is working properly?

A: Look for a lower challenge rate on routine sessions, a higher challenge rate on suspicious transactions, and stable or improved conversion. If adaptive MFA is triggering everywhere, it is behaving like blunt MFA. If it rarely triggers on risky actions, the policy is too weak to matter.

Q: Should organisations replace MFA with passwordless authentication?

A: Organisations should not treat this as a simple replacement question. MFA is still useful where passwordless is not yet available, but passwordless raises the security baseline by removing the password as the primary failure point. The right path is to use MFA as a bridge and passwordless as the destination.

Technical breakdown

How push bombing turns approval prompts into an attack path

Push bombing, or MFA fatigue, works by converting a defensive notification into a coercion channel. An attacker who already knows or has stolen the first-factor credentials sends a flood of push requests so the target approves one just to stop the noise. The important weakness is that the control relies on user discernment at the point of decision, so the security boundary is social rather than cryptographic. That makes the method resilient across devices, geographies, and endpoint states. It also means the attack can succeed without malware, token theft, or protocol exploitation. Practical implication: treat repeated push approvals as a control failure, not normal authentication noise.

Practical implication: treat repeated push approvals as a control failure, not normal authentication noise.

Why legacy push MFA remains phishable

Traditional push MFA is built on approval by prompt. The user sees a login notification and confirms it on a second device or in an app, which sounds stronger than passwords but still depends on a human making a fast judgment. That judgment is vulnerable to distraction, sleep deprivation, urgency, and habituation. The article’s key point is that attackers do not need to break the factor if they can shape the user’s response to it. This is why repeated prompting is so effective against large organisations: the control remains interactive, interruptive, and easy to normalise. Practical implication: review whether your second factor can be socially engineered without compromising the device itself.

Practical implication: review whether your second factor can be socially engineered without compromising the device itself.

How cryptographic, prompt-free MFA changes the trust model

The vendor contrasts push-based approval with device-bound cryptographic authentication. In this model, the private key stays on the user’s device and the platform validates the device, the key, and policy conditions before granting access. The distinction matters because the user is no longer asked to approve a request that an attacker can manipulate. Instead, authentication becomes a cryptographic assertion tied to device possession and policy compliance. That removes the human approval step that push bombing exploits. For identity governance, the architectural shift is from asking users to verify intent to verifying cryptographic proof at runtime. Practical implication: favour authentication designs that remove manual approval from the path to access.

Practical implication: favour authentication designs that remove manual approval from the path to access.

Threat narrative

Attacker objective: The attacker wants to turn stolen or guessed credentials into authenticated access by forcing one approval through fatigue or confusion.

1. Entry occurs after the attacker obtains a user’s credentials, then begins the push-bombing campaign against the target account. Repeated authentication prompts are sent in rapid succession until the user approves one request.
2. Credential access is not solved by the first factor because the attacker is no longer trying to defeat the password directly. The attack instead abuses the authentication channel to convert user fatigue into valid access.
3. Impact follows a single mistaken approval, which can hand the attacker full account access without triggering the kind of alarm that a traditional compromise might produce.

Breaches seen in the wild

• Cisco Yanluowang breach 2022: A password synced to a personal Google account plus vishing and MFA fatigue opened Cisco's VPN; the attacker then abused machine accounts.
• Uber breach 2022: A contractor's stolen password and MFA fatigue gave a Lapsus$-linked attacker Uber's internal tools; Uber rotated keys to many services.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Approval-by-prompt is the broken control assumption. Push bombing succeeds because legacy MFA often assumes the user can remain a reliable security gate after repeated interruption. That assumption is fragile even before the attacker applies pressure, and it collapses completely when the request stream is designed to exhaust judgment. The implication is that identity teams should stop treating user approval as a stable trust boundary.

Human fatigue has become an authentication attack surface. This is not simply social engineering in the generic sense. It is a control-specific abuse of MFA workflows that were designed for occasional confirmation, not adversarial persistence. The field should treat repetitive prompting as an identity risk signal, not as a user-experience nuisance, because the control itself is being weaponised.

Cryptographic proof is a stronger governance primitive than repeated confirmation. When authentication is bound to a device and validated by cryptographic possession rather than an approval tap, the attacker loses the mechanism that push bombing depends on. That shifts the security problem away from persuading humans and toward verifying machine-enforced conditions.

Prompt fatigue gap: The article exposes a governance gap where organisations have substituted user responsiveness for authentication assurance. That gap is especially visible in environments that retained push-based MFA after attackers learned to target the approval step rather than the account password. Practitioners should read this as a sign that the control model itself needs revalidation.

Legacy MFA posture is now an assumption test, not a checkbox. If a second factor can be coerced through volume, then the programme has not achieved the assurance it claims. The practical conclusion is that IAM teams must evaluate whether their MFA design resists the attack pattern, not merely whether it is deployed.

What this signals

Push fatigue is a control-design problem, not a training problem. Organisations that keep relying on approval prompts are preserving a workflow attackers can predict and manipulate. The better programme signal is whether authentication still requires a human to act as the last line of defence under repeated pressure.

Identity assurance has to move away from user interruption. The more the control depends on a distracted person saying yes, the more fragile the programme becomes. Teams should expect stronger outcomes from designs that verify device and policy state at issuance time rather than asking users to adjudicate each request.

For practitioners

• Review push-based MFA exposure Identify where approval prompts still act as the decisive factor for privileged and high-risk access, then classify those flows as susceptible to MFA fatigue abuse.
• Reduce reliance on repeated user approval Replace notification-driven approval workflows with authentication methods that do not ask users to confirm each login attempt under pressure.
• Prioritise high-impact accounts first Start with accounts whose compromise would create the largest blast radius, including admins, support staff, and access paths into sensitive systems.
• Train users to report prompt floods Teach employees that dozens of unexpected push requests are an incident signal, and route those reports into identity threat triage.

Key takeaways

• Push bombing works because it targets the approval step in legacy MFA rather than trying to defeat the first factor directly.
• The article links the pattern to real-world enterprise breaches, which shows the technique is operational, not theoretical.
• Prompt-free, cryptographic authentication removes the user decision point that MFA fatigue exploits and therefore changes the control model.

Key terms

• Push Bombing: Push bombing is an MFA bypass technique that overwhelms a user with repeated authentication prompts until one approval is granted. The attack depends on fatigue, distraction, or confusion, not on breaking the underlying cryptography. It is effective because many organisations still treat user approval as a trustworthy security signal.
• MFA Fatigue: MFA fatigue is the behavioural pressure created when repeated login prompts make a person more likely to approve access without checking carefully. It is a control failure in the authentication experience, and it becomes dangerous when the approved session carries broad privilege or long-lived access.
• Approval by Prompt: Approval by prompt is an authentication pattern where a user confirms access by accepting a notification or entering a short response. It provides convenience, but it also makes the user the final security gate, which is why it weakens quickly under social engineering and repeated request abuse.
• Device-bound authentication: Authentication that only works on a specific device or trusted local context. It reduces replay risk because the secret is not useful from elsewhere, which is materially different from centrally stored credentials that can be stolen and reused remotely.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.