Blog

Why you should never read a one-time passcode to someone who called you

A one-time passcode proves you hold the phone at that moment, nothing more. How scammers use you to pass the check, and what a real request looks like.

A one-time passcode is a short number, usually six digits, that a company sends to your phone or email to prove that the person logging in or paying is you. It proves exactly one thing: that someone with access to that phone or inbox is present right now. If a person who called you asks you to read the code aloud, then you are handing the proof to them, and the proof was the only thing standing between them and your account. That is the whole story, and the rest of this article explains why it works so well for criminals, how to recognize the many disguises it wears, and what to do if you already said the digits.

What a code is meant to do

Passwords have a weakness: they can be copied. A password leaked in a data breach, typed into a fake website or guessed from a pattern works just as well for a stranger as it does for you. So many financial sites add a second step. After the password, the site sends a code to a phone number or email address that you registered earlier, and you type it into the site. The idea is that a thief who has the password does not also have your phone.

This second step is usually called two-step verification or two-factor authentication, and it is the main defense against an account takeover, where a stranger gets into your account and changes it. The code has three important properties:

  • It is generated for one action, such as a sign-in, a password reset, adding a payee or approving an online card purchase.
  • It is short-lived. Codes commonly expire after a few minutes, which limits how long a stolen one is useful.
  • It is meant to be typed by you into a screen you opened. Nothing about the design anticipates you saying it to another person.

A code also does not identify who you are. It identifies who has the phone. If the person who has the phone is you, and you hand the number to a caller, the system cannot tell the difference between you passing the check and you passing it to someone else.

Why criminals do not just guess the code

A six-digit code has 1,000,000 possible values, from 000000 to 999999. Say, as an illustration, that a site allows five wrong tries before it locks the attempt. A criminal guessing blindly would have 5 chances in 1,000,000, which is 0.0005 percent, or one in 200,000. That is hopeless at any scale, which is why the codes work against automated attacks.

So the criminal changes the problem. Instead of guessing the code, he persuades you to tell him the right one. The real code, sent by the real site to your real phone, is just as good as a guess that happened to be right, and it arrives with no effort. One persuaded person delivers the right code every time, while blind guessing almost never does. That is why the scams that rely on talking to you are the ones to watch, not attacks on the code itself.

The attack, step by step

Here is the common sequence, as it unfolds on a typical call or message. The columns show who does what and what you see.

Step What the criminal does What you see
1 Obtains your username and password from a breach, a fake login page or a reused password Nothing
2 Tries to sign in or reset the password at the real site Nothing yet
3 The real site texts you a code A text with a code you did not request, perhaps with the site's name
4 The criminal calls or texts, posing as the issuer, a fraud team, a delivery company or a buyer A convincing call, often with a reason that explains the text
5 He asks you to read the code "to verify" or "to cancel" something A request that seems routine
6 He types the code into the real site Nothing, until you notice the changes
7 He changes the password, adds a device, moves money or makes purchases Alerts, if you have them, or surprises later

The sequence shows why timing is a clue. The call comes within seconds of the code arriving, because the criminal is waiting at the login screen. If a stranger calls and a code appears while you are still talking, the code is a result of what that person is doing on the other end. A call that begins with "you will receive a text" and then waits is a script.

The costumes the request wears

The request is always the same, and the explanation changes. These are the versions that are widely reported.

  • "We are verifying you." The caller says he is from your bank or card issuer and has to confirm your identity. This is the form in the caller says they are my bank's fraud department: three scenarios.
  • "We are cancelling a fraudulent transaction." The code is said to be a cancellation code. In fact it approves a transfer or a purchase.
  • "We sent the code to the wrong number." A person, often a stranger, says that a code was texted to you by mistake and asks you to send it back or read it out. It is a code for an account the sender is trying to open or recover with your phone number.
  • "Verify you are a real buyer." On a resale marketplace, a "buyer" asks for a code to prove you are real. The code is for an account they are setting up against your number.
  • "A friend of yours needs help." A message appears to come from someone you know whose account has been taken over. They say they are locked out and ask you to forward the code that was texted to you.
  • "Approve this payment." Online card purchases sometimes ask you to confirm with a code, a step known as 3-D Secure. A criminal who has a card number from a breach can start a purchase and then needs the code that your issuer sends to you. A caller offers a reason for you to read it out.
  • "Confirm you got the package." A delivery or customs message asks for a code to release a parcel.

None of these is about the thing the caller says it is about. The words differ because the real purpose is to carry a code from your phone to a screen the criminal controls.

How to tell what a code is for

A real code message usually says what it is for, and that is your most useful check. Read the whole text, not only the digits. Typical wording names the company and the action: signing in, resetting a password, adding a device, or approving a purchase, and a card purchase code often states the merchant and the amount. Wording varies by company, so do not treat any phrase as a guarantee, but the principle holds: if the message says it is for a sign-in and you are not signing in, then someone else is.

