A cybercriminal running a business email compromise attack typically avoids impersonating the CEO, the CFO, and other senior executives whose real communications style, calendar, and voice the finance team already knows well — and instead targets mid-level staff, external vendors, or a "new" executive nobody has met. The reason is simple: the higher the real person's visibility inside the company, the higher the chance a recipient spots the fake by stepping into a hallway, hearing a familiar voice, or noticing a change in tone. The exception matters because it tells you where your fraud defences are weakest.
Why Top-Level Executives Make Poor Impersonation Targets
Business email compromise works by borrowing trust, and the CEO holds the most trust in the building. That is exactly why a convincing CEO impersonation is hard to pull off. The people who approve payments already know how the CEO writes, when they travel, and which assistant books their calls. Any deviation — a slightly stilted greeting, a request for a wire transfer by email alone, an unusual hour — triggers a phone call that kills the scheme.
Attackers understand this risk-reward calculation. The Better Business Bureau's 2024 report on business email compromise notes that impersonation fraud is most effective when the criminal mimics a person the victim cannot easily verify. A CEO can be verified in seconds by walking two offices down. That proximity turns the attacker's best-looking disguise into their biggest liability.
There is a second structural reason. A 2023 FBI public service announcement on business email compromise highlighted how attackers exploit "legitimate" email chains and document-sharing notifications. Those tactics thrive with mid-level staff who handle routine vendor payments, not with the executive suite, where approval chains are longer and involve multiple signatures.
So the practical rule is this: a cybercriminal typically skips the CEO, the CFO, and the board chair, and aims one or two levels down, where verification habits are weaker. For anyone defending a business, that tells you to concentrate training and verification protocols on the people who approve routine payments, not just the executives.
The Vendors, Contractors, and New Hires They Do Target Instead
Consider what the criminal wants: a real payment approval from someone with authority and limited ability to double-check. That points straight at a supplier who has worked with the company for years but talks only to accounts payable, or a contractor whose invoice format is predictable. In the FBI's public guidance on business email compromise, the classic pattern is a spoofed vendor email that switches payment instructions to a "new bank account."
New employees make equally attractive targets. A first-week finance assistant hasn't learned who emails whom, so a message "from" the managing director asking for a quiet favour doesn't read as strange. The attacker isn't impersonating a senior figure to that person so much as exploiting the absence of a relationship baseline. It's the gap in familiarity, not the rank, that gets weaponized.
There's also a recurring edge case worth naming: the executive who is genuinely hard to reach, like a founder on a sabbatical or a regional head in another time zone. Attackers may still use senior names there, but only when the company's internal verification is weak — no callback numbers, no face-to-face history. When verification is strong, the same scheme collapses.
For anyone building a training programme, the takeaway is to invest more in "know your correspondent" discipline for mid-level approvers than in warning signs aimed at the C-suite. Most BEC losses start with people who actually touch payment systems.
The Half-Million-Dollar Number Behind BEC Losses
The Federal Bureau of Investigation's Internet Crime Complaint Center recorded $2.77 billion in business email compromise losses in 2023, according to its annual Internet Crime Report. That figure matters because it dwarfs most other fraud categories and keeps BEC on every auditor's list. It's a reminder that the scheme isn't a fringe risk.
Within that total, losses often fall in a narrow band. The FBI and industry insurers commonly cite individual BEC events between roughly $10,000 and $500,000, with initial spoofed-invoice attacks averaging five figures. Larger wire-transfer frauds can crest seven figures when approval workflows are weak.
| Attack pattern | Typical target inside the company | Why the senior executive route fails |
|---|---|---|
| Vendor invoice change | Accounts payable clerk | Vendor contact is routine; CEO impersonation would trigger a callback |
| Payroll diversion | HR or payroll administrator | Payroll staff handle staff queries daily; an executive request would be routine and verifiable |
| Gift-card or urgent-payment request | Junior office manager | Managers rarely see the CEO directly, but they also lack authority for large wires |
| Real-estate or legal closing fraud | Small professional firm owner | The owner is usually reachable within minutes by phone |
| Executive "secrecy" request | Mid-level manager with signing rights | Usually flagged because the real executive's voice is known |
The variable that explains the range is verification friction: the fewer steps between the fake email and the money moving, the larger the loss. Where approvals are single-signature and email-only, losses tend toward six figures.
What the Attacker Actually Reads Before Choosing a Name
Before sending anything, a cybercriminal researches the company: public filings, LinkedIn profiles, press releases, and email auto-replies. They build a shortlist of names whose real communication style they can mimic. That research usually surfaces mid-level names more often than the CEO's, because public-facing executives are recorded and filmed constantly. A chief executive's voice will have appeared in conference videos, podcasts, and interviews.
The company's public posture also shapes the choice. A business that publishes its leadership team and press contacts creates plenty of material for a CEO impersonation, but also plenty of material for a recipient to check against. A quieter mid-level manager in finance may have no public trail at all, which cuts both ways: harder to imitate accurately, easier to impersonate because nobody knows what they "sound like."
One underreported tactic involves forwarding chains. An attacker who compromises a genuine mailbox can reply within an existing thread, inheriting the real sender's identity without impersonating anyone at all. In that case the "senior executive" question becomes irrelevant, because the criminal is speaking through an actual account. This is why mailbox compromises often precede payment fraud.
If you're reviewing your own exposure, start with which staff names are visible publicly, then check whether your finance staff would recognise those people by voice or routine contact. The gap is where the fraud lands.
A Worked Example: How a Missed Verification Unlocks a Payment
Take a construction firm with 60 staff. A supplier invoices monthly for materials and always emails accounts payable. The attacker registers a domain one character different from the supplier's, emails the same AP clerk with "updated banking details," and asks that the next invoice be paid to the new account. The AP clerk has worked with the real supplier for years and trusts the email format.
Follow the money. A typical invoice in this trade might be $18,000. Because the clerk has routine authority to pay without a second check, the payment clears. By the time the supplier calls to chase the unpaid invoice, three days have passed, and the bank's recovery window is already closing. The FBI's Internet Crime Report shows that BEC recovery rates fall sharply the longer a victim waits to report.
The point of the example isn't the amount, it's the workflow. Verification usually means "reply to the same email" — which confirms nothing, because the reply goes back to the attacker. Real verification means calling the supplier's known number and asking for their finance department directly.
Defenders who want a cheap risk metric can use this example as a test case: how many of your approved vendors could change their bank details by email alone? If the answer is "all of them," the AP desk has no perimeter.
Why a Secrecy Request Usually Backfires
A common attacker move is to tell the recipient not to discuss the request with anyone else — "this is confidential." That instruction works only when the recipient has no independent line to the real executive. If the target is a CEO, the instruction is absurd on its face, because the CEO cannot plausibly ask a staffer to keep a wire transfer secret from the finance director.
For a mid-level target, secrecy can sound more believable, especially on first contact with someone new. A junior finance staffer may genuinely think it's normal for a regional manager to request discretion. This is why proximity matters more than seniority.
One failure case worth understanding: attackers sometimes target a senior executive's trusted assistant with a request "from" the executive. It works in offices where the assistant cannot check the executive's actual location. It fails when the assistant knows the executive is in a board meeting and would never be emailing in the middle of it.
Training should treat secrecy requests as a red flag by default, regardless of who appears to be asking. Bank callbacks should be handled by a separate role, and instructions to avoid internal verification should trigger an escalation to security, not compliance.
Does the Attack Work Better Through an Actual Compromised Account?
Yes — and this changes the impersonation question entirely. When an attacker compromises a real mailbox, they don't need to impersonate anyone; they reply to genuine threads, match tone perfectly, and even slip past email authentication checks because the message genuinely comes from a legitimate domain. Reporting by the FBI notes that thread-hijacking and mailbox-compromise tactics sit at the centre of the biggest BEC losses.
The senior executive logic reverses here. An attacker with access to a CEO's account can impersonate the CEO at almost no cost, because the risk of detection through tone and style disappears. That's why the industry shifted its language from "email impersonation fraud" to "business email compromise" — the attack isn't only pretending to be someone, it's taking over their identity.
The practical consequence for defenders is that account hygiene sits above impersonation detection. Multi-factor authentication, mailbox access rules, and review of forwarding rules protect against the version of BEC where senior names are the whole game. If the attacker is already inside a CEO's mailbox, no amount of "don't trust emails from the CEO" training will save you.
This is one reason senior executives are still worth investing in for account security, even though they're poorer impersonation targets. They are high-value mailbox targets, which is a different thing entirely from high-value impersonation targets.
What Controls Actually Reduce the Risk of the Wrong Name Being Used
Given all this, the defence is less about who could be impersonated and more about making impersonation cheap to catch. Buyers often underestimate the cost of email authentication. According to the FBI's internet crime reporting, spoofed domains are still trivially easy to register, and the average cost to a small firm of implementing basic domain-based email authentication with DMARC enforcement is modest relative to the loss size of a single missed fraud.
Consider the arithmetic. A $18,000 invoice paid to a fraudulent account is the loss event. Set against that, a domain monitoring service and caller-verification programme costs a fraction of that per year for a mid-sized firm. The savings claim only holds if you actually compare like for like — the comparison is loss-avoidance, not a guaranteed return.
Steps worth following, in order of impact:
1: Register defensively similar domain names and monitor for new registrations matching your brand. 2: Enforce DMARC, DKIM, and SPF on your own domain, then require internal channels for payment changes. 3: Change the approval workflow so bank-detail changes require a callback to the supplier's known number, not the email. 4: Run short, scenario-based BEC training on the staff who touch payments, not only on executives. 5: Test recovery: know the bank's cutoff time for reversal and report to the FBI's Internet Crime Complaint Center immediately after any loss.
Failures come from two places: training that warns the wrong people, and recovery that starts too late. If your first response after a suspected loss is a "phone the IT team" message, add one more line for the bank's fraud line.
Who Should Skip the Executive-Focused Briefing and Protect Mid-Level Staff Instead
If the answer to one question — "Could a change in supplier bank details clear by email alone?" — is yes, then your money is at risk where routine payments happen, not in the executive suite. Skip the generic "watch out for fake CEO emails" session and spend the hour with accounts payable instead. That is where the criminal will actually go.
Larger, regulated firms with strong signing controls get more from the executive-account route: protecting mailboxes and identity of the people with the highest authority, because thread hijacking doesn't need impersonation at all. Those two defences are complementary, but the order depends on which risk dominates in your business.
Small firms with a single owner-approver sit oddly in the middle. The owner is recognisable to everyone, so impersonation tends to fail, but account takeover doesn't — and the owner usually handles payments personally. For those firms, protecting the owner's mailbox and enabling multi-factor authentication on the email account and bank portal is the highest-value step.
A honest drawback to state plainly: no programme fully stops a criminal who compromises a genuine account. Verification protocols and training raise the cost of failure and shorten the recovery window; they don't promise immunity. Set expectations with leadership on that basis.
FAQ
Do attackers ever impersonate the CEO successfully?
Yes, and the cases tend to fall into two groups: small companies with no independent verification, and attacks where the CEO's real mailbox was compromised so no impersonation was needed. The successful CEO-impersonation frauds reported to the FBI usually involve an employee who had never met the executive in person.
What is the single most common target in a BEC attack?
Accounts payable staff, because they routinely act on payment instructions without needing a second approver. The FBI's annual report records the majority of losses flowing through vendor-invoice and payment-change schemes aimed at this role. What you read as "the CEO is being impersonated" in news coverage often looks different inside the finance workflow.
Is a fraudulent vendor email more dangerous than a fake executive email?
In practice, yes, because the vendor email arrives inside an established routine. A fake executive message asks the recipient to do something unusual; a fake vendor message asks for a normal payment. Routine beats anomaly as an attack pattern every time.
How quickly must a company report a BEC payment?
Contact the bank's fraud line on the same day and file a complaint with the FBI's Internet Crime Complaint Center as soon as possible, ideally within 24 hours. Recovery becomes materially harder after the receiving bank moves the funds. Keep the exact time of the transfer handy.
Can email authentication stop the fake CEO email?
It stops domain spoofing, not display-name spoofing or an actual compromised mailbox. According to the FBI, attackers frequently use lookalike domains, which DMARC helps catch, but an attacker inside a real account bypasses authentication entirely. Pair authentication with callback verification.
Does impersonating a board member count as the same attack type?
Yes, and it's still BEC. The senior executive doesn't have to be employed; a director or investor with signing influence can be impersonated when their identity grants access to funds or data. The verification rule remains: call the person, not the address.
What is the loss range for a typical BEC incident?
The FBI's published figures put the aggregate at billions annually, with individual losses commonly in the $10,000–$500,000 band for mid-sized firms. Larger wire frauds can exceed seven figures when a single-signature workflow is exploited.
Why do some attackers still use executive names?
Two reasons: to scare a junior recipient into acting without verification, and because in the attacker's world a "senior" name costs nothing to fake. If the recipient can't verify quickly, the seniority trick can still work.
This article is general educational information about fraud and cybersecurity, not legal or financial advice. It doesn't promise any specific outcome from the steps described. For regulatory or contractual questions, consult a qualified local professional, and if a crime is in progress or funds have moved, contact local law enforcement and your bank's fraud line immediately.