Quick answer
Business email compromise (BEC) is fraud in which attackers use a compromised or spoofed email account to trick staff into paying money or changing bank details. Common forms are fake supplier invoices, payroll redirection, property settlement fraud and executives appearing to request urgent transfers. It is one of the costliest forms of cybercrime worldwide.
On this page
How It Works
Attackers either take over a real mailbox through phishing or password reuse, or send from a lookalike or spoofed domain. In a takeover, they quietly read email for weeks, learn who pays whom, set up inbox rules to hide replies, then insert themselves into a genuine conversation with new bank details at the perfect moment. AI now helps them match the tone of the person they impersonate, and deepfake voice calls are used to confirm fake requests.
Why It Matters
Payments made to fraudsters are rarely recovered. Because the email often comes from a real account or a convincing lookalike, technical controls alone do not stop it; the decisive control is the payment process.
How to Test for It
- Test payment and bank-detail change procedures with authorized scenarios that use realistic pretexts.
- Check whether your domain can be spoofed: SPF, DKIM and enforced DMARC.
- Review mailboxes for suspicious inbox rules and external forwarding.
- Test help desk and finance verification steps under pressure from apparent seniority.
- Check MFA coverage on every mailbox, including shared and service accounts.
How to Reduce the Risk
Require call-back verification on a known number before changing bank details or paying new accounts, enforce DMARC, block automatic external forwarding, alert on new inbox rules, enforce MFA everywhere and train finance staff to treat urgency and secrecy as red flags.
Regulatory and Framework Context
In the US, business email compromise caused more than $3 billion in reported losses in 2025 according to the FBI's Internet Crime Report; victims should report through IC3 and contact their bank immediately.
Being exploited now
Threat Radar →The latest related vulnerabilities confirmed as exploited in the wild.
- CVE-2026-111793·1 week ago·Email & commsOpenwave Messaging Limited Webtop Media TranscoderOpenwave Messaging Limited Webtop Media Transcoder Incorrect Resource Transfer Between Spheres VulnerabilityEPSS 0.64%
- CVE-2026-116606·1 week ago·Email & commsBarracuda Networks Barracuda Email Security Gateway (ESG)Barracuda Networks Email Security Gateway (ESG) Authentication Bypass Using an Alternate Path or Channel VulnerabilityEPSS 10.9%
- CVE-2026-124194·1 week ago·Email & commsMicrosoft OfficeMicrosoft Office Outlook Missing User Interaction for Potentially Unsafe Action VulnerabilityEPSS 1.6%
- CVE-2026-20320·1 week ago·Email & commsCisco BroadWorksCisco BroadWorks Improper Restriction of XML External Entity Reference VulnerabilityEPSS 0.98%
Latest intel on this topic
- Barracuda links cloud breach to ARTEX AI-powered cyberattackBleepingComputer · November 16, 2026
- Barracuda’s email security gateways bitten by make-me-root vulnsThe Register · November 10, 2026
- Trio used AI to impersonate corporate execs, defrauding companies of nearly $130 million: DOJAI Incident Database · November 7, 2026
- Germany Busts 'Crime-as-a-Service' Investment Fraud OutfitDark Reading · November 3, 2026
- “Next Exploit Opportunities”: How a Threat Actor Used AI to Help Plan and Execute Multiple Types of Cybercrime ActivitiesUnit 42 · October 21, 2026
Updated hourly from the daily briefing. More in scam alerts and fraud warnings.
Common questions
Can BEC payments be recovered?
Sometimes, if the bank is contacted within hours. After funds move on, recovery is rare, which is why prevention through verification matters most.
Does DMARC stop business email compromise?
It stops attackers spoofing your exact domain, but not lookalike domains or compromised real accounts, so process controls are still essential.
For testers: finding write-ups
How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.
Change log
- November 13, 2026First published.