0Pricing
Cloud & IT Cert Prep · Lesson

Vishing, Smishing, and Pretexting

Explore voice-based (vishing) and SMS-based (smishing) attacks, and understand how pretexting creates believable false scenarios to manipulate victims.

Vishing, Smishing, and Pretexting is a free Cloud & IT Cert Prep lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Cloud & IT Cert Prep learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Social Engineering Beyond Email

While phishing dominates headlines, attackers use multiple communication channels to manipulate victims. Vishing uses voice calls, smishing uses SMS text messages, and pretexting is the practice of constructing a believable false scenario (pretext) to justify why the victim should comply with a request. These attacks succeed not because victims are ignorant, but because they exploit fundamental human instincts: trust in authority, desire to be helpful, and the tendency to follow instructions when under pressure.

Vishing: Voice-Based Phishing

Vishing (voice phishing) uses phone calls to manipulate victims. Common pretexts include impersonating an IRS agent threatening arrest for unpaid taxes, a bank fraud department warning of suspicious transactions, tech support claiming to have detected a virus, or a government benefits office requiring verification. Attackers use caller ID spoofing to display the phone number of a legitimate organization. Robocall vishing campaigns operate at scale, then connect interested victims to live operators. The real-time nature of voice calls creates pressure that makes critical thinking difficult.

# Common vishing pretexts:
# 'This is the IRS. You owe back taxes; pay now to avoid arrest'
# 'Microsoft Support detected a virus on your computer'
# 'Your bank account is compromised; verify your PIN to secure it'
# 'Social Security Administration: your number has been suspended'
#
# Red flags:
# - Caller ID can be spoofed (not proof of legitimacy)
# - Legitimate orgs do NOT call demanding immediate payment or credentials
# - Urgency + threats of arrest/account closure are common manipulation

Smishing: SMS-Based Phishing

Smishing (SMS phishing) delivers phishing lures via text message. Common smishing messages impersonate package delivery services (FedEx, UPS, USPS) with fake tracking notifications containing malicious links, banks warning of suspicious charges, or mobile carrier notifications about account problems. Smishing URLs often use URL shorteners or look-alike domains. Mobile users are arguably more vulnerable than desktop users because smaller screens make URL inspection harder, and mobile browsers often hide the full address. SMS also carries inherent trust — users tend to act more quickly on text messages than emails.

# Smishing message examples:
# 'USPS: Your package is held. Confirm your address: bit.ly/xYz123'
# '[BANK]: Suspicious charge of $499. Verify: yourbank-security.com'
# 'Free iPhone 16 winner! Claim now: apple-promo-2026.net/claim'
#
# Technical defenses:
# - Mobile threat defense (MTD) solutions scan SMS links
# - DMARC does NOT protect SMS (different channel)
# - Carrier-level SMS filtering for known smishing patterns
# - User training: never click SMS links for financial matters

Pretexting: The Art of False Scenarios

Pretexting is the fabrication of a false but believable scenario that creates context for a social engineering request. Without a convincing pretext, requests for sensitive information or unusual actions would immediately raise suspicion. A pretexting attacker might impersonate a new IT contractor who needs help accessing systems, an auditor requiring access to financial records, or a vendor delivery person who needs to be 'buzzed in.' The pretext does not have to be elaborate — it just needs to be plausible enough that the target does not stop to verify before complying.

# Pretexting example scenarios:
# IT helpdesk: 'I'm the new IT contractor and need your temp
#   password while your account is being migrated.'
# Vendor: 'I'm from the HVAC company doing scheduled maintenance.
#   I need access to the server room.'
# Executive assistant: 'My CEO needs the quarterly report on Slack
#   right now; please send it directly to him at this number.'
#
# All rely on a believable false role to justify an unusual request

Psychology Behind Social Engineering

Robert Cialdini's principles of influence explain why social engineering works. Authority — people comply with those perceived as authority figures (CEO, IRS, police). Urgency/Scarcity — time pressure prevents careful evaluation ('Act in the next 10 minutes'). Social proof — people do what others are doing. Liking — people comply with those they trust or find agreeable. Reciprocity — people feel obligated to return favors. Commitment — once a small commitment is made, people tend to follow through on larger ones. Understanding these principles helps security awareness trainers craft more effective counter-messaging.

Caller ID Spoofing Technology

Modern VoIP technology makes caller ID spoofing trivial. Services like SpoofCard, Twilio, and various VoIP APIs allow anyone to set the displayed caller ID to any number before placing a call. Attackers routinely spoof bank customer service lines, government agency numbers, or the victim's own number (neighbor spoofing). The STIR/SHAKEN framework (Secure Telephony Identity Revisited / Signature-based Handling of Asserted information using toKENs) was mandated in the US to cryptographically authenticate caller ID, but adoption is incomplete. Never trust caller ID alone to verify identity.

Vishing Against Help Desks

