Slippage attack is a form of social engineering or interface manipulation that exploits timing, confusion or weak confirmation steps to make a user approve an unintended action. It often targets transaction prompts, permissions or authentication flows, where the attacker benefits from rushed review, ambiguous wording or misplaced trust in a legitimate-looking request.
How Slippage Attack Works
A slippage attack does not usually break cryptography or defeat a backend system. It exploits the human decision point, where a user is asked to approve something quickly and may not fully inspect the amount, destination, scope, or permission being granted.
The attacker’s advantage comes from ambiguity and time pressure. If the interface makes a request look routine, legitimate, or technically dense, the user may confirm an action that is materially different from what they intended.
Why Slippage Attacks Succeed
These attacks work best when confirmation steps are weak, language is unclear, or the user cannot easily compare the prompt with the intended action. Small design flaws can create a large trust gap, especially in transaction flows, permission grants, and authentication approval screens.
Slippage is especially effective when the user expects friction to be low. If the interface encourages fast approval, the attacker needs only enough confusion to shift the decision from deliberate review to reflexive acceptance.
Common Slippage Conditions
Slippage attacks often appear in contexts where users approve payments, sign messages, accept session prompts, authorise application access, or confirm recovery and login challenges. They can also exploit wording that hides the real effect of the action behind technical jargon or compressed summaries.
Another common condition is alert fatigue. When users see repeated prompts or similar-looking requests, they are more likely to rely on habit rather than careful verification, which increases the chance of approving the wrong action.
- Transaction prompts that obscure the final recipient or amount
- Permission requests that bundle more access than the user expects
- Authentication flows that reuse familiar-looking prompts to induce haste
- Interface states where the user cannot clearly distinguish one request from another
Security Impact and Defensive Design
The practical danger is not just one mistaken click, but the downstream authority that click can unlock. Once an unintended approval succeeds, the attacker may gain access, move funds, bind a malicious app, or establish a trusted session that is hard to unwind after the fact.
Strong defences focus on making the decision legible before the approval happens. Clear confirmation language, visible context, step-up checks for high-risk actions, and prompts that show the exact consequence of approval all reduce the room for slippage. CISA’s cyber threat advisories are useful for understanding how social engineering and abuse of trust commonly appear in real attacks, while NIST’s Digital Identity Guidelines are a strong reference point for designing higher-assurance authentication and verification flows.
Reviewing MITRE ATT&CK Enterprise Matrix can also help teams connect slippage-like abuse to credential access, privilege escalation, and social engineering techniques that often precede broader compromise.
Risk and Threat Considerations
Slippage attacks matter because they turn a legitimate approval step into an adversary-controlled outcome. The risk is highest when the user can authorise money movement, access grants, or sensitive account changes without strong out-of-band verification or a clear, final-state preview.
Failure mechanism: The interface or workflow reduces careful review, so the user approves an action that differs from their intent, often because the prompt is rushed, ambiguous, or visually similar to a trusted request.
Impact: The attacker can obtain unintended access, authorise harmful transactions, or create a trusted session or permission state that supports follow-on compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-63, CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Slippage attacks exploit weak identity verification and approval steps. |
| Recommendation — Use higher-assurance verification for risky approvals and login flows. | ||
| MITRE ATT&CK | T1566 — Phishing | Slippage attacks use social engineering to induce unintended user action. |
| Recommendation — Map deceptive approval flows to phishing techniques and monitor for abuse patterns. | ||
| CIS Controls v8 | CIS-5 — Account Management | Slippage can lead to unintended access grants and account changes. |
| Recommendation — Review and restrict approval paths that can create or expand access. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | These attacks often target approval and authentication steps that rely on user trust. |
| Recommendation — Harden authenticator and approval workflows to reduce unintended acceptance. | ||
Practitioner Guidance
Why practitioners should care: Slippage is a design and assurance problem, not just a user-training problem. If the approval screen does not make the exact consequence obvious, the control can fail even when the user is acting in good faith.
Common misunderstanding: Teams often assume that a confirmation prompt is protective simply because it exists. In practice, the prompt must be specific enough to distinguish the real action from a lookalike request and important enough to interrupt autopilot behaviour.
Practitioner takeaway: Treat high-consequence approvals as security controls in their own right, and design them so the user must understand what they are authorising before the action can proceed.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 29, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org