Business email compromise response: protect access, safety, and evidence first
Business email compromise can use a stolen mailbox, lookalike domain, altered invoice, compromised supplier, phone impersonation, or fake executive request. The email can appear normal because attackers often study real payment timing and conversation history.
The response has two clocks: payment recovery and technical containment. Neither should wait for the other. A finance owner can contact banks while an administrator preserves mail evidence, revokes sessions, and checks whether the attacker changed rules or delegated access.
Act on the payment while preserving the mailbox evidence
Contact the financial institution promptly through a known route, while retaining the suspicious message, headers, payment details, approval path, and relevant mailbox events. Verify suppliers or executives using saved contact information outside the affected thread.
Work in this order unless immediate safety changes it
Activate the payment response
Contact the bank or payment service immediately, request a recall or fraud hold, identify the receiving institution, and preserve every case and transaction reference.
Secure and preserve the mailbox
From a trusted device, reset credentials, revoke sessions and tokens, remove unknown rules or delegates, retain the messages and headers, and review administrator changes.
Map the affected conversation
Identify suppliers, customers, invoices, attachments, approvals, and people exposed during the access window. Confirm legitimate payment details by another channel.
Notify and report
Tell affected partners exactly which address or invoice was compromised and how future requests will be verified. Follow insurer, legal, regulator, bank, and cybercrime reporting duties.
Change the approval design
Require known-channel verification for bank-detail changes, separate request and approval roles, alert on mailbox rules, and rehearse the process with finance and support staff.
Let the signal determine the next owner
| Signal or evidence | What may be happening | Response or owner |
|---|---|---|
| Supplier email was genuine | The supplier mailbox may be compromised | Both organizations should contain their accounts and verify all open invoices and detail changes |
| Transfer is still pending | There may be a narrow intervention window | Keep the bank on the line, follow its fraud process, and do not wait for an internal meeting |
| Lookalike domain was used | Other staff or customers may receive similar requests | Preserve the domain and headers, warn targeted contacts, and use reporting or takedown routes |
| Attacker changed forwarding rules | Mail may still be copied after a password reset | Remove persistence, revoke sessions and apps, inspect administrator logs, and monitor for renewed rules |
Close the route back in and watch for downstream harm
Verify the transaction outside email
Replying to the thread may reach the attacker. Use a saved supplier number, contract contact, or independently verified directory entry.
Preserve headers and payment records
Screenshots help people read the event, but original messages, headers, invoices, beneficiary details, approvals, and bank references support investigation.
Assume the conversation was observed
If an attacker read the mailbox, changing one password does not reveal what invoices, contacts, tokens, rules, and documents were copied.
Repair the business process
MFA helps account security, but payment controls must also resist a convincing message sent from a real compromised account.
Verify the payment and the mailbox as two connected incidents
A fraudulent invoice or bank-change message may come from a compromised mailbox, a lookalike domain, a hijacked conversation, or information gathered elsewhere. Preserve the full message and headers where possible, but do not delay contacting the financial institution when a transfer may still be stopped or recalled.
Use a saved phone number or established contact to verify the supplier, executive, or employee. Do not use contact details included in the suspicious thread. Record the amount, destination, approval path, message times, mailbox accounts involved, and people notified so finance, technical, legal, and insurance work stays coordinated.
Review the business process as well as the account. Remove malicious rules and sessions, secure recovery channels, inspect delegated access and connected apps, and search for related messages within the evidence boundary. Then add independent verification for payment-detail changes and unusual transactions, with a clear exception and escalation route.
What people ask while responding
Should we ask the recipient to return the money ourselves?+
Coordinate with the bank and investigators first. An attacker may provide new instructions, and direct contact can complicate recovery or evidence.
Does MFA prevent business email compromise?+
It reduces many account-takeover paths, especially when phishing-resistant, but cannot stop every stolen session, compromised supplier, lookalike domain, or manipulated payment process.
When should customers be told?+
Notify people whose payments, accounts, or decisions may be affected as soon as the facts and safe verification route are clear. Legal and contractual advice may set additional duties.
Continue the recovery beyond this incident
Business risk spreads through people, suppliers, data, and recovery dependencies. Use the Business cybersecurity basics hub for the complete topic pathway, then continue with Small-business incident response plan, Password managers, and Employee security training.
Keep bank contacts, mailbox changes, supplier notices, and decisions in an incident evidence log.
Confirm live response details here
Sources for Business email compromise response
Confirm current instructions and limits for this specific task before acting.
