Is SMS Two-Factor Authentication Safe?
Published by Elvento Labs, the maker of Ghost. How we research and review
Is SMS two-factor authentication safe? It is safe enough to be much better than a password alone, and not safe enough to be the only thing guarding your email, your bank, or any account you couldn't afford to lose. A texted code stops the most common attack: someone signing in with a stolen or guessed password. It does not stop a thief who takes over your phone number, a fake login page that asks for the code, or a caller who talks you into reading it out. So don't turn it off. Keep it where it is the only option, and add a stronger method on the accounts that matter most. This guide explains each risk, how likely it is, and how to decide.
Is SMS Two-Factor Authentication Safe? The Short Answer
Three statements are all true at once, and the honest answer needs all three.
It is far better than no second factor. A password by itself fails the moment it is leaked, reused, or guessed. A code sent to your phone means the person with your password still can't sign in. CISA's fact sheet on phishing-resistant MFA says so directly: any form of MFA is better than no MFA.
It is the weakest of the common options. The same fact sheet ranks MFA methods from strongest to weakest, and SMS and voice codes sit at the bottom. CISA says they should only be used as a last resort, though they can serve as a temporary solution on the way to something stronger.
Whether that matters depends on the account. A texted code on a streaming service or a loyalty program is fine. The same code as the only lock on your primary email, your bank, or a cryptocurrency exchange is a weak point worth fixing.
| Your situation | Verdict |
|---|---|
| The account offers only SMS codes | Turn them on. It is a large improvement over a password alone. |
| The account offers SMS and an authenticator app | Use the app, and keep SMS only if the service requires a fallback. |
| The account offers passkeys or security keys | Use them for email, money, and work accounts. |
| You currently have no second factor at all | Turning on SMS codes today beats waiting until you have time to set up something better. |
The rest of this article fills in the reasoning, so you can judge your own accounts instead of following a blanket rule.
How a Texted Code Reaches You
Understanding the route a code takes explains nearly every weakness that follows.
When you sign in with a password, the service generates a short code and hands it to a messaging provider. The provider passes it into the phone network, your carrier looks up which SIM currently holds your number, and the message is delivered to that device. You read the code and type it into the login page. The FTC's guide to two-factor authentication describes these one-time passcodes as typically six digits and good for a single use.
Security people group login credentials into three categories, which the FTC summarizes as something you know, something you have, and something you are. A texted code is supposed to prove the second: that you have your phone. Look closely and it proves something narrower. It shows that whoever typed the code could read a message sent to your phone number at that moment.
That gap is the source of the trouble. Your phone is a physical object in your pocket. Your number is an entry in your carrier's records that can be reassigned to a different SIM, moved to a different carrier, or forwarded. The code follows the number wherever it goes.
Two other properties of SMS matter here:
- The code is readable along the way. Standard SMS is not end-to-end encrypted, so the companies that carry the message can see it. Our explainer on SMS security and encryption covers what that means in practice.
- The code works for anyone who types it. Nothing ties those digits to your device or to the real website. If you type them into the wrong page, or read them to the wrong person, they work just as well for that person as for you.
Services limit the damage by making codes expire quickly. NIST's digital identity guidelines, for instance, say this kind of verification must be treated as invalid unless it is completed within 10 minutes. A short lifetime shrinks the window. It does not close it, because the attacks that work against SMS codes happen in real time.
What SMS 2FA Protects You From
It is easy to read a list of weaknesses and conclude that texted codes are useless. They aren't. They defeat a whole category of attack that needs no skill and runs at enormous scale.
Leaked and reused passwords. When a website is breached, the stolen email and password pairs get tried on other services automatically. If you reused the password, an account with no second factor falls without anyone ever targeting you personally. With SMS codes on, the automated attempt stalls at the code prompt.
Guessed passwords. CISA's fact sheet notes that MFA stops common techniques such as password spraying, where an attacker tries a few popular passwords against a very large number of accounts.
A password someone watched you type or found written down. A nosy coworker, a housemate, or someone who found an old notebook has your password but not your phone.
SMS codes also work as an alarm. A verification text you didn't ask for often means someone just entered your correct password somewhere. Without the second factor you would not have found out until the damage was done.
For most people, most of the time, these password-only attacks are the realistic threat. The attacks that beat SMS codes take more effort per victim, as the next section shows. That is why CISA's guidance on multifactor authentication urges people to turn on some form of it everywhere it is offered, and why the weakest form still earns its place.
SMS 2FA Risks: How Codes Get Stolen
The known SMS two-factor authentication vulnerabilities fall into six groups. They are listed roughly from most to least relevant for an ordinary person.
Fake login pages that relay your code
This is the weakness people overlook, because it has nothing to do with the phone network. You get a message with a link, the page looks exactly like your bank's or your email provider's, and you enter your username and password. The fake page passes them to the real site, the real site texts you a genuine code, and the fake page asks for it. You type it in. The attacker's software uses it within seconds.
CISA's fact sheet describes this technique as widely used, and its own example involves a victim submitting the code from an authenticator app. That detail matters: an app-generated code is exactly as phishable as a texted one. Moving from SMS to an app fixes the phone-number problem, not this one. If a link in a text brought you to a login page, our guide for people who clicked a link in a scam text covers what to do next.
Someone simply asks you for the code
The lowest-tech attack is a request. A caller claiming to be your bank's fraud team says they need to "verify your identity" with the code they are about to send. A marketplace buyer says they want to confirm you are a real person. A stranger texts that they entered your number by mistake and asks you to forward the code that arrived.
Example scam text fishing for a code
+1 (202) 555-0171
Text Message
Hi, sorry to bother you. I typed your number by accident when signing up and my 6 digit code went to your phone. Could you send it to me?
In every version, the code you receive is for your own account, and the person asking is the one trying to get into it. The FTC's advice is blunt: no matter what the story is, don't share your verification code.
SIM swaps and port-outs
Here the attacker goes after the number itself. CISA defines a SIM swap as a form of social engineering in which attackers convince a cellular carrier to transfer control of the user's phone number to a SIM card the attacker controls. A port-out does the same thing by moving the number to a different carrier. Either way, your texts start arriving on someone else's phone, and the FTC lists this as the main drawback of texted codes: hackers can take over your phone number through a SIM card swap attack.
A SIM swap takes real effort. The attacker needs your number, personal details convincing enough to impersonate you, and a carrier employee or process that can be fooled. That makes it a targeted attack. It is aimed at people believed to have something worth the work, not sprayed at millions. Our guide to SIM swapping and its warning signs explains how it unfolds and what it looks like from the victim's side.
Interception inside the phone network
Phone networks exchange routing information using a signaling system called SS7, and CISA's fact sheet lists exploitation of SS7 vulnerabilities as a way attackers obtain codes sent by text or voice. This is real, and it is also the least likely item on this list to affect you. It takes access to carrier signaling systems, which is out of reach for a typical criminal. Treat it as a reason high-value targets should not rely on SMS, not as an everyday worry.
Exposure on your own devices
The code can also leak after it arrives safely.
- Lock-screen previews. If message previews show on a locked phone, anyone who can see the screen can read the code without unlocking it.
- Synced messages. Texts mirrored to a tablet, a laptop, or a smartwatch are readable on each of those, including the shared family tablet in the kitchen.
- Apps with permission to read texts. A malicious or overreaching app that has been granted access to SMS can read incoming codes.
- An old phone number. If you changed numbers and left the old one on an account, the code now goes to whoever was assigned that number next.
The recovery back door
Many services let you reset a forgotten password by texting a code to the phone number on file. If that option exists, a person who controls your number may not need your password at all. They click "forgot password," receive the code, and set a new one. In that situation SMS is not a second factor layered on top of the password. It replaces the password. This is why removing your phone number as a recovery method, where the service allows it, matters as much as changing your sign-in method.
What NIST, CISA and the FTC Say About SMS MFA Security
Three US government bodies have published positions on SMS MFA security, and they agree more than headlines suggest. None says texted codes are worthless. All say better options exist.
NIST: restricted, with conditions
NIST's SP 800-63B, in its fourth revision published in 2025, sets authentication requirements for US federal systems and is widely used as a benchmark elsewhere. It treats a code sent over the public phone network, by text or voice, as a restricted authenticator. Restricted does not mean prohibited. It means an organization that uses the method takes on obligations, including:
- making alternative authenticator types available to subscribers,
- considering risk indicators such as a device swap, SIM change, or number porting before sending a code, and
- informing subscribers about the method's limitations.
NIST also notes that the restricted status may be adjusted as threats evolve.
Two other parts of the document are useful context. First, NIST says email shall not be used for this kind of verification at all, in part because an inbox may be accessible with only a password. A code sent by email is not an upgrade from one sent by text. Second, NIST defines phishing resistance as protection that does not rely on the vigilance of the person signing in, and it states that manually entered codes, whether texted or app-generated, do not qualify, because typing a code does not bind it to the specific session.
CISA: last on the list
CISA's fact sheet, published in October 2022 for IT leaders, ranks methods by which threats can defeat them.
| Method | Phishing | SIM swap and SS7 | CISA's comment |
|---|---|---|---|
| FIDO/WebAuthn (passkeys, security keys) | Resistant | Not applicable | The gold standard for MFA |
| Authenticator app code or push with number matching | Vulnerable | Not applicable | Best option where phishing-resistant MFA is not yet possible |
| Push approval without number matching | Vulnerable to push bombing and user error | Not applicable | Weaker than number matching |
| SMS or voice code | Vulnerable | Vulnerable | Last resort, or a temporary step toward something stronger |
Read the table row by row and the logic is clear. Each step up removes a class of attack. An authenticator app removes the phone network from the picture. FIDO-based sign-in removes the typed code, and with it the fake login page.
FTC: the consumer version
The FTC's consumer guide lands in the same place in plainer words. It says authenticator apps are safer than text messages because the passcode isn't susceptible to a SIM card swap attack, and it calls security keys the strongest method of two-factor authentication because they don't use credentials that hackers can steal.
How Much Risk You Actually Face
Rankings describe methods in the abstract. Your risk depends on what the account protects and whether anyone has a reason to single you out.
By account
| Account type | Is SMS alone acceptable? | Why |
|---|---|---|
| Primary email | No, upgrade first | Password resets for most other accounts arrive here |
| Banking, investing, crypto | Upgrade if the institution allows it | Direct access to money, and losses can be hard to reverse |
| Password manager, cloud storage | No | One account that unlocks many others |
| Work and admin accounts | Follow your employer's policy, and prefer stronger methods | A single takeover can affect other people |
| Main social media profiles | Upgrade when convenient | Used to impersonate you and scam your contacts |
| Shopping with saved cards | Acceptable, upgrade if offered | Limited damage, and card disputes exist |
| Forums, newsletters, loyalty programs | Acceptable | Low value to an attacker |
Some banks still offer only texted codes. If yours does, SMS is your option, and the hardening steps later in this article are how you make the most of it.
By person
You are a more likely target for number-takeover attacks if you hold cryptocurrency in accounts tied to your number, run a business or manage its finances, administer systems for an employer, have a public profile or a valuable social media handle, or are in a dispute with someone who knows your personal details. CISA's fact sheet makes a similar point for organizations, urging system administrators and other high-value targets to move to phishing-resistant methods first.
If none of that describes you, the fake login page and the "read me the code" request are the risks that matter, and they have little to do with the phone network. Caution with links and a firm rule about never sharing codes protect you more than worrying about SS7.
A final factor is how widely your number has spread. An attacker needs to know which number is tied to your accounts before trying to take it over, and a number that appears on public listings, old profiles, and people-search sites is easier to connect to you. Our overview of what someone can do with your phone number explains why the number is worth protecting in its own right.
Should You Turn Off SMS Two-Factor Authentication?
No, not unless you are putting something stronger in its place. Articles about SMS weaknesses sometimes leave readers thinking the responsible move is to disable it. An account with a password and a texted code is harder to break into than the same account with only a password, every time.
What you want to do is replace, in the right order:
- Add the stronger method first: an authenticator app, a passkey, or a security key.
- Sign out and sign back in using the new method, to confirm it works.
- Save the backup or recovery codes the service gives you, somewhere other than the phone itself.
- Only then remove SMS as a sign-in method, if the service lets you.
- Check the account's recovery settings separately, and remove the phone number there too where that is allowed and you have another recovery route.
Step 5 gets skipped most often. Many services keep texting codes for password resets even after you have set up an app, which leaves the recovery back door described earlier wide open.
Some services won't let you remove the phone number at all, or insist on SMS as a fallback. That is still a better position than SMS alone, because everyday sign-ins now go through the stronger method. Harden the number as described below and move on.
How to Make SMS 2FA Safer When It Is Your Only Option
When a service offers nothing but texted codes, you can still reduce most of the risk. These steps are ordered by how much they help.
1. Lock your number at the carrier. The major US carriers offer settings that block SIM changes and number transfers until you switch them off. This is the most direct defense against a SIM swap. Our walkthrough of port-out PIN and number lock settings on T-Mobile, AT&T and Verizon has the steps for each, and the broader SIM swap prevention guide covers the rest of the carrier account.
2. Use a unique password on every account. SMS codes are a second lock. They work best when the first lock holds, and a password manager makes unique passwords practical.
3. Never type a code on a page you reached from a link. Go to the site by typing its address or opening the official app. If you didn't start a sign-in, a code request is not for your benefit.
4. Never read or forward a code to anyone. That includes callers who say they are from the company and people you met online who want to "verify" you. Legitimate support staff do not need your sign-in code.
5. Hide message previews on your lock screen. On an iPhone, as of October 2026, the setting is under Settings, then Notifications, then Show Previews, where you can choose to show them only when the phone is unlocked. Android phones have an equivalent lock-screen notification setting whose name varies by manufacturer.
6. Review where your texts are mirrored. If your messages sync to a shared tablet or an old laptop, either stop syncing to that device or lock it properly.
7. Check which apps can read your texts. On Android, look through the SMS permission list in your settings and remove any app that has no clear need for it.
8. Keep the number on file current. Before you change phone numbers, update every account that texts you codes. Afterward is too late for the ones you forgot.
9. Use your real carrier number for codes. App-based and virtual numbers are a poor fit for this job. Services often reject them, and losing the number means losing the account. Our explainer on what a virtual phone number is goes into the limits.
10. Turn on sign-in alerts. Many services can email or notify you about a new sign-in or a changed setting. An alert you didn't expect is your cue to act.
Give the number that guards your accounts to fewer people
One more habit is worth adopting. The phone number that receives your bank's codes is also, for most people, the number they hand to marketplace buyers, contractors, and people they have only just met. Every one of those handoffs is another place the number can leak from, and another person who can connect it to your name.
Keeping that number for people and institutions you trust is where a tool like Ghost has a role, and only this role. Ghost sends SMS with your real number masked, so the recipient sees a protected sender ID instead (how it works). It is for sending messages to people who don't need your number. It is not a security product, and it is not meant for receiving verification codes or opening accounts elsewhere. Your codes should keep going to your real number, or better, to an authenticator app.
Stop handing out the number your bank texts
Message a one-time buyer or contractor from a masked sender with one free SMS, so the number that receives your login codes stays between you and the accounts it protects.
When SMS Codes Fail for Ordinary Reasons
Not every SMS problem is an attack. Texted codes also fail in mundane ways that lock people out of their own accounts, and that is a safety issue too.
Travel. Abroad without roaming, or on a local SIM with a different number, you may not receive texts sent to your home number. Set up an authenticator app or print backup codes before a trip, not at the airport.
A lost, broken, or stolen phone. Your number can be moved to a replacement phone by your carrier, which is one real advantage of SMS: recovery is simple. The same convenience is what a SIM swapper abuses.
Changing your number. People cancel a line and then discover that a dozen accounts still send codes to it. Carriers eventually reassign old numbers, so the next owner may receive your codes. Update accounts first, then cancel.
Delayed or missing texts. Codes sometimes arrive late or not at all, because of network congestion, a blocked short code, or spam filtering on your phone or at your carrier. If a code doesn't arrive, wait a minute before requesting another. Several requests in a row can leave you guessing which code is current. If your phone has moved between iPhone and Android, or you are unsure which kind of message you are receiving, our guide to why texts turn green and the comparison of RCS vs SMS explain the plumbing.
A dead zone. No signal means no code. An authenticator app generates codes offline, which is a practical reason to prefer one even if security is not your main concern.
These failures share one fix: have a second way in. Backup codes stored offline, a second registered method, or a security key in a drawer all turn a lockout into a minor delay.
What to Do About a Code You Did Not Request
An unexpected verification text is unsettling, but it also means the system worked: someone was stopped at the second step. How you respond depends on the pattern.
One stray code
A single code from a service you don't use, or use rarely, is often a stranger's typo. Do nothing with it. Don't reply, don't tap any link in the message, and don't share the digits if someone contacts you about it afterward.
A code from an account you care about
Assume someone has your password.
- Don't use any link in the text. Open the site or app yourself.
- Change the password to a new, unique one.
- Review recent sign-in activity and sign out of sessions you don't recognize.
- Check that the recovery email and phone number are still yours.
- If you reused that password elsewhere, change it on those accounts too.
Repeated codes, or codes followed by a phone call
A burst of codes, or a code followed by someone phoning to ask for it, is an active attempt. Hang up on the caller. Follow the steps above, then check your carrier account for changes you didn't make. If your phone also loses service unexpectedly, treat it as a possible SIM swap and contact your carrier from another phone straight away.
If you already shared a code
Act as though the account is compromised, because it may be.
After sharing a code with the wrong person
- Sign in yourself right away and change the password.
- Sign out of all other sessions and devices from the account security page.
- Check for changes: recovery email, phone number, forwarding rules, linked apps, new payees.
- Turn on a stronger second factor if the account offers one.
- If it was a bank or payment account, phone the institution using the number on your card.
- Warn your contacts if the account could be used to message them as you.
Speed matters more than thoroughness in the first few minutes. Our guide to protecting yourself from SMS scams covers the wider pattern these requests belong to. This is general information, not legal or financial advice. If money has moved, contact your bank and report the fraud to the relevant authority where you live.
When to Upgrade From SMS and What to Choose
You do not have to convert every account in an afternoon. Upgrade in order of what a takeover would cost you, and let certain events prompt you to speed up.
Reasons to upgrade now:
- The account is your primary email, a financial account, or a password manager.
- You received codes you didn't request, or a carrier alert about a SIM change or transfer.
- You fit one of the higher-risk descriptions above.
- You are about to travel, change carriers, or change numbers.
- A service you use has started offering passkeys.
What to move to. There are three realistic choices, and they are not mutually exclusive.
An authenticator app generates the code on your phone instead of receiving it by text. The FTC notes this is safer because the passcode isn't susceptible to a SIM swap. It still involves a code you type, so it remains phishable, and you need a plan for moving the app when you replace your phone.
A passkey replaces the typed code with a cryptographic exchange between your device and the real website, approved with your fingerprint, face, or device PIN. Because nothing is typed, there is nothing for a fake page to collect. CISA's fact sheet calls FIDO/WebAuthn, the technology behind passkeys, the only widely available phishing-resistant authentication.
A security key is a small physical device built on the same technology. The FTC calls security keys the strongest method of two-factor authentication. They suit people at higher risk and anyone who wants a backup that doesn't depend on a phone, and it is wise to register two so that losing one is not a crisis.
For most people the sensible path is a passkey or authenticator app on email first, then financial accounts, then everything else as time allows, with SMS left on wherever nothing better is offered. The texted code was never the problem to eliminate. Relying on it alone, for the accounts that hold everything else together, is the part worth changing.
Frequently Asked Questions
Is SMS two-factor authentication better than nothing?
Yes. A texted code blocks the most common attack, which is someone signing in with a stolen, leaked, or guessed password. CISA says any form of multifactor authentication is better than none.
Should I turn off SMS two-factor authentication?
Only after you have set up something stronger on that account, such as an authenticator app, a passkey, or a security key, and saved your backup codes. Turning it off with no replacement leaves the account protected by a password alone.
Can hackers intercept text message codes?
They can in some circumstances. The usual methods are taking over your phone number through a SIM swap or port-out, tricking you into typing the code on a fake login page, or persuading you to read it out. Interception inside the phone network is possible but takes far more capability.
Does NIST ban SMS for two-factor authentication?
No. NIST classifies codes sent over the phone network as a restricted authenticator. Organizations following its guidelines can still use them, but they have to offer subscribers an alternative and weigh risk signals such as a recent SIM change or number port.
Are email codes safer than SMS codes?
Not really. A code sent by email is only as safe as the inbox, and NIST does not allow email for this kind of verification in systems that follow its guidelines. If a service emails you codes, protect that inbox with a strong password and its own second factor.
Is an authenticator app code safe from phishing?
No. An app-generated code cannot be stolen by a SIM swap, but a fake login page can ask for it and use it within seconds, just like a texted code. Only passkeys and security keys are designed to resist phishing.
Why did I get a verification code I did not ask for?
Usually someone typed your phone number or your password into a login or sign-up form. A single code may be a typo by a stranger. Repeated codes for an account you own suggest someone has your password, so change it and never share the code.
Can I use a virtual or masked number to receive verification codes?
It is a poor idea for accounts you care about. Many services reject virtual numbers, and losing access to the number can lock you out. Ghost is built for sending messages and is not meant for receiving verification codes.
Sources
See also


