Redirected Wires, Hijacked Mailboxes, Microsoft 365 and Google Workspace
Did a Vendor Payment Go to the Wrong Account?
If money moved, call your bank immediately and ask it to contact the receiving bank. Then call GDF from a trusted phone. We trace the messages and payment instructions to investigate whether a mailbox was compromised or a sender was impersonated, and document the findings for your team, counsel and insurer.

The first hours
The First Hours After a Business Email Compromise
Tell us what you know so far: a payment that reached the wrong bank, an invoice your company never sent, a forwarding rule nobody created. In the first hours we lock down the account records that expire, map what the attacker could reach and give your response team a working picture of the incident while the trail is still warm. Global Digital Forensics has done this work since 1992, and our email practice has completed hundreds of compromised account analyses.

Preserve the records before they expire
Sign in logs, audit records, mailbox rules and message traces are preserved from the Microsoft 365 or Google Workspace tenant at once, because the provider’s retention clock started the moment the attacker logged in.
Trace the attacker through the account
We connect the phishing message, the unfamiliar sign in, the hidden inbox rule, the invoice thread and the altered payment instructions into one timeline your team can act on.
Arm the bank, the insurer and the legal team
You receive the technical findings, the timeline and the information inventory that a recall request, a cyber insurance claim and a notification assessment each depend on.
Contain the Account and Preserve the Evidence Together
The first call settles who does what: your incident contact, the examiner assigned to you, who holds the administrative rights to contain the account and how fast each step can happen. Containment and preservation then run together. An attacker who still holds a session can delete the records that prove what they did, and a response team that resets passwords without logging its own changes blurs the line between the intruder's actions and its own.
We then fix the affected accounts, the activity window and the messages and files in play. From there the work separates what the attacker could reach from what the records show they actually touched, because a message sitting in a mailbox is not proof it was read or taken, and every finding we report keeps those two apart.
Our email practice has collected thousands of mailboxes and completed hundreds of compromised account analyses for businesses and the law firms that represent them. When the matter calls for a full examination and expert report, our business email takeover forensics service carries the work forward. The records we preserve first are the ones Microsoft lists in its Purview audit log activities reference.
If the account is still open and the logs are still within retention, call (800) 868-8189 now and we will tell your administrator what to export before the reset.
If Money Moved, Call the Bank First
If funds were transferred, call your bank now and ask its fraud team to request a recall from the receiving institution, then report the incident to the FBI's Internet Crime Complaint Center at ic3.gov. Neither step should wait for a forensic report. The examination runs in parallel and produces what the bank and the insurer ask for next, and the first hours matter most for getting money back. The FBI's business email compromise guidance sets out the reporting path.
Once the bank has the recall request, get incident help now and preservation starts alongside the recovery effort.
Inside Your Account or Impersonating It
You usually hear about it from outside. A customer asks why your company sent an odd message, a vendor says the bank details on your invoice changed, or your own team finds sent items nobody wrote, missing mail and a forwarding rule nobody recognizes. Each is a symptom, and the first job is to establish which problem you actually have.
We compare the original messages with the account's own records to decide whether someone was inside your Microsoft 365 or Google Workspace account or impersonating it from a forged sender address or a lookalike domain. The two call for different responses, and the right diagnosis saves hours you do not have.
When the evidence shows a genuine intrusion, we identify every message the intruder sent, forwarded, deleted or changed and tie each one to the sign in, session and rule activity behind it. Your team gets a supported sequence of events with every account involved named.
Trace the Altered Invoice Back to the Attacker
A fraudulent payment request works because it arrives inside a real conversation, from a real address, just as an invoice falls due. Preserve the original messages, every version of the invoice, the payment instructions and the transaction records now, in native email format. Screenshots and pasted text lose the headers and identifiers that prove where a message came from.
Before any further payment goes out, confirm the instructions by calling a contact you already know at a number you already trust, never the number in the suspicious message.
We then lay the email and account evidence against the payment timeline to show how the instructions changed hands and which events the records support. An unfamiliar IP address alone does not name a person, so we corroborate with independent records before we tell you who did what.
Find the Access That Survives a Password Reset
A new password closes one door. An attacker who has lived in a mailbox for weeks leaves others open: active sessions and tokens, added authentication methods, consented applications, forwarding and inbox rules, delegated access and administrator changes. We work alongside your IT department or managed service provider, pairing their knowledge of your environment with our Microsoft 365 and Google Workspace compromise analysis.
We examine each persistence route to establish how access began and what still has to be revoked. Restoring email service proves the mailbox works again; our findings show whether the intruder is gone, which is the point your insurer will ask about.
Contain first and preserve as you go. Keep a running log of every response action and the time it happened so the examination can separate your team's work from the attacker's. Microsoft's guide to responding to a compromised email account in Microsoft 365 and Google's guide to identifying and securing compromised Workspace accounts describe the platform steps.
Before the response team closes the ticket, read Five Mistakes That Destroy Digital Evidence Before We Arrive, because a tidy cleanup can erase the record of how the attacker stayed in.
Pin Down How the Attacker Got In
Every business email compromise starts somewhere specific: a phishing page that captured a password and a session, a targeted message to the controller, a fake IT support call, credentials exposed in an earlier breach, an authentication prompt approved by a tired employee or an application permission nobody questioned. We test each candidate route against the messages, sign in records, security settings and relevant device evidence until the record supports one account of how the compromise began and continued.
The report turns the entry route into specific fixes: stronger authentication, tighter application permissions, better account recovery and help desk verification, and independent confirmation of any change to payment details. Closing the door the attacker actually used is the most practical protection against the next attempt.
The FBI public service announcement Cyber Criminals Target Victims Using Social Engineering Techniques describes the phishing and help desk impersonation behind many of these incidents.
Personal and Patient Information Exposure, Documented for Notice
A compromised mailbox rarely holds only invoices. It holds personnel files, patient correspondence, attachments and links into other business systems. Whether that content was present and whether the attacker reached it are separate questions, and notification counsel needs both answered with evidence.
Within the agreed scope we examine mailbox access, forwarding, downloads and other activity, then review the relevant messages and attachments for personally identifiable information, or PII, and protected health information, or PHI. We document the information and the people potentially affected, and we mark exactly where logging and retention gaps sit so no one mistakes an absence of logs for an absence of access.
You receive the timeline, the findings and a scoped information inventory: the evidence a notification decision rests on.
For organizations subject to HIPAA, the inventory supplies the technical facts for the breach notification assessment described in HHS breach notification guidance.
If a notification deadline is already running, call (800) 868-8189 and ask for the affected information inventory to be scoped first.
Turn Your Own Incident Into Training
The people who approve payments, reset passwords and answer the help desk line are the targets, so training has to reach executives and finance staff as well as everyone else. The material that works comes from your own incident: the actual message, the actual call, the actual authentication prompt, shown to the people who will see the next version of it.
Give employees a fast, blameless way to report a concern even after they clicked the link or approved the request, because the hours between the click and the report are the hours the attacker uses. Reinforce independent verification of every sensitive request through a contact method you already trust, and fold the lessons from the examination into procedures, policies and technical controls. NIST's NIST Small Business Cybersecurity Corner: Phishing is a practical starting point.
What the Examination Delivers
Business email compromise, or BEC, covers the frauds that misuse trusted business communications: some run from inside a mailbox the attacker controls, others by impersonation from outside. The examination brings the messages, the account activity and the business events into one supported account of what happened, built from the evidence your tenant retained.
The original emails, headers and attachments establish what was communicated and preserve details that screenshots and pasted text lose. Microsoft 365 or Google Workspace sign in and audit records reconstruct who accessed the account, from where and when. Mailbox activity, forwarding rules, application permissions and security changes expose unauthorized actions and the persistence left behind. Initial access and persistence analysis names the controls your response team has to address, and a correlated timeline ties the account activity to the email, invoice and payment events that cost your business money.
Where the mailbox held sensitive content, review of the relevant messages and attachments identifies personal and patient information within the defined population, and an affected information inventory gives counsel the evidence for the reporting assessment. The written report explains each finding, the records behind it and the corrections we recommend. For the full collection and reporting process, see Email and Microsoft 365 Forensics.
Describe what you are seeing and a senior responder will set the first steps.
GDF does not accept pro se litigation cases, and GDF may decline matrimonial or family law cases at our discretion.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .