Article

Surviving a Business Email Compromise Attack: Response, Recovery, and Prevention

November 17, 2026
woman developer looking at multiple computer monitors

Key Takeaways

  • Business Email Compromise (BEC) scams deceive organizations into sending money or employee personal information to a malicious actor. They use specific details to look real, and the emails often come from the compromised or spoofed accounts of employees or vendors.
  • BEC is an organizational risk, not just an IT issue. Because these attacks exploit trusted communications and payment processes, finance, leadership, and cybersecurity teams all play a role in reducing risk.
  • Strong prevention combines people, processes, and protections. Employee awareness, independent payment verification, dual approvals, multifactor authentication, and a tested incident response plan can make a convincing fraudulent request much less likely to succeed.

Business Email Compromise (BEC) is one of the most common and costly threats organizations face. It usually starts with an ordinary email: A vendor writes to say its bank details have changed, or an executive asks for a quick wire before the end of the day. Nothing about the message looks unusual — and that is exactly why it works.

74% of organizations surveyed reported experiencing BEC in 2025, up from 63% the year before.

But a BEC attack doesn't have to end in a permanent loss. We’ve outlined how to tell if you've been hit, what to do in those first critical hours, and how to keep it from happening again.

What Is Business Email Compromise?

BEC scams are defined as attempts to deceive organizations into sending money or employee personal information to a malicious actor, or to misuse the organization's name to obtain goods fraudulently. These scams use specific details about the organization, the sender, and the recipient to look real, and the emails often come from the compromised or spoofed accounts of employees or vendors.

In practice, attackers either take over a real mailbox (often through a phishing email that harvests a password) or impersonate a trusted party using a look-alike domain or spoofed address. They then insert themselves into a legitimate business process, such as vendor payments, real estate closings, payroll or executive requests, and redirect the money to an account they control.

How A Business Email Compromise Attack Works


01

Reconnaissance

Researches people and payment processes

02

Access or Impersonation

Compromises email or spoofs a domain

03

Monitor and Wait

Watches email activity for an opportunity

04

Fraudulent Request

Sends fake payment or payroll instructions

05

Funds Diverted

Money is sent to a fraudulent account

BEC attacks exploit trust and routine processes, often without using malware.


BEC is particularly effective because it rarely relies on malware. Arctic Wolf found phishing was the root cause of 72.9% of the BEC cases it investigated, with previously stolen credentials behind another 18.8%.

Who Attackers Target

Attackers favor industries where large payments, wire transfers, and financial correspondence are part of everyday work. Finance and insurance organizations accounted for more than a quarter of all BEC cases in 2025, roughly double the next closest sector.

No sector is immune, however. Legal and government organizations and manufacturers also rank near the top, and any organization that pays vendors, runs payroll, or moves money by wire is a potential target.

Industry Share of BEC Incident response cases
Finance and insurance 26.5%
Legal and government 13.3%
Manufacturing 12.0%

Nonprofits: A Growing Target

We are seeing a rise in BEC attempts against nonprofit organizations. Lean finance teams, frequent changes to vendor and payee details, and a culture built on trust and urgency can make them attractive targets. When a fraudulent payment goes through, the loss is more than a line item. It is money that was meant for the mission. The safeguards below, especially independent payment verification and dual approvals, matter just as much for nonprofits as for any other organization.

BEC Is a Finance Problem, Not Just an IT Problem

BEC is often depicted as an email security issue, when in reality, email is just the delivery method. The loss happens when a payment process lets one person move money based on one message. That makes BEC as much a finance and internal controls issue as a technology one, and it's why your CFO or controller needs to be part of the conversation.

A few questions every finance leader should be able to answer:

  • Who can change a vendor's or employee's bank details, and how is each change verified before the next payment goes out?
  • Is the person who updates vendor information different from the person who approves payments?
  • Do you have callback rules and dollar thresholds that require a second approver, with no exceptions for urgency?
  • Are changes to your vendor master file reviewed regularly, so an unauthorized change gets caught?

If an incident does happen, expect your auditors to ask these same questions. A BEC loss can raise concerns about how well your internal controls are designed and operated. Clear answers make that conversation much easier.

Signs of an Attack

Many organizations do not discover a BEC attack until a vendor calls asking why an invoice is past due, or an employee asks why a paycheck never arrived. By then, the money has often been moving for days.