Ask yourself two questions before you do anything with a code:

  1. Did I start this action a moment ago? If you just opened the site yourself and asked for a password reset, a code is expected. If you did not, it is a warning that someone else has your username, and you should change your password at the real site.
  2. Is the person asking me for it someone I called, at a number I chose? The danger is the code going to a person you did not choose.

If both answers are no, do not give the code to anyone, close the call and treat the account as one that may be under attack.

Small details that give the script away

Beyond the code itself, a few habits of the person on the line are worth noticing. None is proof alone, and a skilled caller avoids several, but together they are a pattern.

  • Urgency about a code in particular. A genuine system gives you minutes. A caller who says "read it now, it is about to expire" is pushing you past the point where you would read the text carefully.
  • Instructions to stay on the line. You are told not to hang up, not to open an app and not to check anything, because checking would end the story.
  • Reassurance that the code is safe to share. The message that carries the code often warns that no one from the company will ask for it. A caller who says the warning does not apply to this call is contradicting the company's own text.
  • A request that arrives in a chain. First a code, then a second code, then a request to approve something in the app. Each one opens another door, and a caller who needs several is working through a login.
  • A story that moves between channels. The call starts as a fraud alert, becomes a verification, then a refund. Real processes do not change their explanation halfway through.

The practical answer is to treat the text as the authority. If the text says not to share the code with anyone, it applies to the nicest caller you have ever spoken to.

The one case that can look the same

There is a case that confuses people: some issuers verify a caller by texting a code and asking you to read it to the representative. That can happen on a call you placed to the number on your own card. The difference is who started it. When you called the published number, you know who is on the line. When someone called you, you do not.

Even in the legitimate case, check the text. It should name the issuer and say what it is for, and you should be able to see it was triggered by your call. If anything feels off, you can end the call and call back, or ask for another verification method. The rule that keeps you safe is simple: never give a code to a person who contacted you. It costs nothing to follow it, and it handles the rare exception, because a real representative can always tell you to call back.

If you already read a code aloud

It is common. Scammers are good at this, and the embarrassment is part of what they count on. Move fast, and do these in order.

  1. Hang up. Do not take a callback.
  2. Change the password on the affected account at the real site, typed by you, and sign out of all other sessions if the site offers it.
  3. Call the number on the back of your card, or the number on the real company's site for a non-card account, and tell them what happened and what the code was for. Ask them to review recent activity, lock or replace the card and block anything that is pending.
  4. Check what changed. Look at sign-in history, linked devices, payees, contact details and forwarding rules on your email.
  5. Change the same password anywhere else you used it. If the criminal had it, he will try it elsewhere.
  6. Consider a credit freeze or a fraud alert if the account held personal details. The facts: a freeze is free to place and lift, and an initial fraud alert lasts at least one year.
  7. Report it to the FTC at ReportFraud.ftc.gov, and to the CFPB if a company does not help.

The money question is the one most people ask first. A criminal who used your card number without your permission has made an unauthorized charge, and federal law caps your liability for those at $50. If you were persuaded to approve or send a payment yourself, the picture is less settled and depends on the payment method and the facts. scam payment or unauthorized charge: why your protections can differ explains how the two differ. Do not wait to find out which one you have. Call first.

Making the code harder to steal

You cannot control what the next caller says, but you can narrow what a stolen code can do.

  • Use a unique password for each financial account, so a leak at one company does not open another.
  • Consider an authenticator app or a passkey instead of text codes where the site offers them. These are generally regarded as stronger than text messages, which can be intercepted if a criminal persuades a carrier to move your number. They do not stop you from reading a code aloud, so the rule still applies.
  • Turn on alerts for sign-ins, password changes and new payees. An alert is the first sign that a code was used.
  • Know your own call-back habit. If you decide in advance that a call you did not start never gets a code, you will not need to decide under pressure.

For the situation where the message came by text and you want to check whether it is genuine, A text says there is fraud on my card. How do I check without replying? gives a single path that does not depend on anything in the message.

Key takeaways

  • A code proves that someone holds your phone at that moment. Reading it to a caller gives that proof to them.
  • A six-digit code has 1,000,000 values, so criminals do not guess it. They trigger the real code and ask you for it, usually within seconds of the text arriving.
  • The cover story changes (verification, cancellation, wrong number, buyer check, delivery) but the request is always for the digits. Read the full text of the message to see what the code is really for.
  • The rule is simple: never give a code to someone who contacted you. The only reasonable exception is a call you started, to the number on the card, and even then you can hang up and call back.
  • If you already read one out, change the password at the real site, call the number on the back of your card, check what changed and report it.

Terms used in this article

Latest on this topic