Business email compromise (BEC) is a form of targeted fraud in which an attacker impersonates a trusted business contact to persuade someone to transfer money, change payment details, disclose sensitive information, or perform another unauthorized action. It combines social engineering with the exploitation of business communication and approval processes, usually through email. Despite its name, BEC does not necessarily involve a compromised mailbox: attackers may use forged sender information or look-alike addresses instead.
Scope and distinguishing features
BEC exploits the apparent legitimacy of a business request. A message may seem to come from a senior executive, supplier, colleague, lawyer, or customer, and may refer to an actual invoice, transaction, or ongoing conversation. The intended action often resembles an ordinary task that the recipient is authorized to perform.
BEC overlaps with phishing, particularly highly targeted phishing, but the terms describe different aspects of an attack. Phishing is a method of deception that can be used to obtain credentials or deliver malicious content. BEC describes a fraud scenario centered on abuse of trusted business communications. A phishing message may steal the credentials later used in a BEC operation, while the eventual fraudulent payment request may contain neither an attachment nor a link.
Unlike many malware attacks, BEC can succeed without exploiting a software vulnerability or executing unauthorized code. A technically uncompromised recipient may approve a payment because the request appears credible.
“CEO fraud” is often used for the executive-impersonation subtype, but it does not encompass all BEC schemes.
Impersonation and account access
Attackers establish apparent credibility through several mechanisms.
Sender spoofing. Email spoofing falsifies sender information so that a message appears to originate from a trusted person or organization. A familiar display name can also conceal an unrelated sending address.
Look-alike domains. An attacker may register a domain resembling a legitimate organization's domain through small spelling changes, added words, or visually similar characters. The address is controlled by the attacker rather than by the impersonated organization.
Mailbox takeover. Stolen passwords, compromised sessions, or maliciously obtained application permissions can give an attacker access to a genuine account. Messages sent from that account may pass normal technical checks and appear within established correspondence.
Conversation hijacking. After gaining access to a mailbox, an attacker may read an existing exchange and intervene at a financially significant moment. Authentic signatures, invoice details, and prior correspondence can make a fraudulent instruction difficult to distinguish from routine business communication.
In a compromised account, mailbox rules may also redirect messages or hide replies that would otherwise reveal the fraud. The compromised mailbox may belong to the victim organization, a supplier, or another participant in the transaction.
Common forms
| Form | Typical fraudulent request |
|---|---|
| Executive impersonation | A supposed senior manager directs an urgent or confidential payment. |
| Supplier or invoice fraud | An apparent supplier asks that a legitimate invoice be paid into a different bank account. |
| Payroll diversion | Someone impersonating an employee requests a change to salary-payment details. |
| Transaction diversion | A participant in a property purchase or another high-value transaction appears to provide revised payment instructions. |
| Gift-card or purchase fraud | An apparent manager asks an employee to buy gift cards or goods and disclose the redemption details. |
| Sensitive-information theft | An apparent authorized requester asks for employee records, tax documents, or other confidential information. |
These categories can overlap. A supplier impersonation may begin with mailbox takeover and end with conversation hijacking. Some schemes combine email with telephone calls, text messages, or online meetings.
Typical progression
BEC operations vary, but commonly involve several stages:
- Reconnaissance. The attacker identifies relevant staff, reporting relationships, suppliers, or transactions using public information, social media, or stolen correspondence.
- Preparation. The attacker obtains account access or creates an impersonating identity, then develops a plausible business pretext.
- Request. The victim receives an instruction framed as legitimate work. Urgency, confidentiality, authority, or a plausible administrative change may be used to discourage verification.
- Transfer or disclosure. Money, information, or redeemable value is sent to an attacker-controlled destination.
- Concealment and movement. The attacker may suppress correspondence or move funds through additional accounts to complicate detection and recovery.
The central deception is often not that a transaction exists, but that its destination or authorization has changed. A genuine outstanding invoice can therefore become the basis for a fraudulent payment.
Detection and prevention
BEC prevention involves both cybersecurity controls and financial-process controls.
Identity and mailbox security
Multifactor authentication reduces risks associated with stolen passwords, although protection depends on the method and implementation. Some attacks target authenticated sessions or induce users to approve fraudulent sign-ins. Phishing-resistant authentication provides stronger protection against credential-relay attacks than reusable passwords or manually entered one-time codes.
Access controls, least-privilege permissions, and monitoring of mailbox rules, forwarding settings, and application permissions can limit opportunities for takeover and concealment.
Email authentication and filtering
Sender Policy Framework, DomainKeys Identified Mail, and Domain-based Message Authentication, Reporting, and Conformance help receiving systems assess whether messages are authorized to use particular domains. Correct deployment can reduce direct impersonation of a protected domain.
These mechanisms do not establish that a business request is honest. A look-alike domain can authenticate its own messages, and a compromised legitimate account can send technically authentic fraudulent mail. Likewise, encryption protects aspects of communication confidentiality but does not prove that a payment instruction is legitimate.
Filtering and anomaly detection can identify suspicious sender relationships, unusual account activity, or unexpected payment language. Legitimate business exceptions and convincing impersonations limit the reliability of any single indicator.
Transaction controls
Independent verification of changed payment details addresses the fraud at the point of authorization. Its effectiveness depends on using an established contact route rather than contact details supplied in the suspicious request.
Other controls include separation of duties, multiple approvals for sensitive changes, and documented procedures for urgent exceptions. Training commonly emphasizes unexpected account changes, secrecy demands, and attempts to bypass normal approval channels. Poor grammar alone is not a reliable indicator: fraudulent messages can be fluent and contextually accurate.
Incident response and impact
BEC-related incident response has both financial and technical dimensions. Common activities include contacting affected financial institutions about possible recalls or holds, preserving messages and transaction records, identifying compromised accounts, revoking unauthorized access, and investigating forwarding rules or application permissions. Recovery is uncertain and depends partly on whether funds remain accessible.
A confirmed incident may also involve a data breach if an attacker accessed correspondence or obtained personal or confidential records. Reporting and notification obligations vary by jurisdiction and by the information involved.
Losses extend beyond the diverted payment. Organizations may face interrupted supplier relationships, exposed records, investigation costs, and disputes over responsibility. Aggregate loss estimates are difficult to compare because reporting systems use different definitions and incidents may go unreported. Reported losses therefore do not measure the full prevalence of BEC.