A push attack is an authentication abuse technique that overwhelms a user with repeated login prompts until one is accepted. The attacker usually already has valid credentials and is trying to convert them into access through fatigue, distraction, or habit. It is also called push fatigue or MFA prompt bombing.
Expanded Definition
Push attack is a social and technical abuse pattern that targets the approval step of multifactor authentication, usually by flooding a legitimate user with repeated prompts until one is accepted. In NHI and IAM operations, it matters because the attacker often starts with valid credentials, then relies on fatigue, distraction, or a mistaken assumption that the prompts are routine. Guidance varies across vendors on whether push attack is treated as a distinct attack class or as a form of MFA fatigue, but the operational risk is the same: the approval channel becomes the weakest link rather than the secret itself.
This pattern is especially relevant where the login workflow has low friction, broad notification permissions, or weak conditional access checks. NIST SP 800-53 Rev. 5 frames the control expectation around authenticating and verifying access attempts, while NIST SP 800-63 helps explain why authenticator binding and stronger phishing-resistant methods reduce this exposure. The most common misapplication is treating push approval as equivalent to user intent, which occurs when repeated prompts are accepted without verifying the requesting context.
Examples and Use Cases
Implementing defenses against push attack rigorously often introduces user friction, requiring organisations to weigh login convenience against a lower probability of accidental approval.
- A help desk or remote worker receives a burst of mobile prompts after a credential stuffing attempt, then approves one out of habit, enabling account takeover.
- An attacker uses stolen enterprise credentials to target an admin who is distracted during a meeting, relying on prompt fatigue rather than password cracking.
- Security teams correlate prompt spikes with identity telemetry and threat intel, then review suspicious sessions through the MITRE ATT&CK Enterprise Matrix for related credential-access behavior.
- Governance teams compare local incident patterns with the 52 NHI Breaches Analysis and Top 10 NHI Issues to understand how weak approval workflows are abused across identity estates.
- Program owners replace legacy push-only MFA with phishing-resistant methods after repeated prompt abuse is observed in VPN, SSO, or cloud console sign-ins, using CISA guidance to shape escalation and response.
Industry usage is still evolving, but the practical meaning is consistent: an attacker is trying to turn an authenticated challenge into a mistaken human approval. The strongest implementations reduce prompt volume, add number matching or context binding, and reserve push approval for low-risk cases only.
Why It Matters in NHI Security
Push attack is not just a human-factor annoyance. In NHI security, the same approval weaknesses often sit adjacent to privileged service consoles, CI/CD tooling, and cloud admin portals where stolen human access can rapidly expose secrets, tokens, and API keys. NHIMG research shows that 79% of organisations have experienced secrets leaks and 77% of those incidents caused tangible damage, which makes authentication abuse an upstream risk rather than a narrow login issue. That matters because a single approved prompt can unlock paths to NHI inventory, vault access, deployment pipelines, or key rotation workflows.
The issue becomes more severe when organisations assume MFA alone equals resilience. The Ultimate Guide to NHIs explains why weak visibility, excessive privilege, and poor rotation create compound exposure, while the Ultimate Guide to NHIs — Key Challenges and Risks shows how those weaknesses propagate across the identity plane. Push attacks also intersect with broader adversary behavior described in the Anthropic report, where identity compromise supports later-stage abuse. Organisations typically encounter the real cost only after a prompt is accepted and a session has already been used to access systems, at which point push attack becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST SP 800-63, NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 | Push attacks often enable downstream secret misuse after account takeover. |
| OWASP Agentic AI Top 10 | A-03 | Agent and operator approvals can be abused when prompt fatigue weakens verification. |
| NIST SP 800-63 | Defines authenticator assurance expectations that favor phishing-resistant methods over push approval. | |
| NIST CSF 2.0 | PR.AA-1 | Identity proofing and authentication controls support resistance to prompt abuse. |
| NIST Zero Trust (SP 800-207) | Zero Trust requires continuous verification beyond a single accepted prompt. |
Harden authentication paths and detect repeated MFA prompts before compromised access reaches NHI assets.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 27, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
