An SMS one-time passcode is a short-lived code sent by text message and used to confirm a login, onboarding step, or transaction. It is easy to deploy, but it can be exposed to forwarding, SIM swap, interception, and phishing, which makes it weaker than stronger device or network based authentication methods.
What SMS one-time passcodes are and how they work
SMS one-time passcodes are a form of short-lived, out-of-band authentication. They are usually used when a service needs a quick second factor for login, enrolment, account recovery, or a sensitive transaction, and the code is delivered over the mobile network rather than generated inside the app or device.
The appeal is simplicity: almost every user can receive a text message, so deployment friction is low. The trade-off is that the message travels through a channel that was not designed as a strong authenticator. That makes the method easy to adopt, but also easier to target than stronger phishing-resistant options.
Why SMS OTP is weaker than stronger authenticators
The security weakness is not the concept of a one-time code itself, but the delivery path. SMS can be forwarded, intercepted, socially engineered, or displaced through SIM swap attacks, so possession of the phone number does not reliably prove possession of the intended device or user session. That is why SMS OTP is typically treated as a weaker fallback rather than a preferred primary factor.
Compared with app-based or device-bound authenticators, SMS OTP has less binding to the authenticating device and less resistance to adversary-in-the-middle phishing. When the attacker can coerce the victim into entering the code, or can redirect the number to a different SIM, the second factor no longer adds much protection.
For a broader view of how text-message codes compare with stronger options such as authenticator apps and device-bound methods, see Authenticator Apps and OTP Guide.
Common failure modes and abuse paths
SMS OTP breaks down when the delivery assumption is false. Forwarded messages, SIM swap fraud, voicemail or inbox compromise, and phishing kits that proxy the code in real time are all practical abuse paths. The attacker does not need to defeat the code mathematically, only to obtain it before expiry and use it fast enough.
That is why SMS OTP is often attractive in account takeover campaigns: once the victim is tricked into revealing the code, the attacker can complete login, reset a password, or approve a transaction while appearing to hold a valid second factor. The code may still be short-lived, but short-lived does not mean phishing-resistant.
Guidance on phishing relay, SIM swap, code sharing scams, and rate-limiting controls is covered in OTP security.
Where organisations still use it, and how to reduce exposure
Many organisations keep SMS OTP for reach, recovery, or step-up authentication because it works with almost any handset. In practice, that means it often remains in the account lifecycle even when better authenticators are available. The key governance question is not whether SMS OTP exists, but whether it is allowed for high-risk actions, privileged accounts, or recovery paths that attackers routinely target.
If SMS OTP must remain in use, it should be paired with stronger account controls, risk-based step-up logic, and careful recovery design so the text code is not the only thing standing between the attacker and the account. The strongest improvement usually comes from reducing how often users see SMS as the default path and making phishing-resistant authentication the norm for sensitive access.
For a practical comparison of legacy and stronger MFA choices, see MFA Guide.
Detection and response after suspected compromise
When SMS OTP is involved in a compromise, the response should focus on the identity session and the phone number, not just the password. A successful abuse path can leave the attacker with an active session even after the code expires, so organisations should review recent sign-ins, transaction history, recovery changes, and any evidence of number redirection or SIM change.
Post-incident review often needs to include credential reset, session invalidation, and re-enrolment into a stronger factor. If the account was used for sensitive access, the organisation should also treat the phone number as potentially exposed and monitor for follow-on social engineering against the same user.
For an example of SMS-based phishing leading to downstream account access, see Twilio 0ktapus breach 2022.
Risk and Threat Considerations
SMS OTP creates a concentrated trust dependency on the mobile number and the telecom path that carries the code. If an attacker can intercept, redirect, or socially engineer that channel, the second factor can fail even when the login flow appears normal.
Failure mechanism: The attacker captures the one-time code through phishing, SIM swap, message forwarding, or device compromise, then reuses it before expiry to complete authentication or account recovery.
Impact: This can lead to account takeover, session hijacking, fraudulent transactions, and compromise of any access or recovery path that still trusts the SMS factor.
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, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Defines authenticator assurance and phishing-resistant authentication for OTP choices |
| Recommendation — Prefer phishing-resistant authenticators over SMS OTP for sensitive access and step-up flows. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Covers issuance, protection, and lifecycle handling of authenticators used in login flows |
| IA-2 — Identification and Authentication (Organizational Users) | Applies when users authenticate with an SMS code as part of account access | |
| IA-8 — Identification and Authentication (Non-Organizational Users) | Applies where external users authenticate with SMS OTP | |
| Recommendation — Manage SMS OTP as a low-assurance authenticator and tightly govern its issuance and use. Require stronger authentication for higher-risk user access and avoid relying on SMS OTP alone. Use SMS OTP only where external-user assurance needs remain limited and risk is acceptable. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Supports restricting weaker authentication paths for privileged or sensitive access |
| Recommendation — Restrict SMS OTP use for sensitive access paths and enforce stronger controls where risk is higher. | ||
| MITRE ATT&CK | T1111 — Multi-Factor Authentication Interception | Covers interception of one-time codes during authentication abuse |
| T1556 — Modify Authentication Process | Includes abuse of authentication flows and factors to bypass intended login controls | |
| Recommendation — Hunt for code interception, real-time phishing, and related MFA abuse patterns in authentication logs. Detect tampering or manipulation of authentication workflows that weakens SMS OTP validation. | ||
Practitioner Guidance
Why practitioners should care: SMS OTP is best treated as a compatibility control, not a preferred trust anchor, because its security depends on a channel that is vulnerable to redirection and relay. If it remains enabled, define exactly which users, actions, and recovery flows may use it.
Common misunderstanding: A short expiry time does not make SMS OTP phishing-resistant. Expiry reduces replay time, but it does not stop an attacker from collecting and using the code in real time.
Practitioner takeaway: Use SMS OTP selectively, reserve stronger authenticators for higher-risk access, and review any flow where the text code is still the easiest path into the account.
Related resources from NHI Mgmt Group
- One Time Passcode
- How should security teams use phone intelligence to decide whether to send an SMS one-time passcode?
- How should teams implement SMS one-time passcode login in a Next.js app without weakening session security?
- Why do SMS and email one-time passwords remain risky for enterprise access?
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 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org