Skip to content

Smishing: SMS Phishing Attacks and How to Defend

What smishing is, why SMS phishing bypasses email defenses and works so well on phones, the common attack types, and how to test and defend against it.

Mark KissBy , Founder & CEOUpdated 7 min read

Phishing Simulation & Social Engineering TestingFrom $3,600Fixed scope, no hourly billing.

Get my fixed price

Smishing is phishing delivered by text message: SMS phishing. The name is a contraction of “SMS” and “phishing,” and the technique is exactly what it sounds like: a fraudulent text designed to make you tap a link, call a number, or hand over information. It has grown fast for a simple reason: people trust and act on texts far more readily than emails, and almost none of the defenses that guard the inbox exist on the messaging app. Our phishing statistics roundup has the sourced numbers.

The primary channel is the text message itself, sent to a personal or work phone. MITRE ATT&CK lists it under Phishing (T1660) in its Mobile matrix.

Smishing vs phishing vs vishing

Phishing Smishing Vishing
Channel Email SMS and other text messages Phone call
Typical lure Shared document, invoice, password reset Delivery, bank alert, expired password, “it’s the CEO” Help desk, bank fraud team, IT support
What stands in the way Mail gateway, link rewriting, sandboxing Almost nothing on most phones The person who answers
What the attacker wants Credentials, a session, a payment Credentials, an MFA code, a payment A password reset, an MFA approval, a payment

Why SMS works better for attackers than email

The channel does most of the work:

No filtering. Corporate email has years of layered defense. SMS arrives essentially raw: there is no enterprise spam filter, no link rewriting, no attachment sandbox sitting between the attacker and the screen. The message simply appears.

Higher trust and urgency. Texts are personal. They come from friends, family, delivery drivers, your bank’s fraud line. People tend to read a text soon after it arrives and act on it quickly, which is precisely the reflex an attacker wants.

The small screen hides the tells. The clues that expose a phishing email (the full sender address, the real URL on hover) are hidden or absent on a phone. A shortened or lookalike link is hard to inspect, and mobile browsers show little of the address. The medium removes the evidence.

Blurred work and personal boundaries. People read work and personal texts on the same device, in the same relaxed frame of mind, often while distracted. A work-targeted smish lands in that unguarded context.

The common smishing attacks

Most smishing falls into a few reliable patterns:

  • Package delivery: “Your parcel is held, confirm your details here.” Ubiquitous because almost everyone is expecting something, and the timing often lands.
  • Bank and payment fraud alerts: “Suspicious transaction detected, verify now.” Manufactured urgency around money, driving a tap before thought.
  • Account and MFA lures: a fake “verify your account” text, or one prompting for a code, aimed at harvesting credentials or a one-time passcode.
  • Boss / executive texts: “Hi, it’s the CEO, I’m in a meeting and need you to sort something urgently.” The SMS cousin of business email compromise, often opening with a request for gift cards or a transfer.
  • Government and tax: impersonating a tax authority or agency with a threat or a refund.

The through-line is a trusted sender, a manufactured reason to act now, and a link or number that leads somewhere the attacker controls.

Smishing in a corporate breach

It is tempting to file smishing under personal fraud, but it is a genuine enterprise threat. Employees use phones for work: email, MFA, chat, VPN. A smish that harvests corporate credentials or an MFA code through a convincing fake login page is a direct route into the organization, and it arrives on a device your email gateway never sees. The executive-impersonation variant targets finance staff for transfers exactly as email BEC does. Any assessment of your human attack surface that stops at email is missing the channel sitting in every employee’s pocket.

For advisers the same pretext arrives as a client asking to move money; our page on wire and distribution fraud testing for wealth managers covers how that is tested.

A real corporate smishing attack, step by step

