How to Defend Against AitM Phishing Attacks Targeting US Organizations
Introduction
Cybercriminals are constantly refining their tactics, and a recent wave of sophisticated phishing campaigns has emerged, specifically targeting US organizations. These attacks use emails that claim to contain a conduct report, tricking recipients into visiting a convincing Microsoft phishing website. The site employs an Adversary-in-the-Middle (AitM) technique to intercept credentials and bypass multi-factor authentication. This guide provides a step-by-step approach to recognizing, preventing, and responding to such threats—helping you safeguard sensitive data and maintain organizational security.

What You Need
- Basic understanding of email security protocols (SPF, DKIM, DMARC)
- Access to your organization’s email filtering or security tools
- Awareness of your company’s incident response plan
- Multi-factor authentication (MFA) enabled on all accounts (preferably hardware-based or app-based)
- Regularly updated web browser and security software
- Training materials for end users (optional but recommended)
- Ability to report suspicious emails to your IT/security team
Step-by-Step Defense Guide
Step 1: Understand the Attack Vector
Before you can defend against a threat, you must know how it works. In this campaign, attackers send emails that appear to come from a trusted source—often mimicking internal HR or compliance departments. The email contains an attachment or link claiming to be a conduct report. When the victim clicks the link, they are redirected to a counterfeit Microsoft login page. Unlike traditional phishing, this page uses an AitM proxy: it sits between the user and the real Microsoft service, capturing credentials and session cookies even if MFA is used. The attacker can then use those tokens to access accounts in real time.
- Key takeaway: AitM attacks are more dangerous because they bypass standard security measures.
- Action: Educate yourself and your team about AitM so you can spot suspicious login flows.
Step 2: Identify Suspicious Emails
The first line of defense is your inbox. Look for red flags in any email claiming to include a conduct report. Common indicators include:
- Urgent or threatening language (e.g., “Immediate action required” or “Violation report enclosed”).
- Mismatched sender addresses (e.g., sender@micorsoft-security.com instead of microsoft.com).
- Generic greetings like “Dear Employee” instead of your name.
- Unexpected attachments or links, especially from someone you don’t normally communicate with.
- Poor grammar or spelling errors, though these have become less common in sophisticated attacks.
Even if the email looks legitimate, never trust it blindly. Hover over any link without clicking to see the actual URL – if it contains unusual characters or doesn’t match microsoft.com, it’s malicious.
Step 3: Verify URLs Before Clicking
Attackers often use lookalike domains or subdomains to trick you. For example, the link might be “microsoft-login.secure-verify.com” instead of “login.microsoftonline.com”. To stay safe:
- Always manually type the known genuine URL (like login.microsoftonline.com) into your browser instead of clicking links.
- Use a bookmark for critical services like Office 365 or Azure.
- Check the page URL after the page loads: A phishing site may redirect or display a spoofed address bar.
- Look for HTTPS and a padlock icon, but be aware that AitM proxies can also use valid certificates—don’t rely on this alone.
If you are unsure, contact your IT department or the sender via a different channel (e.g., phone call) to confirm the email’s legitimacy.
Step 4: Use Multi-Factor Authentication (MFA) Wisely
MFA is not a silver bullet against AitM attacks, but using better forms can help. Here’s what to do:

- Prefer hardware security keys (e.g., YubiKey) or FIDO2/WebAuthn. These resist AitM because they tie authentication to a specific domain and cannot be replayed by a proxy.
- If your organization uses app-based or SMS MFA, treat any unexpected prompt as suspicious. If you receive a push notification you didn’t initiate, deny it and report it immediately.
- Implement conditional access policies. For example, require MFA only from trusted locations or devices, and block logins from untrusted IP ranges.
- Use ‘number matching’ in Microsoft Authenticator to reduce accidental approval of fraudulent requests.
Remember: No single security control is perfect. Combine MFA with other steps for layered defense.
Step 5: Report and Educate
If you encounter a phishing email, don’t ignore it. Take action:
- Forward the email to your security team or use your organization’s phishing reporting button (often found in Outlook).
- Do not reply, click, or download anything from the email.
- After reporting, delete the email.
- If you accidentally clicked a link or entered credentials, immediately change your password, revoke active sessions, and notify IT.
Finally, promote a culture of security awareness: conduct regular phishing simulations, share real-world examples, and encourage employees to speak up if something feels off. A vigilant workforce is your strongest defense.
Tips for Long-Term Protection
- Keep software updated: Patch browsers, email clients, and security tools regularly to close vulnerabilities that AitM proxies might exploit.
- Use DNS filtering: Block known malicious domains at the network level to prevent access to phishing sites.
- Implement DMARC: This email authentication protocol helps prevent spoofing of your organization’s domain, reducing the chances of your own employees receiving similar phishing lures.
- Monitor for anomalous logins: Enable alerts for logins from unusual locations or devices.
- Backup critical data: In case of a successful breach, regular backups minimize damage from ransomware that often follows credential theft.
- Stay informed: Follow trusted sources like SecurityWeek for updates on evolving threats.
By following these steps, you can significantly reduce the risk posed by sophisticated AitM phishing campaigns. Remember, security is a continuous process—stay vigilant, stay educated, and stay protected.
Related Articles
- Defending the Code Pipeline: GitHub’s Rapid Response to a Critical RCE Vulnerability
- 13 Years After Snowden: Ex-NSA Chief Chris Inglis on Regrets, Insider Threats, and Cultural Failures
- Amazon SES Phishing: How Attackers Exploit Trusted Email Infrastructure
- How to Leverage Frontier AI for Browser Vulnerability Hunting: A Step-by-Step Guide
- Critical Security Patch: Google Resolves Maximum-Severity Flaw in Gemini CLI and GitHub Actions Integration
- China-Linked Hackers Breach Asian Governments, NATO Ally, Journalists in Coordinated Cyber Campaign
- Fortifying Your Enterprise Against AI-Powered Vulnerability Discovery and Exploitation
- Everything About Learning from the Vercel breach: Shadow AI & OAuth sprawl