pretexting

Pretexting: How Attackers Use a Fake Story to Get Access

Huzaifa.Hamza Article 9 min read

The phone rings. The caller says he is from the IT helpdesk, knows your name and your manager’s name, and needs to fix a problem with your mailbox before the end of the day. All he needs is the code that just arrived on your phone.

There is no malware here and no hacking tool. There is only a believable story. That is pretexting, and it is one of the oldest and most effective ways attackers get access to data, money, and systems.

This guide explains what pretexting is, how a pretexting attack works, the most common scenarios, and how to train your staff to verify before they trust.

What Is Pretexting?

Pretexting is a social engineering attack in which the attacker invents a situation, the pretext, to persuade a victim to share information or take an action they normally would not. The story gives the request a reason to exist.

According to Wikipedia’s entry on pretexting, the term was coined by the FBI in 1974. In the UK the same practice is often called "blagging."

Pretexting vs. Phishing

The two overlap, but they are not the same thing.

Phishing is usually a message sent to many people, hoping some will click.

Pretexting is built around a story and a role, often for one target or a small group.

Phishing relies on a link or an attachment.

Pretexting often relies on conversation: a call, a chat, or a long email thread.

Many phishing emails use a pretext. Many pretexting attacks never use a link at all.

For a broader look at how these tactics combine, see our article on social engineering attacks that worked in the real world.

Why Pretexting Works

A good pretext uses normal human instincts against the victim.

Authority: the caller claims to be a manager, auditor, or official.

Urgency: there is a deadline, a locked account, or an angry executive.

Helpfulness: most employees want to solve problems quickly.

Familiarity: the attacker knows names, projects, and internal terms.

How a Pretexting Attack Works

Most pretexting attacks follow the same four stages.

Research. The attacker studies the target using LinkedIn, the company website, press releases, and social media. They learn names, roles, suppliers, and how the organization talks.

Build the story. They pick a role that has a natural reason to ask for something: IT support, a supplier, an auditor, a new colleague, or a bank.

Establish trust. They open with small, harmless requests. They drop real names and details to sound like an insider.

Make the ask. Once trust exists, they request the real prize: a password, an MFA code, a payment, a file, or physical access.

The best attacks of this kind feel completely routine to the victim. That is the point.

Common Pretexting Scenarios

These are the stories attackers use most often against organizations. Each one gives the request a reason that sounds normal.

The Fake IT Helpdesk

The attacker calls or messages an employee, claims to be IT support, and asks for a password or an MFA code to "fix" an issue. A reverse version also exists: the attacker calls the real helpdesk pretending to be an employee who is locked out.

The Vendor or Invoice Change

A "supplier" emails finance to say their bank details have changed. The next invoice should go to a new account. This scenario sits at the heart of business email compromise, where a single fake email can redirect a large payment.

The Executive Impersonation

A message appears to come from the CEO, who is "in a meeting" and needs an urgent transfer or a set of gift cards. The pressure of seniority stops people from asking questions.

The Bank or Government Caller

The victim gets a call from someone claiming to be their bank, a telecom provider, or a government agency. The caller asks them to "confirm" card details or a one-time password. This voice-based version is often called vishing.

The New Colleague or Contractor

Someone claims to be a new hire, a consultant, or a delivery driver. They ask for building access, Wi-Fi details, or help logging in "just this once."

Real-World Case: The HP Scandal

One of the best known cases came from inside a company. In 2006, Hewlett-Packard wanted to find the source of boardroom leaks to the press.

According to the Wikipedia account of the HP spying scandal:

Investigators working for HP impersonated board members and journalists to obtain their phone records.

HP’s chairwoman, Patricia Dunn, resigned as chair in September 2006, as did the company’s general counsel.

Criminal charges followed in California, and one investigator was later sentenced in federal court.

The case partly led to the US Telephone Records and Privacy Protection Act of 2006, which specifically prohibits pretexting for phone records.

The lesson for defenders is simple. If trained investigators could get phone records just by calling with a story, your helpdesk can be fooled the same way.

Where Attackers Find the Details for Their Story

A pretext is only as convincing as the details behind it. Most of those details are public or easy to get.

