Zoes
← Blog

Why business email compromise stays so expensive

Reported BEC losses have held near $3 billion a year in FBI data, roughly fifty times what is reported for ransomware. Four structural reasons it keeps working.
By · October 14, 2026 · 6 min read
Two people reviewing printed figures beside laptops
Photo: Scott Graham on Unsplash

The numbers

Every year the FBI's Internet Crime Complaint Center (IC3) publishes what victims reported to it. Business email compromise - an email that impersonates a colleague, executive or supplier to get money moved - has sat near the top of the loss table for the past four reports:

Year
Complaints
Reported losses
Average per complaint
2021
19,954
$2.40 billion
~$120,000
2022
21,832
$2.74 billion
~$126,000
2023
21,489
$2.95 billion
~$137,000
2024
21,442
$2.77 billion
~$129,000

In 2024 BEC was the second-costliest crime type in the whole report, behind investment fraud. For comparison, IC3 recorded about $60 million in ransomware losses for 2023. That ransomware figure is known to be incomplete - it leaves out downtime and recovery costs, and many victims never file - but even with generous adjustment, impersonation emails move more money than any email threat that involves malware.

Source: FBI IC3 Internet Crime Reports 2021-2024. Averages are calculated from the published totals.

What the average hides

A six-figure average is easy to read as an enterprise problem. It is not. The complaint count has hovered around 21,000 a year, and the losses are spread across companies of every size. An average is pulled up by a few very large transfers; the typical small-business loss is smaller, but it is also a larger share of what the business has in the bank.

Two things make the real number higher than the reported one. Many businesses never report a loss - because the money was recovered, because they are embarrassed, or because nobody knew where to report it. And the loss is rarely just the transfer: there is the payment owed to the real supplier, the time spent with the bank, the insurer and the auditor, and sometimes a damaged supplier relationship.

Why it keeps working

Over the last decade, email-borne malware got steadily harder to land: attachments are opened in sandboxes, links are rewritten and checked at click time, browsers block known bad sites. Almost none of that touches BEC.

  • There is no payload. A BEC message is a few lines of plain text. There is no file to detonate and often no link to check, so the defences built around inspecting payloads have nothing to inspect.
  • It costs almost nothing. A lookalike domain costs about ten dollars and takes minutes to register. Writing the email is free, and language models now write it fluently, in the right tone, in any language.
  • It is low volume by design. One message to one person, sent once. Reputation systems learn from patterns across many mailboxes; a single message from a domain that did not exist last week gives them nothing to learn from.
  • The victim completes the attack. A real employee authorises a real payment through a real bank. Nothing downstream looks wrong until the genuine supplier asks, weeks later, why they have not been paid.

How an attempt unfolds

The pattern below is a composite. Names and domains are fictional.

Stage
What the attacker does
Research
Reads the company website, LinkedIn and press releases to learn who approves payments and who the regular suppliers are.
Setup
Registers greywater-supply.com to imitate the real supplier greywatersupply.com, or a lookalike of the company's own domain.
Timing
Writes near month-end, before a holiday, or while the owner is travelling - when payments are expected and people are rushed.
The ask
"Our bank has changed, please use the details below for this month's invoice." Polite, short, plausible.
Pressure
Follows up the next day: "Accounts is asking - has this gone out?" Sometimes a second, fake "manager" joins the thread.
Cash-out
The money lands in a mule account and is moved on within hours, which is why speed matters so much if it is caught.

Who gets hit

BEC is aimed, not sprayed. It lands on the few people who can move money without a second signature: accounts payable, payroll, executive assistants, and at small companies the owner or office manager who does all of those jobs. A company with 30 staff may have two or three such people, and attackers know which two or three.

That is why a company-wide count of blocked messages says little about BEC risk. The question that matters is how much dangerous mail reaches those specific inboxes. Zoes' Most Targeted Members view answers exactly that, ranking people by the severity of what they receive rather than by volume.

What changes the odds

Ranked roughly by how much loss each control prevents for the effort it takes:

Control
What it stops
Effort
Phone verification of bank changes
Almost every vendor and payroll diversion, whatever got through the filters
A written rule
Two-person approval above a threshold
Single-employee mistakes under time pressure
Low
MFA on every mailbox
Account compromise, the source of the most convincing BEC
Low to medium
Blocking external auto-forwarding
Attackers quietly watching invoice threads from inside a mailbox
One setting
DMARC on your own domain
Exact spoofing of your domain to your customers and staff
Medium
Inbox-level detection
Lookalike domains, first-time senders posing as known contacts, payment-change scripts
Minutes to connect
Step-by-step setup for each of these is in the business email compromise post and the small-business checklist.

A policy you can copy

The single most effective control is a written payment-verification rule that everyone with access to money has read. It does not need to be long. A version that fits most small companies:

1. We never change a supplier's, customer's or employee's bank details because of an email, a PDF letter or a text message alone.

2. Every change is confirmed by phone, using a number from our own records or the original contract - never one supplied in the request.

3. The first payment to any new account, and any payment above an agreed amount, needs a second person to approve it.

4. Urgency or secrecy in a payment request is a reason to slow down. Nobody is criticised for delaying a payment to check it.

5. Anyone who thinks a payment went to the wrong place tells the owner and the bank immediately, at any hour.

The fourth line matters more than it looks. BEC works by making a careful employee feel that checking is the risky option - that the CEO will be annoyed, or the supplier will stop shipping. A rule that explicitly protects people who slow down removes that pressure.

Share the policy with your regular suppliers too. When they know you always call to confirm bank changes, a request that asks you not to call stands out immediately - to them and to you.

The first hour

If a payment has already gone to the wrong account, the order of operations matters:

  1. 1Call your bank's fraud line, not your branch, and ask for a recall of the transfer. Give them the amount, time, and receiving account.
  2. 2In the US, file at ic3.gov the same day. The FBI's Recovery Asset Team works with banks to freeze funds, and it can only help while the money is still in the receiving account.
  3. 3Assume a mailbox may be compromised: reset the password, sign out all sessions, and check for forwarding rules and inbox rules that hide replies.
  4. 4Contact the real supplier on a known number. They may be compromised too, and other customers may be receiving the same request.
  5. 5Tell your insurer early. Many policies have notification windows and conditions about verification procedures.

Questions

Can the money be recovered?

Sometimes, if the bank and law enforcement act before it is moved on. Within the first day the odds are far better than after a week.

Does cyber insurance cover BEC?

Often only partly, and many policies require proof that payment changes were verified. Read the social-engineering section of your policy before you need it.

Will SPF, DKIM and DMARC stop it?

They stop exact spoofing of your own domain. They do nothing against a lookalike domain or a real, hijacked supplier account. See SPF, DKIM and DMARC explained.

Keep reading

See what is reaching your inboxes

Connects to Google Workspace or Microsoft 365 in minutes. Try it free for 14 days.