Business email compromise explained: when a work email asks for money
BEC emails often arrive as plain text, so filters have little to catch. How the impersonation works, and the verification habit that reduces the risk.
Picture an email attack and you probably imagine something trying to sneak past your filters - a malicious link, an infected attachment. Business email compromise often skips all of that. IC3, the FBI's Internet Crime Complaint Center, defines BEC as a sophisticated scam targeting businesses and individuals performing a transfer of funds, usually carried out by compromising a legitimate business email account through social engineering or computer intrusion. The result is an unauthorized transfer of funds - and because the email itself is often plain text, there is little for a filter to catch.
Why filters miss it
Cloudflare's analysis of BEC campaigns explains why they so often slip through. They are extremely low-volume, sometimes just one or two emails, so they can evade the volume-based detection signals those tools watch for. They often contain no malware, links or attachments - typically nothing but a few lines of text. They are personalized to the victim after research into the organization, sometimes arriving inside an already-existing email thread. They may even come from a real, previously compromised inbox - and mail from a genuinely compromised account can pass DMARC legitimately, when it authenticates and aligns with the real domain. The reverse case needs care: per dmarc.org, a domain's DMARC policy (none, quarantine or reject) only tells receivers what to do with mail that fails the alignment check - a lenient policy leaves failing mail deliverable, it does not make it pass.
The anatomy of the ask
What the email wants is almost always the same: money moved, gift cards purchased, or data handed over. Cloudflare lists the recurring elements. Time pressure - "urgent", "quick", "before close of business". An authoritative sender, usually someone senior. A plausible-sounding reason for the request. Specific instructions - exact amounts and destinations, which read as more legitimate than vague ones. And often a direction not to contact the purported sender or anyone else, because one phone call collapses the whole scheme.
The checks that stop it
The defenses are procedural more than technical. IC3's core advice: verify requests for changes in account information through secondary channels or two-factor authentication - a callback to a number you already have, not the one in the email. Check the sender's actual address, especially on mobile, where mail clients often show only a display name. Turn on full email-extension views so a disguised attachment type cannot hide. And monitor financial accounts for irregularities like missing deposits. Cloudflare adds the human layer: treat unusual, unexpected or sudden requests as a signal to verify with the purported sender through another channel, and report suspected BEC to whoever handles security - secure email gateways alone struggle with exactly these emails.
If the money already moved
Speed decides whether the loss is recoverable. IC3's steps: contact the originating financial institution as soon as the fraud is recognized and request a recall or reversal, along with a Hold Harmless Letter or Letter of Indemnity - acting quickly may reduce or eliminate the loss. Then file a detailed complaint at ic3.gov, including the banking information. IC3 also publishes alerts on active BEC trends targeting specific sectors.
The calm version
BEC works because it looks like work - a short, plausible email from someone you trust, asking for something you could plausibly do. The strongest countermeasure is a habit, not a product: any request that moves money or changes payment details gets verified through a channel you already trust, no matter who appears to be asking. Verification reduces the risk rather than eliminating it - a request from a genuinely compromised account can still look convincing - which is why the bank-recall steps above matter as a backstop.
Sources: IC3's Business Email Compromise page (definition, protection tips, bank-recall and complaint steps) and Cloudflare's "What is business email compromise?" (why filters miss BEC, email anatomy, gateway limits, verification and reporting advice); dmarc.org's DMARC overview (how alignment and policy enforcement actually work).
Frequently asked questions
What is the difference between BEC and regular phishing?
Phishing casts a wide net with links or attachments; BEC is a targeted, personalized social-engineering attack - usually a few lines of plain text impersonating someone specific, often a senior figure, after research into the organization.
Why do BEC emails ask for gift cards?
Gift-card purchases are a documented BEC pattern - Cloudflare's worked example is exactly that. But IC3's definition covers any transfer of funds, so the ask can just as easily be a wire transfer or a change to supplier payment details.
Does DMARC stop BEC?
Partly. DMARC checks whether mail authenticates and aligns with the sender's domain, and an enforced policy (quarantine or reject) tells receivers to act on mail that fails - which helps against direct spoofing of the domain. But a monitoring-only policy (p=none) leaves failing mail deliverable, and mail from a genuinely compromised account can pass legitimately. That is why the procedural checks above matter as much as the protocol.
Is BEC only a big-company problem?
No. IC3 defines BEC as targeting both businesses and individuals performing transfers of funds, and any business that pays invoices by email fits the profile.