Professional profiles: job titles, reporting lines, and recent hires

Company websites and press releases: supplier names, new projects, office locations

Social media: travel plans, events, and photos of badges or desks

Out-of-office replies: who is away, for how long, and who covers for them

Earlier breaches: leaked email addresses and phone numbers

Reduce What You Give Away

Review what staff publish about internal systems and processes.

Keep out-of-office messages short and avoid naming backups by role.

Remove direct phone numbers for finance and IT from public pages where possible.

Remind executives and their assistants that their calendars are valuable to attackers.

Warning Signs of Pretexting

Train staff to pause when they notice any of these.

An unexpected request for a password, MFA code, or one-time password

Pressure to act quickly or skip the normal process

A request to keep the conversation private

A change to bank details, payroll, or delivery address

A caller who refuses a call-back or offers their own number to call

Details that are almost right: a slightly wrong title, a new email domain

Flattery or emotional pressure, such as "you will get me fired if this fails"

How to Stop Pretexting

You cannot stop attackers from making up stories, and you cannot expect every employee to spot every lie. You can make sure stories alone are never enough to get access.

Use Call-Back Verification

End the call or chat politely.

Find the contact details yourself, from the company directory or a known invoice, not from the message.

Call back and confirm the request with the real person.

Build Process Controls for Payments

Require two people to approve any change to supplier bank details.

Hold new payee details for a short waiting period before the first payment.

Never accept bank detail changes by email alone.

Lock Down the Helpdesk

Verify callers with something an attacker cannot easily find online.

Never reset MFA based only on a phone call.

Log and review all password and MFA resets.

Train Staff With Realistic Simulations

People learn to resist a convincing story by practicing it. Simulated vishing calls and fake supplier emails show staff what a convincing story feels like, without real damage. Review results together, praise people who verified, and coach those who did not.

What to Do If You Fell for a Pretexting Attack

Speed matters more than embarrassment.

Report it immediately to your security team or manager.

Change the password you shared and revoke active sessions.

Call your bank at once if a payment was made. Fast recalls sometimes succeed.

Write down details: the number, the name used, the time, and what was said.

Warn colleagues if the attacker may try the same story on them.

A no-blame reporting culture makes this step much faster. People who fear punishment stay quiet, and attackers gain time.

Conclusion

Pretexting works because it targets trust, not technology. The attacker studies you, builds a role, and makes the request feel normal.

The defense is just as human. Teach people the warning signs, give them a simple rule to verify through a known channel, and add process controls so that no single story can move money or unlock an account.

Train Your Team to Spot Pretexting With PHISH-X

PHISH-X runs realistic simulations across email, SMS, and voice, including vishing scenarios built around pretexting stories. When someone falls for a test, they get targeted micro-training straight away, and repeat failures drop over time.

See how PHISH-X works or contact the CyberX team to plan your first campaign. Learn more about our awareness approach on the CyberX home page.

Frequently Asked Questions

What is pretexting in simple terms?

Pretexting is when an attacker invents a believable story to trick someone into sharing information or taking an action, such as a fake IT call asking for a password.

What is an example of pretexting?

A common example is a fake supplier email asking finance to send the next payment to a new bank account. Another is a caller posing as IT support who asks for an MFA code.

How is pretexting different from phishing?

Phishing usually sends a mass message with a link. Pretexting is built around a role and a story, often through a call or conversation, and may not use a link at all.

Is pretexting illegal?

Pretexting to obtain protected records is illegal in many countries. In the US, the Telephone Records and Privacy Protection Act of 2006 specifically prohibits pretexting for phone records.

How can companies prevent pretexting?

Use call-back verification through known contacts, require dual approval for payment changes, verify helpdesk callers properly, and train staff with realistic simulations.

AwareX

Train your staff to stop cyber attacks

  • Ready-made Arabic awareness content
  • Realistic phishing simulations
  • Reports ready for NCA requirements
Book a demo

Talk to the CyberX team

Tell us about your organization and we will suggest the right awareness program within one business day.

    By clicking submit below, you consent to allow CyberX to store and process the personal information submitted above to provide you the content requested.
    Languages: