The short version: If someone who contacted you asks you to read out a code, it is a scam. This is true even if they say they are your bank, a tech company or a government agency. Our advice: hang up or stop replying, and contact the company yourself.

What is a code, and why does it matter?
Many websites and apps send you a short code when you sign in, often six numbers. It may come by text, by email or from an app on your phone. You may hear it called a verification code, a one-time passcode (OTP) or a security code. It proves it is really you.
Your password is like one lock on your front door. The code is like a second lock. The code adds a second check, so a stolen password alone is not enough. Our guide to two-factor authentication explains this second lock.
Scammers try to get you to open the second lock for them.
What the rule says
A code sent to you is only for you to sign in. If anyone who contacted you asks you for it, treat it as a scam. Google, for example, will not call you to check a code.
How the trick works
- A criminal already has your password, or is trying to reset it.
- They try to sign in. The website sends a code to your phone, because it thinks you are signing in.
- At the same time, the criminal calls or texts you. They say they are from your bank or a tech company. They say they need to “confirm it is you,” or “stop a fraud,” or “send a refund.”
- They ask you to read out the code you just got.
- If you do, they type it in and get into your account. They may change the password so you cannot get back in.
A fake website that looks like your bank or email works the same way. It asks for your password and then your code. The criminal types both into the real website. So go to websites yourself, not through a link in a message.
If you get a code you did not ask for
Sometimes a code arrives and you did not try to sign in. Someone may be trying to get into your account. Or someone may have typed your number or email by mistake.
- Do not share the code.
- Do not tap “approve” on any sign-in request you did not start.
- An unexpected approval request may mean someone already has your password. Change the password on a device you trust, by going to the website yourself.
If someone asks you for a code
- Hang up, or stop replying.
- Do not share anything.
- Contact the company yourself, using a number from its real website, your statement or its app.
Our alert on fake “official” calls explains this rule.
The same goes for PINs, recovery codes and passwords
Treat these like a code:
- Your PIN (secret number). Do not tell your bank card PIN or the PIN for your phone company account to someone who calls you.
- Recovery codes. These are backup codes that help you get back into an account if you lose your phone. Do not give a recovery code to someone who calls or messages you. Our guide to recovery codes and backups shows how to keep them safe.
- Your password. No real company needs you to say your password on the phone.
There is one small exception. With an Apple Account, you can choose a trusted friend or family member as your recovery contact. If you are locked out, you start the recovery yourself and then call or visit that person. They get a six-digit code on their device and tell it to you. If you are someone’s recovery contact, Apple says to give the code only to that person, directly. If anyone else asks you for it, do not give it.
In the UK
The rule is the same. Being asked for a one-time passcode, a password or a PIN is a warning sign.
If you already shared a code
It happens to careful, smart people. Act quickly and calmly.
- If money is involved, call your bank or card company first. Use the number on your card or in the bank’s official app. In the UK, you can also call 159 (if your bank takes part).
- Change the password for that account on a device you trust, by going to the website yourself. If you installed an app because a caller asked, delete it. If you have security software, run a scan.
- Report it.
Where to report
- In the US: report it to the FTC (the US Federal Trade Commission) at ReportFraud.ftc.gov. Forward scam texts to 7726 (SPAM).
- In the UK: in England, Wales and Northern Ireland, report it to Report Fraud (formerly Action Fraud) at reportfraud.police.uk or on 0300 123 2040. In Scotland, call Police Scotland on 101. Forward scam texts to 7726.
Do this today (under 10 minutes)
- Our advice: write the rule down (2 minutes). On a sticky note near your phone, write: “Don’t read out a code.”
- Our advice: save your bank’s number (3 minutes). Copy it from the back of your card into your phone’s contacts. UK readers: also save 159.
- Our advice: tell one person (3 minutes). Call or message someone you love and agree: “If anyone asks us for a code, we hang up and call back ourselves.”
See also: Why text-message codes are the weakest common 2FA (and what to use instead)
Sources
- US Federal Trade Commission (FTC), “What’s a verification code and why would someone ask me for it?”, 7 Mar 2024: https://consumer.ftc.gov/consumer-alerts/2024/03/whats-verification-code-why-would-someone-ask-me-it
- FTC, “Use Two-Factor Authentication to Protect Your Accounts” (two locks; codes by text, email or app): https://consumer.ftc.gov/articles/use-two-factor-authentication-protect-your-accounts
- FTC, “Never move your money to protect it. That’s a scam.” (no caller will ask for the code): https://consumer.ftc.gov/consumer-alerts/2024/03/never-move-your-money-protect-it-thats-scam
- FTC, “SIM Swap Scams: How To Protect Yourself” (they may change your passwords; phone account PIN): https://consumer.ftc.gov/consumer-alerts/2019/10/sim-swap-scams-how-protect-yourself
- FTC, “What To Do if You Were Scammed”: https://consumer.ftc.gov/articles/what-do-if-you-were-scammed
- FTC, “How To Recognize and Report Spam Text Messages” (7726): https://consumer.ftc.gov/articles/how-recognize-and-report-spam-text-messages
- Google Account Help (no call from Google to check a code): https://support.google.com/accounts/answer/185839
- Google Help, “Google Account Security Scam via Phone Call”: https://support.google.com/faqs/answer/17170932
- US Cybersecurity and Infrastructure Security Agency (CISA), “Implementing Phishing-Resistant MFA” fact sheet (fake sign-in page asks for the password and the code): https://www.cisa.gov/sites/default/files/publications/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf
- Microsoft Support, “Why is Microsoft texting me?” (codes you did not ask for): https://support.microsoft.com/en-us/accounts-billing/security/why-is-microsoft-texting-me
- UK National Cyber Security Centre (NCSC), guidance for high-risk individuals (sign-in approvals you did not expect): https://www.ncsc.gov.uk/collection/defending-democracy/guidance-for-high-risk-individuals
- Take Five to Stop Fraud (UK), “Protect yourself”: https://www.takefive-stopfraud.org.uk/protect-yourself/
- Report Fraud, courier fraud (PIN as a warning sign): https://www.reportfraud.police.uk/courier-fraud
- Report Fraud, “Report Fraud service goes live”, 4 Dec 2025 (England, Wales and Northern Ireland; Scotland 101; 0300 123 2040): https://www.reportfraud.police.uk/news/report-fraud-service-goes-live/
- Report Fraud, “How to report suspicious messages, calls and websites” (7726): https://www.reportfraud.police.uk/how-to-report-suspicious-activity/
- Stop Scams UK, 159: https://stopscamsuk.org.uk/campaign/get-help-now/
- Apple Support, “Set up a recovery contact for your Apple Account” (published 14 Sep 2026): https://support.apple.com/en-us/102641
- Apple Support, “Get a recovery code for a friend or family member as their Apple Account recovery contact” (published 14 Sep 2026): https://support.apple.com/en-us/102608
Checked: 5 Nov 2026. Our disclosure: SafeinAI has no affiliate links and earns nothing from the sites or tools named on this page. If this ever changes we will say so here, on this page.
Leave a Reply