What Is Spear Phishing? Examples and Prevention

Spear phishing is a phishing attack aimed at one specific person, or a small group inside one organization, and built from research about that target. The message is written to look like it comes from someone the recipient already trusts — a manager, a regular supplier, the IT help desk — and it asks for one thing: a password typed into a fake login page, an attachment opened, a payment sent, or records handed over. Because the details are researched, the usual tells of a mass scam email — a strange sender, a generic greeting, sloppy writing — are missing.

That research is the whole method. Ordinary phishing accepts that almost everyone will ignore it; spear phishing picks its recipient first, learns how that person works, and spends its effort on making one message believable. Below: how an attack is assembled, three worked examples, the red flags that still show, defenses for individuals and businesses, and what to do in the first hour if you clicked.

How a spear phishing attack is built, step by step

Step 1 — Picking the target. Attackers choose people whose access or authority is worth having: finance staff who can move money, IT administrators, executives and their assistants, HR staff holding employee records. Job adverts and LinkedIn profiles reveal who holds which role.

Step 2 — Research. The attacker studies the target using public sources: company websites, press releases, social media posts, and data left over from earlier breaches. They learn the manager’s name, current projects, regular suppliers, the software the company uses, and when the target is travelling. None of this requires hacking. It requires patience.

Step 3 — Building the lure. The message is written in the voice of a trusted person and references real details gathered in step 2. The sender may be spoofed, sent from a lookalike domain registered for the purpose — one letter different from the real one — or, in the strongest variant, sent from a genuinely compromised mailbox, sometimes dropped into an existing email thread so it inherits a real conversation’s context.

Step 4 — The payload. Three forms cover most attacks. A link leads to a credential-harvesting page that copies a real login screen and records whatever is typed. An attachment — an invoice or spreadsheet — installs malware when opened. Or there is no payload at all: a pure conversation that talks the target into a payment or data handover — business email compromise.

Step 5 — Follow-through. Stolen credentials are used within minutes or hours: inbox rules are created to hide replies, and the victim’s real account starts sending further lures. Money is moved through intermediary accounts the same day, and malware spreads from the first machine. This speed is why the first hour after a click matters so much.

How it differs from ordinary phishing

Ordinary phishing is a single message sent to thousands of people, written generically, and relying on a tiny fraction of recipients responding. Spear phishing is researched and written for its one recipient, which is why it succeeds far more often and why “look for bad grammar” is such poor protection against it. When the chosen target is a senior executive, the same technique is often called whaling — a different label, not a different method.

Three spear phishing examples

The scenarios below are invented, with fictional names, and assembled from techniques described in CISA’s phishing guidance and FBI IC3 reporting on business email compromise.

Example 1: The CEO wire request (business email compromise)

A finance officer — call her Priya — gets an email at 4:40 p.m. on a Friday, apparently from her chief executive:

“Priya — we sign the Hartwell acquisition on Monday. I need the $86,500 closing payment sent today to the account below. Keep this between us until the announcement.”

A trade article had mentioned the acquisition talks, so the reference feels inside. The sender domain has one letter swapped. The request carries a deadline, a reason for secrecy, and a reason it cannot go through normal channels — the three ingredients this scam runs on. The FBI’s Internet Crime Complaint Center (IC3) has put exposed losses from business email compromise at more than $50 billion across a decade of reporting, most of it moved by messages no more technical than this one.

Example 2: The IT password reset

An employee receives a message from “IT Service Desk” two days before a real, company-announced systems migration:

“As part of Thursday’s migration, your single sign-on password expires in 2 hours. Sign in here to keep your account active.”

The message names the employee’s actual manager and the actual software being migrated — both lifted from company announcements. The link opens a page that copies the real company login screen, hosted on a domain differing by one character. The employee enters a password and approves the sign-in prompt; the attacker, watching in real time, is inside within minutes.

Example 3: The supplier bank-detail change

A message arrives in accounts payable from a regular supplier’s usual contact address — the supplier’s mailbox has been quietly compromised:

“Please note our bank has changed. Update our remittance details to the account below before paying invoice 4471, attached.”

The invoice number is real, copied from the hijacked thread. The business updates the details and pays its next invoice — to the attacker. The fraud surfaces a month later, when the real supplier chases a payment it never received.

Red flags: what to inspect before you act

Perfect spelling proves nothing. CISA’s phishing guidance is clear that modern messages can be flawlessly written, so inspect the request itself instead:

  • The sender’s real address, not the display name. Open the full address. One letter changed, an extra word, or a consumer mail domain where a company domain belongs are decisive tells.
  • A request that skips the normal process. Secrecy, bypassed approvals, or a new payment destination are the attack, whatever the message around them says.
  • Urgency measured in hours. Deadlines exist to stop you verifying. A genuine sender can wait for a callback.
  • Personal details used as decoration. Real project names and colleagues’ names feel like proof of identity. They are bait, gathered from public sources. Familiarity is not authenticity.
  • Link and attachment behaviour. Hover or long-press a link to see where it goes, and treat any login page reached from an email — rather than from your own bookmark or app — as suspect. Unexpected attachments get the same treatment.