Help desk staff are prime targets for vishing because their job is to help users — creating a natural tension with security procedures. A typical attack: the attacker calls posing as a senior employee who urgently needs their account reset because they are locked out before an important meeting. The pressure of authority + urgency can cause a well-intentioned help desk agent to skip verification steps. The celebrated 2020 Twitter hack began with vishing attacks on Twitter employees that gained access to internal tools. Help desks need strict identity verification procedures that cannot be waived regardless of urgency.

# Help desk identity verification procedure:
# 1. Employee initiates account reset via SELF-SERVICE portal first
# 2. If phone call required: verify with manager callback (not to number provided by caller)
# 3. Out-of-band verification: employee must present to IT desk in person for high-privilege resets
# 4. Automated OTP sent to MANAGER for approval before reset
# 5. Log all password resets and alert SIEM on after-hours resets
# NEVER bypass verification for urgency

SIM Swapping Attacks

A SIM swap attack combines vishing and social engineering against a mobile carrier's customer support. The attacker calls the carrier pretending to be the victim, provides answers to identity verification questions (sourced from data breaches or social media), and convinces the agent to transfer the victim's phone number to a SIM card controlled by the attacker. Once the number is hijacked, all SMS-based MFA codes go to the attacker, enabling account takeover of email, banking, and cryptocurrency accounts. SIM swapping has been used to steal millions in cryptocurrency.

# SIM swap defense measures:
# User-side:
#   - Set a carrier-level PIN/passcode (separate from account password)
#   - Use app-based TOTP instead of SMS-based MFA where possible
#   - Use hardware security keys (FIDO2) — not tied to phone number
#   - Freeze/lock your SIM with carrier ('number lock' or 'port freeze')

# Organization-side:
#   - Never use SMS OTP for high-value account recovery
#   - Use FIDO2 security keys for employee accounts

Detecting and Investigating Vishing/Smishing

Detecting social engineering attacks requires combining employee reporting with technical logging. Every employee should know how to report a suspicious call or text — ideally a one-click button in email or a dedicated email alias (phishing@company.com). Technical indicators include call logs showing inbound calls from spoofed numbers, SIEM alerts on help desk password resets preceded by incoming calls, and out-of-hours account access changes. After an incident, phone records and SMS logs are key forensic artifacts alongside email logs and authentication events.

# Reporting and detection workflow:
# 1. Employee receives suspicious call/text
# 2. Reports via: phishing@company.com or helpdesk ticket
# 3. SOC reviews: was any account action taken?
#    - Check AD logs for password changes/unlocks
#    - Check SIEM for account access changes post-call
# 4. If social engineering succeeded:
#    - Immediately reset affected credentials
#    - Review all actions taken by the compromised account
#    - Alert affected systems and downstream services

Defending Against Pretexting

Defending against pretexting requires establishing verification procedures that employees follow consistently regardless of the pressure they feel. Key policies include: always verify identity through a separate, established channel before fulfilling unusual requests; establish a code word system for executive communications; train employees that authority figures within the organization will not be offended by requests for verification; and create a security-positive culture where following procedures is rewarded even when it causes minor inconvenience. Unannounced social engineering tests measure whether training is effective in practice.

Comparing Phishing Channels

For the Security+ exam, clearly distinguish between the phishing channels. Phishing is via email. Vishing is via voice/phone. Smishing is via SMS text. Pharming redirects DNS without requiring a click. All share the same goal — manipulating the victim into revealing credentials, transferring money, or installing malware — but the delivery mechanism and countermeasures differ. Email has technical defenses (SPF/DKIM/DMARC/sandboxing); voice and SMS have far fewer technical controls, making user awareness training even more critical for those channels.

Quick Check

Test your understanding of CompTIA Security+ (SY0-701) concepts from this lesson.

Lesson Recap

In this lesson you learned: vishing uses phone calls with caller ID spoofing to impersonate authority figures and extract credentials or actions, smishing delivers phishing lures via SMS where mobile users have reduced URL visibility, and pretexting creates believable false scenarios that justify unusual requests — defended with strict identity verification procedures, out-of-band confirmation, and employee training. Next up we explore physical social engineering through tailgating and baiting.

Frequently asked questions

Is the “Vishing, Smishing, and Pretexting” lesson free?

Yes — the full text of “Vishing, Smishing, and Pretexting” is free to read here on the web, and the Cloud & IT Cert Prep course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Cloud & IT Cert Prep course, upgrade to CoddyKit PRO.

What will I learn in “Vishing, Smishing, and Pretexting”?

Explore voice-based (vishing) and SMS-based (smishing) attacks, and understand how pretexting creates believable false scenarios to manipulate victims. You practise Cloud & IT Cert Prep with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Cloud & IT Cert Prep?

No prior experience is required. Cloud & IT Cert Prep on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Vishing, Smishing, and Pretexting” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Cloud & IT Cert Prep lesson?

Yes. Every Cloud & IT Cert Prep lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Phishing, Spear Phishing, and Whaling
  2. Vishing, Smishing, and Pretexting
  3. Physical Social Engineering: Tailgating and Baiting
  4. Security Awareness Training and Anti-Phishing Controls
← Back to Cloud & IT Cert Prep