What Is Pretexting? The Story Behind Every Scam

Publication Date

October 24, 2026

Category

Social Engineering Tactics

Reading Time

7 Min

Author Name

Shubh Arya

What Is Pretexting? The Story Behind Every Scam

<pre><pre><pre><pre>Pretexting is a social engineering technique in which an attacker invents a believable story, and often a false identity, to persuade someone to hand over information, access or money. The story is the attack. Everything else, the email, the call, the fake profile, is only the delivery.

Pretexting scams rely on a fabricated scenario and a false identity that earn the target's trust, usually reinforced by pressure such as authority or urgency.

That definition explains why pretexting is so hard to catch with technology. A pretext does not need a malicious link. It needs a character who seems to have a good reason to ask.

Pretexting vs phishing: story vs delivery

People often treat these as rivals. They are better seen as layers. Phishing, vishing and smishing describe how a message arrives. Pretexting describes what it says. A phishing email with a convincing invented backstory is both.

PretextingPhishing, vishing, smishing
What it isThe invented scenario and identityThe channel the message travels through
Needs a link or file?NoOften, but not always
What detects itA person asking whether the story holds upFilters, scanners, blocklists, plus people
Where you see itHelp desk calls,urgent requests from 'executives', 'vendors' changing detailsEmail, phone, text

The five parts of a pretext

Looking at real cases side by side, we found the same five parts in each. This is our own framework, not an industry standard, but it makes stories much easier to take apart.

PartWhat it isWhy it works
CharacterWho the attacker claims to bePeople help colleagues, bosses and officials
PropSomething that makes the character real: a photo, a voice, a name, a detail from social mediaA small true detail makes the rest feel true
ReasonThe believable situation behind the callA reason removes the need to ask why
SqueezePressure such as urgency, secrecy or authorityPressure shortens thinking time
AskThe one thing they wantOften small and reasonable on its own

Five cases, one framework

CaseCharacter and propReason and askOutcome
HP investigation, 2006Investigators using false pretences with phone companiesObtain board members' and journalists' call records to trace boardroom leaksExposed in late 2006. The US FTC later sued the contractors and a court barred them from pretexting for phone records
UAE bank, 2020A cloned voice of a company director the bank manager already knewA pending acquisition that needed money moved. Ask: authorise transfers of about 35 million dollarsTransfers approved. Some case details remain unpublished
Scattered Spider, 2023 onwardsCallers posing as IT staff, or as employees phoning the help desk, using details from social media and data leaksA locked account or an alert. Ask: a password reset, a one-time code, or a move of the employee's sign-in method to the caller's deviceDocumented by CISA as a recurring method
Ferrari, 2024A WhatsApp account and then a call imitating the CEO's voice and accentA supposed China-related deal needing a currency hedge transactionFailed. The executive asked for the title of a book the CEO had recently recommended, and the caller hung up
WPP, 2024A fake WhatsApp account using the CEO's public photo, then a Teams call with a voice clone and video footage of himSet up a new business venture. Ask: money and personal detailsFailed. WPP credited staff vigilance

Notice what is missing from the table: no malware, no exploit, no software flaw. Every case is a story told well, to someone who had no easy way to check it in the moment.

Also notice that the two cases that failed were stopped by people who did something small and slightly awkward. At Ferrari, the executive asked a question the fake could not answer. At WPP, the company credited staff vigilance.

The 30 second story audit

When a request is unexpected, run it through five questions before acting. None needs technical skill.

QuestionWhat you are checking
1. Who exactly is asking, and how do I know?The character. Can I confirm the identity another way?
2. What makes them seem real?The prop. Anything a stranger could find online proves nothing.
3. Why now, and why me?The reason. Would this normally come to me, by this route?
4. What happens if I wait an hour?The squeeze. Real deadlines survive a phone call back.
5. What exactly do they want?The ask. Is it money, a code, access or secrecy?

If two answers are weak, stop and verify through a channel you started yourself, such as a number from your own records. This is the single move that defeats most pretexts, because the attacker controls the story but not your phone book.

What organisations can change

Treat the help desk as a front line. CISA describes attackers phoning IT staff while posing as employees, and asking for password resets or a change of the employee's sign-in method. A fixed verification routine that does not rely on easily found personal details closes much of that gap.

Shrink the prop supply. A review of the digital footprints of hundreds of executives found that around 60 percent of an individual's exposure could be found with an ordinary web search. Reviewing what staff and leaders publish removes material from attackers.

Make verification polite and normal. People skip checks that feel rude. A written rule that everyone verifies, including requests from the CEO, takes the awkwardness out.

Practise with realistic stories, not just links. Simulations that tell a believable story across email, phone and messaging are closer to the real thing. SimuPhish builds scenarios across those channels so teams can rehearse the pause.

See SimuPhish in action

FAQs