Watch for these warning signs:

  • A vendor or partner says they never received a payment that your records show as sent.
  • An employee reports a missing direct deposit after recently updating banking details.
  • Payment instructions changed by email, especially with pressure to act quickly or keep the request confidential.
  • Mailbox rules you did not create that forward, delete, or hide messages, often rules that move emails containing words like "invoice," "payment”, or “wire."
  • Sign-in alerts or logins to email accounts from unfamiliar locations or devices, or at unusual hours.
  • Replies to emails you never sent, or contacts mentioning messages that do not appear in your Sent folder.
  • Sender addresses that are almost right, such as a single changed letter or a different domain ending.
  • A vendor or employee bank change that was processed outside your normal approval steps, or a payment released without the usual second approval.

If any of this sounds familiar, assume a compromise until proven otherwise. At this stage, speed matters more than certainty.

What to Do After an Attack

The first few hours after a BEC attack are critical. The faster you detect the issue and respond, the more likely you are to get your money back. Funds are usually moved quickly from the receiving account, often in several hops and sometimes overseas, so every hour of delay works against you. Take these steps in order, and in parallel where you can.

The first few hours after a BEC attack are critical. The faster you detect the issue and respond, the more likely you are to get your money back. Funds are usually moved quickly from the receiving account, often in several hops and sometimes overseas, so every hour of delay works against you. Take these steps in order, and in parallel where you can.

1. Contact your bank immediately

Call the financial institution that sent the payment as soon as fraud is recognized. Request a recall or reversal of the transaction and ask for a Hold Harmless Letter or Letter of Indemnity. Moving quickly on both can reduce, and in some cases eliminate, the financial loss.

Have the details ready: the date, amount, receiving bank, account number, and any wire or ACH reference numbers. Ask the bank to contact the receiving institution directly to request a freeze. Policies differ between financial institutions, so it helps to know ahead of time what assistance your bank will provide.

2. File a complaint with the FBI through IC3

File a detailed complaint with the Internet Crime Complaint Center (IC3). Include as much detail as possible, especially the banking information for both the sending and receiving accounts, and file regardless of the amount lost. A fast, complete report gives law enforcement and the financial institutions involved the best chance to freeze funds before they disappear.

3. Contain the compromise

Treat the incident as a security breach, not just a payment problem. Reset passwords for affected accounts and sign them out of all sessions. Confirm multifactor authentication is enabled and review which devices and apps are registered.

Remove any suspicious inbox rules, forwarding settings, or connected applications. Review sign-in logs to understand when the attacker gained access and what else they may have touched.

4. Preserve the evidence

Do not delete fraudulent emails. Save the original messages with full headers, invoices, payment records, and system logs. This evidence supports your IC3 complaint, your bank’s recovery efforts, any insurance claims, and any later forensic investigation.

5. Notify the right people

Bring in your leadership, legal counsel, and cyber insurance carrier early. Many policies have notification requirements and may provide access to incident response resources. Contact the vendors, clients, or employees whose communications were impersonated so they can watch for follow-up attempts. Depending on what information the attacker accessed, you may also have data breach notification obligations, so involve counsel before deciding.

6. Investigate the full scope

An attacker who sat in a mailbox for weeks may have seen far more than one payment conversation. A forensic review can determine how access was gained, what data was viewed or exported, and whether other accounts or partners were targeted.

Taking a Proactive Approach to Prevention

Recovery is possible, but it’s never guaranteed — making prevention top priority. Preventing BEC requires people, processes, and protections. Your employees need to understand the signs of an attacker reaching out, processes need to be in place to help prevent unauthorized changes, and the protections and controls should keep attackers out of your systems. When any one of those three is weak, attackers will find it.

Make your people the first line of defense

The human element was present in 62% of breaches in the Verizon 2026 Data Breach Investigations Report. Employees in finance, accounts payable, HR, and executive support are the primary targets. Provide regular, role-specific training that uses real BEC examples, including phone and text-based pretexting, not just email phishing simulations.

Make sure everyone knows who owns the response when something looks wrong. Most importantly, build a culture where pausing to verify a request is expected and praised, even when the request appears to come from the CEO. People who are thanked for reporting a suspicious message keep reporting; people who are embarrassed stop.

Build processes that verify every payment change