Two companies published what happened when the same kind of campaign hit them in the summer of 2022.

  1. The text. Employees received legitimate-looking texts with a link. At Twilio the messages posed as IT and said a password had expired.
  2. The page. The link opened a fake sign-in page on a lookalike domain. At Cloudflare it asked for the username, password and one-time code.
  3. The outcome at Twilio. Some employees entered their credentials. The attackers used them to reach internal tools and the data of 209 customers (Twilio incident report).
  4. The outcome at Cloudflare. At least 76 employees received the texts and three entered their credentials. The attackers still could not log in, because Cloudflare’s FIDO2 hardware security keys are bound to the real site. No systems were compromised (Cloudflare’s account).

The same lure worked on people at both companies. The difference was the login control behind them.

How smishing is tested

Controlled SMS campaigns are part of social engineering penetration testing, run alongside email and voice for full coverage of the human attack surface. With authorization, testers send realistic smishing messages to agreed participants and measure who taps, who submits information on the landing page, and who reports it. Because it exercises a channel most organizations have never tested, a smishing assessment can show that staff who are cautious with email are less guarded over text, a gap you can only find by testing all three channels together.

What a smishing simulation includes

  • Written authorization and a participant list. The numbers to be texted are agreed in advance, including whether personal phones are in scope.
  • A realistic sender and lure, such as IT, HR or a delivery notice, agreed with your point of contact.
  • A landing page that records each attempt so it can be counted.
  • Metrics by department. Who tapped, who entered information, and who reported the text.
  • A report. What worked, where reporting failed, and what to change in training and login controls.

Our phishing and social engineering testing starts at $3,600, with SMS and voice scenarios as scoped options; the phishing and social engineering testing cost page shows the tiers.

How to defend against it

Smishing is countered with training, technical controls, and process:

  • Phishing-resistant MFA: FIDO2 keys and passkeys defeat the credential-and-code harvesting that most smishing aims for. The strongest single control.
  • Awareness that explicitly covers SMS: staff need to know texts are an attack channel, that delivery and bank alerts are prime lures, and that a link in a text deserves the same suspicion as one in an email. Most training never mentions it.
  • A verification habit: never act on an unexpected text through its link or number. Open the official app, or call the organization on a known number. For any “boss” request, verify out of band.
  • Reporting that includes texts: give employees an easy way to report a suspicious SMS, and make clear it is welcomed. You cannot respond to what no one reports. In the United States, the FTC also says to forward the message to 7726 (SPAM), which helps the carrier block similar texts.
  • Mobile device management: on corporate devices, MDM and mobile threat defense can block known malicious sites and add a filtering layer SMS otherwise lacks.

The short version

Smishing works because SMS is the channel with the least protection and the most trust: no enterprise filter, a small screen that hides the warning signs, and a reader primed to act fast. It is a real corporate threat, not merely personal fraud: employees carry work credentials and MFA on the same phones. The defenses are phishing-resistant MFA, awareness training that actually names SMS as an attack vector, an out-of-band verification habit, and easy reporting. And since staff cautious with email are often careless over text, testing all three channels together is the only way to see the whole picture.

Frequently asked questions

What is the difference between smishing and phishing?

Phishing is the general term and usually means email. Smishing is the same attack sent by text message, where no mail gateway stands in the way and the small screen hides the real link.

How do I report a smishing text?

At work, report it through your company’s security reporting channel and do not tap the link. In the United States, forward the text to 7726 (SPAM) so your carrier can act on it, and report it to the FTC at ReportFraud.ftc.gov.

Can MDM or mobile threat defense stop smishing?

Partly. On company-managed phones they can block known malicious sites after a tap, but they do nothing on unmanaged personal phones. Phishing-resistant MFA is the control that still holds when someone taps.

Want to know how your team responds across email, voice, and text? A multi-channel social engineering assessment tests all three together. Scope one here.

Mark Kiss

Written by

Mark Kiss, Founder & CEO

15+ years in the field. Focus: Offensive security & strategy. Part of the team that scopes, tests, and reports for our clients. Full profile →

All articlesRed Teaming

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online