If business email is being used to send fraudulent requests or divert payments, contact your bank immediately if money is at risk and involve the email administrator. Secure affected accounts from a trusted device, end unauthorized access and preserve messages and logs where practical.
Business Email Compromise: How to Respond to Fraud or a Hacked Inbox

Jump to a section
Business email compromise can involve a genuinely hacked mailbox, an impersonated sender or a combination of both. An invoice with changed bank details does not by itself prove which account was compromised. Investigate the evidence while stopping active harm.
Make the first decisions in parallel
- Money sent or at risk: call the originating bank on a trusted number and ask whether the payment can be stopped or recalled. Independently verify the instructions with the genuine recipient.
- Mailbox may be accessed: involve an authorized administrator. Block unauthorized access and revoke sessions where supported; use a device that is not suspected compromised.
- Others may be targeted: use a trusted channel outside the affected conversation to coordinate with staff, suppliers or customers who may have received false instructions.
- Keep evidence where safe: retain original messages, payment records, alerts and relevant logs without delaying containment.
The FBI's business email compromise guidance advises contacting the originating bank promptly and requesting a recall. A recall or reimbursement is not guaranteed. The diverted-invoice checklist covers the payment record in more detail.
Match the response to what happened
If you only received a suspicious message, report it without replying or using its links. Receipt alone does not prove an account was accessed. If someone entered credentials or approved an unexpected sign-in or app, contact the administrator promptly and identify what was shared or approved. If money was sent, call the bank immediately even while the email investigation continues.
Secure the mailbox and its recovery routes
Work with the provider or administrator to change affected credentials, secure recovery methods and end active sessions or revoke tokens where the service supports it. Review mailbox forwarding, inbox rules, delegates, unfamiliar devices and connected applications. Record relevant details before removing unauthorized changes when practical, but do not leave an attacker active merely to collect evidence.
A password change may not remove an unauthorized app or forwarding rule. Microsoft's compromised-account guidance describes these checks for Microsoft 365. Provider settings and administrator permissions vary.
Find out what happened without guessing
Compare the full sender and reply-to addresses with previously verified details. Preserve original messages rather than relying only on screenshots when possible. Ask the administrator to review sign-in and mailbox activity, changes to payment instructions and the period in which the attacker may have had access.
A lookalike address can impersonate a supplier without entering its mailbox. Conversely, a legitimate address does not prove the sender is in control. Separate verified findings from questions that remain open, and do not accuse a supplier or employee based on the message alone.
Tell the right people through a trusted channel
If fraudulent messages were sent from a genuine account, identify who received them and warn affected contacts using independently verified details. Tell them which request to disregard and how to confirm genuine payment instructions. Avoid sending sensitive account records or unnecessary personal data in the warning.
Where employee or customer information may have been accessed, involve your privacy or legal adviser. Notification duties and deadlines depend on the facts and jurisdiction. In the United States, the FBI's Internet Crime Complaint Center accepts reports; use relevant local authorities elsewhere.
Restore trust in the payment process
Pause disputed changes to supplier details until they are checked through a known number or independently established channel. Review recent approvals and other payments that used the affected conversation. A second person approving the same unverified email is not independent verification.
For an affected Microsoft 365 administrator, use the Microsoft 365 business recovery guide. If the event involves other systems as well, use first steps after a business hack.
The response is complete only when unauthorized access is addressed and the business can distinguish genuine instructions from the altered ones. Keep monitoring and follow up on unresolved findings with the provider and bank.