Common BEC tactics are the recurring methods criminals use in business email compromise, a form of fraud where attackers trick employees into sending money or sharing sensitive information. Most of these scams succeed not through technical breaking-in but through believable messages that exploit trust and routine.
This guide explains the patterns behind these schemes in plain terms. Understanding how they are built makes it easier for staff, managers and business owners to pause, verify and report suspicious requests before any funds or data are lost.
Why Attackers Rely on Ordinary Business Routines
Business email compromise, often shortened to BEC, is a type of fraud in which a criminal impersonates a trusted person or company to redirect payments or obtain confidential data. The attacker usually does not need malware; a convincing email and a plausible reason to act are often enough.
Attackers study how organizations communicate. They look for who approves invoices, who handles payroll, and how executives typically ask for help. Public websites, professional networking profiles and leaked email threads can reveal these details.
Routine work creates openings. Month-end payments, vendor onboarding and changes to bank details are normal tasks, so a request tied to one of them may not look unusual. Criminals time their messages around these moments.
Recognizing that the scheme depends on normal behavior helps explain why verification steps matter. A procedure that treats even familiar requests with a short check can interrupt the attacker’s plan.
How Spoofed and Lookalike Email Addresses Work
Spoofing means forging the sender information in an email so it appears to come from a known person. Some attackers use this technique, though many modern mail systems flag or block obvious forgeries. Others rely on lookalike addresses instead.
A lookalike address changes one character or adds a word, such as a domain that swaps a letter or uses a different ending. At a glance, an employee may read the name and assume the message is genuine without checking the full address.
Display names are another common trick. An email may show a familiar name in the sender field while the actual address belongs to an unrelated account. Viewing the full address in the message details reveals the difference.
Email authentication standards such as SPF, DKIM and DMARC can reduce spoofing for an organization’s own domain, but they do not stop every lookalike domain. Careful reading of addresses therefore remains an important human check.
Common Warning Signs in Suspicious Requests
Certain features appear repeatedly in messages used for business email compromise. Checking for these signs can help staff decide when to slow down and confirm a request through a separate channel.
- A sudden change to bank account or payment instructions for an existing vendor or employee
- Pressure to act quickly, keep the request secret, or skip the usual approval steps
- A request from an executive that arrives outside normal hours or from an unfamiliar address
- Unusual payment amounts, new recipients, or requests to send gift cards or wire funds abroad
- Messages that avoid direct phone contact or insist that all communication stay in email
None of these signs proves fraud on its own, since legitimate changes and urgent requests do happen. Together, however, they form a pattern worth checking. When several appear in one message, the safest response is to stop, verify the request using a contact method you already trust, and involve a supervisor before taking action.
Vendor Impersonation and Payment Redirection
One of the most common BEC tactics involves impersonating a supplier. An attacker may have access to a real email thread between a company and a vendor, then step into the conversation at the right moment with a message about updated payment details.
The new instructions often point to a different bank account, sometimes in another country. Because the message appears to continue an existing exchange, the employee may treat it as routine paperwork rather than a warning sign.
Fake invoices are a related approach. The attacker sends a bill that looks like it came from a known supplier, sometimes with a logo and formatting copied from genuine documents, and asks that it be paid to a new account.
Businesses can reduce this risk by confirming any change to payment details through a phone number already on file, not one supplied in the message, and by requiring a second approver for changes to vendor records.
Executive Impersonation and Other Targeted Approaches
Some attackers aim directly at senior leaders or at people who can move money. Impersonating an executive, often called CEO fraud, uses authority as the pressure point, while other variants target lawyers, human resources staff or accounting teams.
How Executive Impersonation Typically Unfolds
In a typical executive impersonation, an attacker poses as a chief executive, chief financial officer or another senior leader. The message may say that a confidential acquisition or urgent payment needs attention before the end of the day.
The request often asks the recipient to keep the matter quiet and to bypass normal approval channels. Staff may feel reluctant to question a senior person, which is exactly what the attacker counts on.
A hypothetical example: an accounts payable clerk receives an email that appears to come from a manager asking for an urgent transfer to a new supplier. The clerk who calls the manager on a known number discovers the request was never sent.
Targeting Human Resources and Payroll
Attackers also send requests to human resources and payroll teams. A message may ask for a change to the direct deposit details of an employee, sometimes claiming the worker has recently changed banks or is traveling.
If accepted without verification, the change can redirect a paycheck to an account controlled by the criminal. Because the request concerns a real person, it may appear ordinary to busy staff.
Organizations can protect against this by verifying changes with the employee through an established channel and by keeping a record of any update to pay details.
Attacks on Legal and Real Estate Transactions
Real estate closings and legal settlements involve large sums and many parties, which makes them attractive to criminals. A message may appear to come from a title company, attorney or escrow agent with new wiring instructions shortly before a transfer.
Because buyers and sellers often expect instructions by email, the change may not be questioned. Practitioners in these fields commonly recommend confirming wiring details by phone using a number obtained independently.
Specific procedures and responsibilities vary by jurisdiction and by contract, so anyone involved in a large transaction should consult the relevant professionals and their own written policies.
How Attackers Gain Access to Email Accounts
Some BEC tactics begin with taking over a real mailbox. Phishing emails that imitate a login page can capture a password, and reused credentials from older data breaches may allow an attacker to sign in to an account without any guesswork.
Once inside, the attacker may read existing conversations, learn who handles payments, and set up hidden forwarding rules that copy incoming messages to an outside address. Some criminals also add their own email address to a mailbox as an alternate contact so they can intercept reset codes.
Because the activity happens inside a genuine account, messages sent from it may pass standard checks. This is why an unusual change to account settings deserves attention even when the email itself looks normal.
Protecting accounts with multi-factor authentication, unique passwords and regular review of forwarding rules makes this route considerably harder for attackers to use.
Verification Habits That Interrupt These Schemes
The most effective defense against common BEC tactics is a simple verification habit. Before acting on a request to change payment details or send funds, the recipient confirms it using a channel that the attacker does not control.
Calling a known phone number, rather than replying to the email or using a number listed in the message, is a widely recommended approach. Some organizations also use a short internal code word for sensitive requests, although any shared phrase should be kept confidential.
Written procedures help make verification routine rather than awkward. When a policy states that all payment changes require a second approver and a call-back, employees are less likely to feel they are accusing a colleague.
Staff should also feel safe to say no or to delay. A culture where questioning an unusual request is praised, not penalized, removes much of the pressure these schemes depend on.
Steps to Take When a Suspicious Request Arrives
If an employee suspects a message may be part of a business email compromise, prompt and calm action can limit the damage. The following steps are commonly recommended as a starting point for an internal response plan.
- Do not send money, change payment details or share credentials until the request is verified
- Contact the supposed sender using a phone number or channel already on record
- Notify a supervisor, the finance team or the security contact as soon as possible
- Preserve the original email and its full headers so they can be reviewed later
- If funds may have been sent, contact the bank immediately and ask about recall options
Reporting matters even when the request was caught early, because patterns across an organization help security teams spot campaigns. Depending on the situation, reporting to law enforcement or a fraud reporting center may also be appropriate. Rules about notification duties differ by state, industry and contract, so organizations should check with qualified legal or compliance advisers.
Building a Practical Defense Plan Going Forward
A useful next step is to map where payment decisions are made in your organization. Identify who can change vendor bank details, who approves transfers and which requests arrive by email alone. These points are where verification should be strongest.
Training works best when it uses realistic examples drawn from your own workflows. Short, regular sessions that walk staff through a made-up payment change can build familiarity without overwhelming busy schedules.
Technical controls complement these habits. Multi-factor authentication, email filtering, and authentication standards for your domain each reduce exposure, though none replaces a person pausing to confirm an unusual request.
Review your procedures after any near miss and update them as vendors, staff and tools change. Treating common BEC tactics as an ongoing risk, rather than a one-time problem, keeps defenses aligned with how criminals actually operate.