Prevention for individuals

Turn on multi-factor authentication (MFA) everywhere it is offered, preferring an authenticator app, passkey or security key over text-message codes. A stolen password on its own should never be enough to sign in.

Verify through a second channel. Never reply to the suspicious message itself. Call or message the person on a number or app you already trust, or open the service directly and look for the request there. If the request is real, it will survive being checked.

Use a password manager — for its judgement, not just its memory. A password manager will not autofill your credentials on a lookalike domain, because the address does not match the one it has saved. That refusal is one of the most reliable warnings you will ever get. Unique passwords also mean one phished password cannot unlock anything else.

Report quickly. Use your mail app’s report-phishing option or forward the message to your IT team. The same lure usually went to colleagues; reporting protects them.

Prevention for businesses

Set up email authentication — SPF, DKIM and DMARC — and enforce it. In plain terms: SPF is a published list of the servers allowed to send mail for your domain. DKIM attaches a cryptographic signature so receivers can confirm a message genuinely came from an authorized system and was not altered in transit. DMARC is your domain’s policy telling receivers what to do with messages that fail those checks — monitor them, quarantine them, or reject them — and it sends you reports on who is sending as your domain. Together they make direct spoofing of your exact domain far harder. They do not stop lookalike domains, which is why the next two controls matter.

Make payment changes boring. Any request to change bank details, add a payee or redirect payroll is verified by calling a number already on file — never a number supplied in the requesting email — and transfers above a set threshold need a second person’s approval. This single callback habit defeats most business email compromise.

Train against realistic lures, and never punish reporting. Simulations should resemble the examples above, not obvious junk mail. Staff who report — even after clicking — are the early-warning system; blame slows reporting, and slow reporting is what attackers count on.

Apply least privilege. Finance staff do not need software-installation rights, administrators should use separate admin accounts for admin work, and access should be removed the day a role changes. Least privilege does not prevent the phish; it limits what one successful phish can reach.

Keep endpoint protection current, as a backstop. Security software blunts the attachment-based variant of these attacks — our TotalAV review covers what a current suite does and does not catch — but no scanner can stop a payment an employee was talked into authorizing. Process, not software, is the defense there.

If you clicked or replied: the first hour

  1. Stop, and disconnect if you opened an attachment or ran a file. Take the machine off the network or Wi-Fi, but do not power it off unless IT tells you to — a running machine preserves evidence.
  2. Tell IT or your security contact immediately. Minutes decide whether a payment can be recalled and a session killed. Nobody competent will punish a fast report.
  3. Change the password from a different, clean device, then sign out all active sessions and check which MFA methods are registered on the account.
  4. If money has moved, call the bank’s fraud line now, not after internal emails settle. Businesses should also report to the FBI’s IC3, which identifies speed of reporting as the factor that most improves recovery chances.
  5. Look for persistence. Check for new inbox rules or forwarding you did not create, unfamiliar sent messages, and new recovery addresses or phone numbers on the account.
  6. Warn the next targets. Anyone in the impersonated thread, and the person who was impersonated, may be next.
  7. Write down the timeline while it is fresh — when the message arrived, what you clicked, what you entered. Investigators will ask; memory fades fast.

Spear phishing works because it arrives dressed as ordinary work. Almost every defense above is a habit rather than a product — slow down at the moment of the ask, and verify somewhere the attacker does not control. It is the same principle we return to across our Cybersecurity coverage, because it is the one that keeps working.

FAQ

Can spear phishing arrive by text message or phone call, not just email?

Yes. Email is the most common channel, but the same researched approach works over text messages, chat apps and voice calls — anywhere a message can impersonate someone trusted. The tell is never the channel; it is the request and the pressure around it.

Does MFA stop spear phishing?

MFA stops most logins attempted with a stolen password alone. It is not absolute: real-time phishing pages can relay a one-time code or approval prompt as you enter it. Passkeys and security keys resist that relay because they are bound to the genuine site’s address — the strongest option where available.

What should you do if you clicked on a spear phishing link but entered nothing?

Close the page, and still report it. A click alone is far less serious than entering credentials or running a file, but the same lure went to colleagues and your report warns them. If anything downloaded, treat it as an opened attachment: disconnect and call IT.

Why is spear phishing so hard to spot?

Because it is built from true facts. The names, projects and timing in the message are real — only the request is false. Filters and readers are tuned to catch messages that look wrong, and a spear phishing message’s design is to look right. That is why verification habits outperform detection instincts.

Similar Posts