Why does MFA prompt bombing still work when users know not to approve unknown prompts?

Why user knowledge alone does not stop MFA prompt bombing

prompt bombing succeeds because it targets human attention under pressure, not just awareness. Even informed users can be worn down by repeated approval requests, especially when the attacker already has a password and keeps the login attempts going until the user makes a mistake, gives up, or approves to make the noise stop.

That is why MFA Guide treats fatigue, push fatigue, and phishing-resistant methods as control issues, not training issues. A user can know the right answer and still be placed into a bad decision environment where the attack is designed to exploit repetition, urgency, and distraction.

What makes the attack effective in practice

The attacker usually starts with valid primary credentials, then uses repeated push requests to create a stream of interruptions. The control failure is not that the user lacks intent, but that the approval workflow gives the attacker too many chances to convert pressure into a single mistaken tap. If the only barrier is a user noticing something odd, the attacker can simply keep going.

That is why phishing-resistant authentication matters. NIST SP 800-63 Digital Identity Guidelines is directly relevant here because it distinguishes stronger authenticators from weaker ones and supports a move away from approval flows that can be socially engineered. Passwordless and Passkeys Guide shows why passkeys and FIDO2 reduce this class of abuse by removing the simple approve-or-deny pattern that attackers repeatedly weaponise.

In other words, prompt bombing works when the process assumes a single informed decision is enough. Once the attacker can keep re-presenting the same decision, the system itself becomes part of the weakness.

How to think about the control problem, not just the user problem

Prompt bombing is best understood as a control-design failure that exposes an account to repeated human decision abuse. If a user can be asked the same question dozens of times, the system has created an opportunity for fatigue, confusion, and reflexive action. The practical fix is to reduce the number of times a human must make a yes-or-no choice under stress, and to make the remaining choice meaningfully harder for an attacker to exploit.

Workforce Identity Security Guide is useful here because it ties phishing-resistant MFA, passkeys, account recovery, and step-up controls together rather than treating MFA as a standalone checkbox. Microsoft Midnight Blizzard breach and Uber breach 2022 both illustrate the same pattern: once an attacker can combine valid credentials with a weak or overloaded second factor, the issue becomes access governance, not user education alone.

The practical lesson is that the best control is one the attacker cannot easily repeat until the user slips.

Risk and Threat Considerations

Prompt bombing is risky because it turns an authentication control into a denial-of-attention problem. The attacker benefits from persistence: repeated prompts can condition the user to approve, especially if the account is valuable, the requests arrive at an inconvenient time, or the user believes the prompts will stop only after approval.

Failure mechanism: the attacker already has the password or another valid entry point, then repeatedly triggers MFA prompts until fatigue, confusion, or annoyance produces an approval or a missed denial.

Impact: the attacker gains access to the account without defeating the user’s knowledge of policy, which can lead to session abuse, email takeover, lateral movement, or further privilege escalation depending on what the account can reach.

Practitioner Guidance

What to verify: Confirm whether your MFA flow allows unlimited repeated prompts, whether users can report and suppress them, and whether the second factor can be approved without an additional possession check or number matching step.

Decision rule: If a method can be defeated by repeated user prompts, treat it as a weaker control for high-value accounts and prioritise phishing-resistant sign-in or stronger step-up authentication for those populations.

What good looks like: Legitimate sign-ins are rare enough that a user can distinguish them from abuse, repeated requests are rate-limited or blocked, and the user experience does not reward an attacker for persistence.

Practitioner takeaway: Educating users is necessary, but the durable fix is to make repetition unprofitable for the attacker and unactionable for the user.

Related resources from NHI Mgmt Group

• Why does prompt bombing work against MFA users?
• What should security and IAM leaders do when users know about MFA but still use passwords?
• Why do ephemeral credentials still leave risk in machine access models?
• How should security teams reduce MFA prompt bombing risk?