Business Email Compromise Recovery: What to Do After a BEC Loss
Business email compromise recovery has two halves, and most guides only cover one. The first is the money: a wire that may still be recallable. The second is the mailbox itself, which the attacker still controls and is still using to invoice your customers. Fixing the money without fixing the mailbox means the loss repeats next week. A convincing invoice email is the usual entry point for BEC, and checking an email for scam signals covers the recall window once a payment has gone.
Business Email Compromise Recovery. The Mailbox Is Still Theirs
The Short Version: Business Email Compromise Recovery
- A BEC attack is mailbox takeover, not a single fraudulent email. The attacker reads, waits, and then redirects a real payment.
- Two tracks run in parallel: recall the wire, and evict the attacker from the mailbox. Neither alone is enough.
- The IC3 recorded 21,442 BEC complaints and $2.77 billion in losses in 2024 — an average above $129,000 per complaint.
- Notify your bank, your customer, your insurer and law enforcement in that order, within the first business day.
The short answer: two problems, not one
Most BEC victims discover the fraud when a supplier says they never received payment, or a customer says they paid an account they have never used before. By then the attacker has usually been inside the mailbox for weeks.
| Track | What is at stake | Deadline |
|---|---|---|
| Money | The redirected payment, if it is still in the receiving account | Hours. A recall is only possible while funds remain. |
| Mailbox | Every future invoice, every customer relationship, every credential | Same day. The attacker is still reading. |
| Reputation | Customers who paid a fraudster and expect you to absorb it | First 48 hours, before they hear it elsewhere |
The order is not obvious. Most people start with the bank. That is correct for the money, but it leaves the attacker in place — and a BEC actor who sees the account being locked will often send one more invoice before they are evicted. Do both, and do the mailbox eviction the same day.
What the IC3 data shows about BEC losses
BEC is not the most-reported cybercrime, but it is consistently one of the most expensive, because a single successful attack redirects a five- or six-figure payment.
- The IC3 received 21,442 BEC complaints in 2024, with reported losses of $2.77 billion — the second-costliest category after investment fraud.
- That works out to an average reported loss above $129,000 per complaint, which is why BEC is treated as an organisational incident rather than a consumer one.
- BEC losses have totalled roughly $8.5 billion across 2022–2024 alone, and more than $17 billion since the category was first tracked in 2015.
- Total reported cybercrime losses reached $16.6 billion in 2024, of which BEC accounted for more than 17%.
The scale explains why banks, insurers and law enforcement all have BEC-specific processes. You are not explaining a novel situation to any of them — which means the fastest path is to use their vocabulary: "business email compromise", "unauthorised wire", "account takeover", "recall request".
The first business day: the exact sequence
Work down this list in order. Steps 1 and 2 can run in parallel if two people are available.
1. Call the sending bank and request a wire recall
Ask for the fraud team and say: "We sent a wire on [date] to [account] as a result of a business email compromise. The beneficiary account is fraudulent. We are requesting an immediate recall and a fraud hold on the receiving account."
Give them the Fedwire or SWIFT reference, the exact amount, and the time sent. If the funds are still in the receiving account, a recall is realistic. If they have moved, the bank will tell you — and that answer determines everything that follows.
2. Evict the attacker from the mailbox
In this order: revoke all active sessions, reset the password, enable phishing-resistant MFA, then audit. Check for inbox rules that forward or delete messages, check for delegate access, check for connected applications and OAuth grants, and check the sent items for messages you did not send.
3. Identify every message the attacker sent
Search sent items and the mail flow logs for the period of compromise. You need the list of recipients, because each one is a potential second loss and a person you must call before they pay.
4. Call the affected customer or supplier directly
Not by email — the attacker may still have access, and your email is now suspect to them. Call, explain, and ask them to stop any pending payment. Give them a single named contact and a callback number they can verify independently.
5. Notify your insurer and law enforcement
If you hold crime or cyber coverage, notify the insurer the same day — most policies require prompt notice and many have a preferred incident-response panel. Then file with the IC3 at ic3.gov and, if the amount is significant, with your local FBI field office.
What a wire recall can and cannot achieve
A recall is a request to the receiving bank, not a right. Understanding the mechanics stops you wasting the first day on the wrong expectation.
| Funds position | Realistic outcome | Who decides |
|---|---|---|
| Still in the beneficiary account, unclaimed | Recall often succeeds; funds returned minus fees | Receiving bank's fraud team |
| Withdrawn or transferred onward | Recall fails. Recovery depends on a criminal case. | Receiving bank, then law enforcement |
| Beneficiary account is a mule account | Partial recovery possible if frozen before withdrawal | Receiving bank, on a fraud-hold request |
The single most useful thing you can do is get the receiving bank to place a hold. A recall request that names the account and states "fraud" moves faster than a general indemnity claim, because it triggers the bank's own suspicious-activity process.
How the attacker got in, and why they waited
BEC actors rarely break in. They log in, using credentials from a breach, a phishing page, or a consent prompt that granted an OAuth token.
- Credential reuse. A password from an unrelated breach works because it was reused on the mail account.
- Adversary-in-the-middle phishing. A convincing login page captures both the password and the session cookie, defeating ordinary MFA.
- OAuth consent phishing. The user grants a malicious app permission to read mail — no password needed afterwards.
- Vendor or client compromise. The attacker takes over a party you already trust and replies inside a real thread.
The waiting is the tell. A BEC actor typically monitors for weeks, learns your payment cycle, your signatories and your tone, then inserts a single message at the moment an invoice is due. That is why the fraudulent email often looks perfect — it is written in your own style, because they have read everything you wrote.
If the wire has already left the receiving account
This is the more common outcome, and it changes the objective from recovery to documentation and containment.
Build the incident file
Collect the original invoice, the fraudulent email with full headers, the wire confirmation, the recall request and the bank's response, the mail audit log showing the unauthorised access, and a dated timeline. Your insurer will ask for exactly this, and so will law enforcement.
Preserve the evidence properly
Export the fraudulent message as an .eml file rather than forwarding it — headers are what prove the origin. Screenshot the inbox rules before you delete them, then remove them.
Decide the customer conversation early
If a customer paid the fraudster believing they were paying you, the question of who bears the loss will come up. Handle it as a relationship decision, not a legal one, and involve your insurer before you make any commitment.
Prevention that actually holds
- Phishing-resistant MFA (passkeys or hardware keys) on every mailbox. Ordinary push or SMS MFA does not stop session-token theft.
- Callback verification for every change of bank details, using a number from your own records.
- Alert on new inbox rules and on new OAuth grants. Both are the persistence mechanisms attackers rely on.
- Dual authorisation above a threshold, with the second approver seeing the beneficiary details, not just the amount.
- Quarterly access review for delegate permissions and connected apps — the two places attackers hide.
Why BEC survives every security upgrade
Because it targets a process rather than a system. No firewall inspects whether an invoice is genuine, and no email filter reliably distinguishes a well-written message from a compromised account from a legitimate one — the account really is legitimate.
That is why the effective controls are procedural: a callback, a second approver, an alert on rule creation. They cost almost nothing and they break the attack at the only point where it is visible — the moment someone is asked to change where money goes.
Questions people ask about business email compromise recovery
What is the difference between BEC and phishing?
Phishing is the entry method; BEC is what happens after. A BEC attack involves taking over or impersonating a real mailbox and using it to redirect a payment, usually after a period of monitoring. The victim is often a business, and the loss is usually a wire transfer.
How quickly can a BEC wire be recalled?
A recall is only possible while the funds remain in the receiving account, which can be hours. Call the sending bank's fraud team immediately and ask them to request a fraud hold on the beneficiary account. Once funds are withdrawn, the recall fails.
Does cyber insurance cover BEC losses?
Often yes, under crime or social-engineering coverage, but the wording varies enormously and many policies require prompt notice and use of an approved incident-response provider. Notify your insurer the same day, before you commit to any recovery spend.
How do I know if my business email has been compromised?
Look for inbox rules you did not create, sent messages you did not write, unexpected password-reset emails, mail clients you do not recognise in the account's device list, and customers reporting emails from you that you never sent.
How much does BEC cost businesses each year?
The IC3 recorded 21,442 BEC complaints and $2.77 billion in reported losses in 2024, an average above $129,000 per complaint. Losses have totalled more than $17 billion since the category was first tracked in 2015.
Should I tell my customers that my email was hacked?
Yes, and quickly, by phone. Anyone who received a fraudulent message from your mailbox is a potential second loss, and they need to hear it from you before they hear it from their bank. Waiting to 'confirm the full picture' is the mistake that turns one loss into three.
Build the incident file while the logs still exist
Mail audit logs roll off. A dated record captured today is what your insurer and the FBI will ask for.
Primary sources and further reading
- FBI IC3 — 2024 Internet Crime Report — ic3.gov
- Abnormal — 2024 FBI IC3 Report: BEC Remains a Multi-Billion Dollar Threat — abnormal.ai
- FBI IC3 — File a Complaint — ic3.gov
- FTC — ReportFraud.ftc.gov — reportfraud.ftc.gov
Related guides
Information only. We never promise recovery.