The message looks real. Check the sender.
A familiar logo or convincing caller does not verify an identity. Give yourself a moment before responding.
How it can happen.
A few situations you might recognize. Open an example to see the pattern behind it.
Bank impersonation and “safe account” transfers
A caller says your money is at risk and directs you to move it. A convincing caller ID, personal details, or official-sounding handoff does not prove who is speaking.
Imagine this: A “fraud specialist” asks you to transfer your balance to a temporary holding account.
Delivery, toll, and payment texts
A small overdue fee or failed delivery becomes a reason to enter card details or sign in through a link. Check the real provider independently.
Imagine this: A text demands a small redelivery payment for a package you are expecting. The link goes to a lookalike website.
QR-code traps
A code can hide the destination until you scan it. An unexpected package or message may direct you to a page designed to collect credentials or card information.
Imagine this: A surprise parcel includes a QR code to “find out who sent it.” The page asks you to sign in.
AI voice and family impersonation
A recognizable voice can be imitated. Urgency and secrecy make it harder to pause and check with the person through a number you already know.
Imagine this: Someone sounding like a relative says they urgently need money and asks you not to tell anyone.
Fake support and account-security alerts
An alarming pop-up or message directs you to a supposed technician. Requests for remote access or payment can turn an invented computer problem into a real one.
Imagine this: A browser warning tells you to call support immediately. The caller then asks to control your computer.
Use a separate route
Open the organization’s official app or type its known website address yourself. Verify the request there instead of using links or phone numbers in the message.
Protect account access
If you shared credentials, change the affected password through the real service and enable multi-factor authentication. Never share a login code with someone who contacts you.
Save and report
Keep a copy of the message and sender details without opening attachments. Use the service’s official reporting channel. If money moved, contact your payment provider promptly.
Yes, this is a situation you can bring to us.
Your advocate helps you document the contact, identify what was shared, and organize a practical reporting checklist. You remain in control of securing your accounts through official providers; we never need your password, security code, or remote access.
Membership includes advocacy support for every scam category in this library. We assess the facts, explain the scope of help, and work through the available next steps with you. Recovery, refunds, and third-party decisions cannot be guaranteed; this is not insurance or formal legal representation.
See what membership includesYour checklist.
0 of 4 readyFor the official guidance, read FTC: recognizing phishing · FTC: fake emergencies and cloned voices · FTC: unexpected-package QR codes · FTC: tech support scams · FTC: requests to move money for safety.
Processes and deadlines depend on your location and the organizations involved. These guides are general information; check the rules that apply to your situation. Shieldman membership provides consumer advocacy; it does not guarantee a refund.
You can bring us
the messy part.
Your advocate helps organize the facts and work through the next steps.
Meet your backup