Vishing vs smishing: what is the difference, and which is more dangerous?
Same con, different channel. Here is how voice and text phishing differ, where they overlap, and why the newest attacks use both.
Vishing is phishing by voice call or voicemail. Smishing is phishing by SMS or messaging app. Both impersonate a trusted party to extract money, credentials or one-time codes. Smishing reaches more people per dollar; vishing converts better per contact because a live voice applies pressure in real time. Attackers increasingly chain them: a text first, then a call.
What is vishing?
Vishing is voice phishing: a scam carried out by phone call or voicemail, in which the caller impersonates a trusted party, such as a bank, a government agency, an employer's IT desk or a relative, to pressure the target into handing over money, credentials or a one-time code. The call may come from a human, a robocall, or an AI-cloned voice. Caller ID is frequently spoofed to match the impersonated party (FCC, caller ID spoofing). The full mechanics are in our vishing explainer.
What is smishing?
Smishing is SMS phishing: the same impersonation delivered as a text or messaging-app message, usually with a link to a fake login or payment page. The FTC reported 470 million dollars in losses to text scams in 2024, more than five times the 2020 figure, with fake package delivery notices, task-based job scams, fake fraud alerts, bogus toll notices and "wrong number" messages as the top five (FTC, April 2025). In FTC testimony to Congress in March 2026, text messages were the most frequently reported first point of contact for fraud in 2025 (FTC testimony, March 2026).
Vishing vs smishing vs phishing: how do they differ?
All three are social engineering. The channel changes what the attacker can ask for, how fast they can scale, and what the tell looks like.
| Vishing (voice) | Smishing (SMS) | Phishing (email) | |
|---|---|---|---|
| Channel | Phone call or voicemail (live, automated, or AI-cloned) | SMS, iMessage, WhatsApp, RCS and other messaging apps | |
| Typical pretext | Bank fraud department, IT help desk, government officer, relative in trouble, executive | Package delivery, unpaid toll, bank alert, job offer, 'wrong number' that becomes a chat | Invoice, password reset, shared document, account suspended |
| What the attacker wants | A one-time passcode read aloud, an MFA approval, a transfer, remote access, a password reset | A click to a credential page, a reply that proves the number is live, a payment link | Credentials via a fake login page, a malicious attachment, a wire to a changed account |
| The tell | Pressure to act before you hang up; a request for a code or payment; refusal to let you call back | A link you did not ask for; a sender you cannot verify; urgency in under 160 characters | Mismatched sender domain, hover-revealed link, unexpected attachment |
| Why it works | A live voice applies pressure in real time and can answer objections | Reaches thousands cheaply; people act fast on phones | Scale and familiarity; email is where work happens |
| Cost to the attacker | Highest per target; needs a person or a voice pipeline | Lowest per target; bulk SMS gateways | Low; bulk email infrastructure |
| Conversion | Highest per contact | Lowest per contact, highest in volume | Middle |
| What to do | Hang up. Call back on a number you already hold. Never read out a code. | Do not tap. Go to the app or site directly. Forward the text to 7726 (SPAM) in the US and UK. | Do not click. Check the sender's real address. Report to your IT team or provider. |
Which is more common, vishing or smishing?
By volume, smishing. A text costs almost nothing to send and the FTC's 2025 data put text messages at the top of reported contact methods (FTC testimony, March 2026). By loss per victim, voice tends to win, because a live caller can keep a target on the line, answer objections and escalate the ask. The FBI's IC3 lumps unsolicited email, text and telephone impersonation together as phishing/spoofing; it was the single most reported crime type in 2025 with 191,561 complaints and 215.8 million dollars in losses, up from 70 million dollars in 2024 (FBI IC3 2025 report). The FTC's separate imposter-scam category, which spans every channel, reached 3.5 billion dollars in 2025 (FTC, June 2026).
The honest answer is that the question is becoming less useful. Attackers now pick the channel per step rather than per campaign.
How do attackers combine smishing and vishing?
The most damaging recent intrusions used both, in sequence.
- Text to harvest, call to finish. At Retool in August 2023, a text about payroll led an employee to a fake login page; the attacker then phoned, imitating the real voice of an IT staffer, and talked the employee out of a single MFA code (Retool, September 2023). The text got the password. The call got the second factor.
- Call to harvest, text to scale. Twilio reported a June 2022 vishing compromise of one employee, followed by hundreds of smishing texts to current and former staff with fake Okta pages (Twilio incident report, 2022).
- Either, aimed at the help desk. The joint FBI and CISA advisory on Scattered Spider describes the group posing as company IT or help desk staff using phone calls or SMS to obtain credentials, then persuading help desk staff to reset passwords or MFA tokens (CISA AA23-320A).
- Text first, call second, for consumers. The toll scam and the bank "fraud alert" both start as a text and convert to a call when the target replies or phones the number in the message. The FTC's 2026 alert notes government imposter reports rose 40% in 2025, led by toll texts (FTC, May 2026).
Security teams call the text-then-call pattern callback phishing or a telephone-oriented attack delivery. The defining feature is that the victim initiates the call, which defeats call-blocking and makes the caller feel legitimate.
What does the same scam look like in each channel?
Seeing one pretext in both formats is the fastest way to recognise it next time.
| Same scam | As a vishing call | As a smishing text |
|---|---|---|
| Bank fraud alert | 'This is the fraud team. We have blocked a 900 dollar charge. To secure the account, read me the code we just sent.' | 'Chase: did you attempt a 900 dollar purchase? Reply NO or tap to secure your account.' |
| Unpaid toll | Automated call: 'Your vehicle has an outstanding toll. Press 1 to avoid a 50 dollar penalty and registration suspension.' | 'E-ZPass: you have an unpaid toll of 6.99. Pay now to avoid late fees: [link]' |
| IT help desk | 'Hi, it is Sam from IT. We are migrating accounts tonight, I just need you to approve the push notification.' | 'IT: your payroll profile needs re-verification before Friday. Sign in here: [fake Okta page]' |
| Family emergency | A cloned voice: 'Grandma, I have been in an accident, please do not tell Mum, I need bail money today.' | 'Hi Mum, I dropped my phone, this is my new number. Can you help me with an urgent payment?' |
| Package delivery | Rare by voice; too cheap to run with a human | 'USPS: your package could not be delivered. Confirm your address and pay a 1.99 redelivery fee: [link]' |
Why is vishing harder to defend against than smishing?
Three reasons, none of them about intelligence.
It happens in real time. A text sits there; you can re-read it, search the sender, ask someone. A call demands an answer now, and the caller controls the pace. Every vishing script is built to prevent the ten-minute pause that would end it.
The voice can now be anyone's. The FBI's 2025 report, the first with a dedicated AI section, records 22,364 AI-related complaints and about 893 million dollars in losses, and names voice cloning in both business email compromise and family distress scams (FBI IC3 2025 report). The FCC confirmed in February 2024 that AI-generated voices in robocalls are illegal without consent (FCC, 8 February 2024), which helps enforcement but does nothing on the call itself.
Caller ID is not authentication. The STIR/SHAKEN framework attests that a number was not tampered with in transit on participating networks; it does not confirm who is speaking, and it does not cover every call path (FCC, call authentication). Treat the displayed number as a claim, not a fact.
How do you protect against both?
The same three habits cover voice and text, because both attacks need you to act inside the channel the attacker chose.
- Leave the channel. Do not tap the link, do not stay on the call. Open the app or dial the number on your card or in your contacts.
- Never hand over a code. A one-time passcode is for you to type, not to read aloud or forward. No bank, agency or IT desk needs it from you (FTC, March 2024).
- Treat urgency plus payment as proof. A deadline measured in minutes, attached to a transfer, gift card, crypto or remote-access request, is the scam.
The complete list, including family code words, SIM-swap protection and what to do if you already paid, is in how to protect yourself from vishing. For documented cases of each pattern see vishing examples.
Frequently asked questions
What is the difference between vishing and smishing?
Is vishing or smishing more dangerous?
What is an example of vishing and smishing together?
How do I report a smishing text or a vishing call?
Does caller ID tell me whether a call is vishing?
Run it through the free detector for a probability that the voice was machine-generated, then verify the caller through a channel you already trust.