Identity & Email Incident Response

Tracing invoice fraud through mailbox rules and MFA changes

I reconstructed a Microsoft 365 mailbox compromise behind a fraudulent invoice, tracing phishing interaction, unauthorised MFA registration and inbox rules used to conceal activity.

Growing MSSP with Offensive ServicesHands-on identity and email investigation2 min read

An executive mailbox had been compromised and a fraudulent invoice had been paid. I needed to establish how the account was accessed, what the attacker changed and how far the abuse extended across Microsoft 365.

I built the access timeline from Azure sign-in logs and Office compliance records. After locating the first suspicious successful sign-in, I examined the mailbox for a related phishing message and used browser history to corroborate that the user had followed its link. Repeated failed sign-ins were also present, but did not establish the entry method.

I found an added MFA method and mail-filtering rules that could maintain account access and conceal messages. I reviewed audit activity for sensitive-file access and outbound email to scope the compromise beyond the known invoice-fraud conversation.

I supported reversal of the unauthorised account changes and provided recovery guidance. The known invoice-fraud conversation was the mailbox abuse identified in the records reviewed; the conclusion remained tied to the available account evidence.

Methods, evidence & technical decisions

Account persistence and message concealment

I investigated the additional MFA method and mail-filtering rules after suspicious account access. The method offered another way to maintain access, while the rules could conceal relevant messages. Recovery needed to address those account changes alongside the compromised credentials.

Open this detail ↗
Correlating identity, email and browser evidence

I connected Azure sign-in timestamps with Office compliance activity, located the suspected phishing message and corroborated interaction with its link through browser history. I then reviewed authentication-method changes, inbox rules, file-access activity and sent messages.

Open this detail ↗
Recovery and the observed scope

I supported reversal of the unauthorised changes and recovery guidance. The review identified the already-known fraudulent conversation as the mailbox abuse visible in the available records.

Open this detail ↗

Skills used in this work

This work connects to

SOC & incident response

Your exploration

Viewed history

Saved only in this browser.

Ask my portfolio

Ask about my work.

Ask about an investigation, a technology or my contribution. Answers link to the relevant case and technical detail.

Every answer links to the work.
How this works

When AI is connected, your question, recent questions and relevant published pages are sent to MiniMax to select supporting passages. Otherwise, this searches the site directly. Answers quote the saved website and link to their sources. This website does not save chat transcripts. Clearing or leaving the page clears this conversation.

Help improve this website

Report an issue

Spotted something broken or inaccurate? Tell me what happened and what you expected.