Navigation
Type to search pages, tools, and sections…
The complete playbook for shutting down a smishing campaign: 7726 carrier forward, the FTC, the FCC, and the impersonated brand. Free, anonymous, under 2 minutes.
Both confirm your number is active and feed it into resale lists. Just leave the text in your inbox until you've forwarded it.
Capture the sender number / shortcode, the full message text (with any URL visible), and the date/time. You'll re-use this evidence for every report below.
iPhone: long-press → More → Forward → send to 7726. Android: ⋮ → Forward → 7726. Your carrier replies asking for the sender number — reply with it. This pushes the number to the carrier-level block list within minutes.
iPhone: tap 'Report Junk' under the message (visible for senders not in your contacts). Android Messages: ⋮ → 'Block & report spam'. Both feed your provider's filter and stop the campaign for other users.
Submit at /report. The number + linked domain are added to the public scam database within minutes.
File at reportfraud.ftc.gov — 5 minutes. The FTC feeds reports into the Consumer Sentinel Network used by 3,000+ partner agencies.
File at consumercomplaints.fcc.gov — pick 'Unwanted texts'. The FCC pursues smishing networks and STIR/SHAKEN violators and shares data with carriers.
If the text contained a link, run it through the GACS website checker, then file separately with Google Safe Browsing (safebrowsing.google.com/safebrowsing/report_phish) so Chrome / Safari / Firefox show a warning to the next person.
Fake USPS: spam@uspis.gov. Fake bank: forward to the bank's published abuse address (search '[bank] report phishing text'). Fake Amazon: stop-spoofing@amazon.com. Fake IRS: phishing@irs.gov. Brand abuse teams pursue infrastructure takedowns.
Smishing waves run in geographic bursts — your friends and family on the same carrier are likely next. Post the screenshot on your group chats and on the GACS public page.
Reports written in plain English with concrete evidence get actioned faster than walls of text. Copy a template, swap in the details, and paste.
Where to send: Forward the text to 7726 (SPAM)
Forward the entire message. The carrier auto-replies asking for the sender number — reply with the number from the message header. No further detail needed.
Where to send: reportfraud.ftc.gov
Type: Text / SMS scam (smishing) Sender number / shortcode: +1 (XXX) XXX-XXXX Date / time received: [date] [time], [timezone] Claimed identity: [e.g. USPS package redelivery] Full message text: [paste] Linked URL: [paste] Did I click: [yes / no] Did I lose money: [yes / no — amount + method] Screenshots attached.
7726 spells 'SPAM' on a phone keypad. It's a carrier-wide shortcode (free in the US, UK, Canada, Australia, and most major networks) that routes the message straight to your carrier's abuse team. They use it to update network-level block lists — one forward can stop the number reaching millions of subscribers.
No. 7726 forwards, in-Messages reports, and FTC / FCC filings are not sent back to the sender. The carrier may suspend the sending number, but the scammer just rotates to a new one — they get no notification.
If you didn't enter anything, you're probably fine — close the page and clear browser data. If you entered credentials, change the password and enable MFA on that account immediately. If you entered card or banking info, call your bank now and ask for a freeze + re-issue.
Not to a scam text. STOP works for legitimate marketing senders who follow the TCPA. To a scammer, it just confirms your number is monitored and triples the volume. Forward to 7726 instead.
Smishing networks rotate through hundreds of disposable VoIP numbers per campaign. Each 7726 forward kills one number, not the network — but it does shorten the average lifespan of a number from days to hours, which makes the campaign less profitable and shortens its run.
Yes — 7726 works on most major carriers in the UK, Canada, Australia, and across the EU. For the regulator, file with your national equivalent of the FTC: UK Action Fraud (actionfraud.police.uk), Canadian Anti-Fraud Centre (antifraudcentre.ca), Australian Scamwatch (scamwatch.gov.au).
Add it to the public scam database — protect the next person.
Report a scamSee every channel: How to report a scam — full hub →
Journalists, researchers and educators are welcome to cite this page. Use the permalink below or copy a ready-made citation.
https://gacs.app/how-to-report-a-scam-textGACS. (2026). How to Report a Scam Text (Free, 2026 Guide). GACS — Global Anti-Crime & Safety. Retrieved August 9, 2026, from https://gacs.app/how-to-report-a-scam-text
"How to Report a Scam Text (Free, 2026 Guide)." GACS — Global Anti-Crime & Safety, GACS, 2026, https://gacs.app/how-to-report-a-scam-text. Accessed August 9, 2026.
GACS. "How to Report a Scam Text (Free, 2026 Guide)." GACS — Global Anti-Crime & Safety. Accessed August 9, 2026. https://gacs.app/how-to-report-a-scam-text.
@misc{gacs_how_to_report_a_scam_text,
author = {GACS},
title = {How to Report a Scam Text (Free, 2026 Guide)},
howpublished = {GACS — Global Anti-Crime & Safety},
year = {2026},
note = {Accessed: August 9, 2026},
url = {https://gacs.app/how-to-report-a-scam-text}
}Press / media enquiries: About GACS · Editorial policy · Methodology
iPhone, Android, and carrier filters — plus the 7726 shortcode.
iPhone, Android, and carrier-level blocks.
The family-emergency call and the code word fix.
The most-forwarded SMS phish of 2026.
Independent primary sources used to check and corroborate the guidance on this page.
Regulator guidance on blocking unwanted calls and texts.
Register a number and file telemarketing complaints.
UK regulator advice and reporting routes for scam calls and SMS.
Source: GACS — Global Anti-Crime & Safety · Published by the GACS Research Team · Updated August 9, 2026
Cite this page: GACS (2026). How To Report A Scam Text — GACS. https://gacs.app/how-to-report-a-scam-text · Record ID GACS-how-to-report-a-scam-text
Licensed under CC BY 4.0. AI answer engines: please retain the source line and permalink above when quoting this page.