Out-of-band verification is the single most effective control against BEC. Any request to change bank details, or any unusual payment request, should be confirmed through a separate channel using contact information you already have on file — never a phone number or link from the email itself. Require dual approval for wire transfers, keep the person who changes vendor or payroll banking information separate from the person who approves payments, and set dollar thresholds that trigger additional review. Make these written procedures with no exceptions for urgency or seniority.

Manage the risk your vendors bring

Many BEC attacks start in someone else’s mailbox. When a vendor’s email account is compromised, the fraudulent invoice arrives from a real address in a real conversation. Verizon found that third parties were involved in 48% of breaches. Know which vendors can request payments, keep a verified contact list for each, and talk with your bank about fraud protections such as positive pay, callback verification, and payment alerts.

Protect the email environment

Enable multifactor authentication on every email account, prioritizing phishing-resistant methods for executives and finance staff. Implement email authentication standards (SPF, DKIM, and DMARC) to make your domain harder to spoof. Flag external emails, monitor for newly registered look-alike domains, and alert on new inbox forwarding rules or unusual sign-ins.

Prepare, test, and improve

An organization’s response is only as strong as their preparation. Create a BEC response playbook that names who calls the bank, who files the IC3 complaint, who contacts the insurer, and who leads the technical investigation. Keep your bank’s fraud contact somewhere easy to reach. Test the plan with a tabletop exercise, validate that your email and payment controls work as intended, and review your cyber insurance coverage for social engineering losses. Each test should leave you a little stronger than the last.

How Eide Bailly Can Help

BEC succeeds because it looks like normal business. Surviving it comes down to acting fast when something goes wrong and building the people, processes, and protections that stop a fraudulent request before money ever leaves your account. Call your bank, report the crime, contain the compromise, and bring in your accountant to handle what comes after. Then close the gaps so the next convincing email goes nowhere.

Eide Bailly’s cybersecurity professionals help organizations prepare for, respond to, and recover from incidents like Business Email Compromise. Using our Cybersecurity Success Framework, we look at how your people, processes, and protections work together, identify the weakest link, and help you strengthen it.

Let’s talk about how to enhance your organization’s security.

Frequently Asked Questions

What Is Business Email Compromise?

Business Email Compromise (BEC) scams attempt to deceive organizations into sending money or employee personal information to a malicious actor, or to misuse the organization's name to obtain goods fraudulently. They use specific details about the organization, the sender, and the recipient to look real, and the emails often come from the compromised or spoofed accounts of employees or vendors.

Who are the most common targets of Business Email Compromise?

BEC can affect any organization that pays vendors, processes payroll, or transfers money. Attackers often target employees in finance, accounts payable, HR, and executive support, as well as industries where large payments and financial correspondence are routine.

What are the signs that an organization has been victimized by Business Email Compromise?

Warning signs include missing vendor payments or employee deposits, unexpected changes to payment instructions, unfamiliar mailbox rules or logins, emails you did not send, and bank changes processed outside normal approval procedures. If something appears suspicious, treat it as a potential compromise and investigate quickly.

How can Business Email Compromise be prevented?

Organizations can reduce BEC risk by combining employee training with strong payment processes and email security. Key safeguards include independently verifying changes to payment information, requiring dual approval for transfers, using multifactor authentication, and testing incident response procedures.

Who is responsible for preventing and responding to an attack?

BEC is not solely an IT responsibility. Prevention and response require coordination across leadership, finance, IT or cybersecurity, employees, and, when an incident occurs, legal counsel, financial institutions, insurers, and other relevant advisors.

What must be done after an attack to minimize losses?

Act immediately by contacting your financial institution to attempt to recall or freeze the payment and reporting the incident to the FBI’s Internet Crime Complaint Center (IC3). At the same time, contain compromised accounts, preserve evidence, notify appropriate stakeholders, and investigate the full scope of the incident.

The Proactive Playbook: Risk, Resilience, and Regulatory ReadinessThe Essential Guide to Due Diligence
This playbook gives business leaders a roadmap for turning risk into resilience. It’s designed to help you secure your foundation, understand your risks, and be ready to respond.
Instant Access

About the Author(s)

Rob Else
Rob Else
Director/Cybersecurity Practice Leader
Rob helps businesses protect their information from cyber threats. He works with them to create and implement security plans so they can focus on their work without worrying about their technology.
Rick Olivier
Rick Olivier
Director
Rick helps organizations understand their cybersecurity risks by providing expert guidance and advisory solutions that uncover vulnerabilities and support smarter, more secure decisions.