Scammers abuse Google Voice, prepaid SIMs, and “verify your number” scripts to steal SMS one-time codes, charge unlock / reactivation fees, or convince you to buy gift cards so a “support agent” can “restore” a number. Google does not cold-call to demand gift-card PINs or remote-access apps so you can keep a Voice number.
This guide is Voice- and phone-verification–specific. Broader login theft: Phishing and account takeover. Spoofed bank callbacks: Fake bank security alerts. Landscape: Credit and debt scams.
How the verification play works
| What you see | What is actually happening |
|---|---|
| “Google Voice Support” says your number will be recycled unless you pay a $49–$199 fee | Impersonation; real Google billing is in-account, not gift cards |
| A buyer, employer, or dating match asks you to read them a text code “to verify you are human” | They are hijacking your Voice / SMS MFA on another account |
| A job or rental portal texts a code and a stranger asks you to forward it | Account takeover of their victim funnel using your phone |
| Caller wants AnyDesk / TeamViewer “to unlock Voice” | Remote-access theft (Fake tech-support refund scams) |
| “Pay with Vanilla / Apple / Google Play cards and read the PINs” | Irreversible extract (Gift cards and prepaid debit risks) |
Google Voice is a legitimate Google product. The scam is the unsolicited fee, the code handoff, or the fake support channel—not the app itself.
Common Google Voice / verification scripts
- Fake Google Voice support. Caller or chat claims suspension, spam flags, or “carrier unlock.” Demands gift cards, crypto, or a wire. Hang up; sign in only at voice.google.com from a bookmark you typed yourself.
- Code-forwarding for Marketplace / romance / “employer.” Stranger sends money or a job offer, then asks for the SMS or Voice code that just arrived. That code is often MFA for their Cash App, bank, or crypto account—or for stealing your Google login.
- Paid “number verification” portals. Fake apartment, job, or background sites charge a fee to “verify your Google Voice / VoIP number.” Real landlords and employers do not collect gift-card PINs for SMS checks. Job-fee cousins: Fake job background-check fee scams.
- SIM-swap adjacent pressure. Scammer already social-engineered a carrier; they push you to approve a Voice port or read recovery codes.
- Refund / overpayment with Voice callback. Fake deposit script plus a “Google-verified” callback number that is just another Voice line.
Worked example
Sam lists concert tickets. A buyer on OfferUp says they will pay via Cash App after Sam “verifies” with Google Voice. Sam gets a text: “G-482913 is your Google verification code.” The buyer asks Sam to read it “so Cash App can release the hold.” Sam reads the code. Minutes later Sam’s Gmail shows a new device and a password-reset email. The buyer disappears. Loss path: Google account takeover, not a failed ticket sale.
Healthy version: never share a verification code with anyone who contacted you first. Meet locally or use a platform’s built-in payment. Confirm Completed status only inside your apps.
Hard rules that prevent most losses
- Never read an SMS, Voice, authenticator, or email one-time code to an inbound caller, chat, or “buyer.”
- Google and banks do not ask for gift-card PINs to restore Voice, Gmail, or a bank login.
- Sign in only through official apps or URLs you type; ignore “voice-google-support.com” lookalikes.
- Refuse any fee to “unlock,” “whitelist,” or “carrier-verify” a Google Voice number outside Google’s own checkout.
- Prefer authenticator apps or hardware keys over SMS-only MFA on email and banking when you can.
If you already shared a code or paid a fee
- On a clean device, change your Google password; review Devices and 2-Step Verification at myaccount.google.com; sign out unknown sessions.
- If gift cards were bought, contact the issuer/retailer fraud line immediately with card numbers and receipts; file ReportFraud.ftc.gov.
- Call your bank or card issuer from the number on the card if you wired, Zelled, or carded a “verification fee.”
- Treat shared remote-access sessions as full compromise: Phishing and account takeover.
- Reject “recovery agents” who charge a second fee to get the first loss back.
Checklist
- Treat unsolicited Google Voice “support” as hostile until you verify in-account.
- Never forward or read verification codes to strangers.
- Refuse gift-card, crypto, or wire “unlock” fees.
- Use official Google Voice / Google Account settings only.
- Strengthen MFA beyond SMS-only on email and banking.
- Report attempts even when you walked away.
WhatsApp uses the same “read me the code” account-takeover pattern: Fake WhatsApp account-takeover scams.
Educational only. Not legal, security, or fraud-recovery advice. Google, carrier, and bank policies change; verify contacts through official apps and statements.