Microsoft Details Multi-Stage AiTM Phishing Campaign Targeting 35,000 Users

· Original article ↗

Summary

Microsoft analyzed an April 2026 phishing campaign that targeted more than 35,000 users with compliance-themed emails and PDF lures, leading to an AiTM flow designed to capture authentication tokens. Microsoft recommends email, browser, and phishing-resistant MFA mitig

Key points

  • Microsoft observed campaign waves from April 14–16, 2026, targeting more than 35,000 users across 13,000+ organizations in 26 countries.
  • Emails impersonated internal compliance communications and used PDF attachments to direct recipients through staged, CAPTCHA-gated pages.
  • The final “Sign in with Microsoft” step initiated an AiTM session-hijacking flow designed to capture authentication tokens and enable account access.
  • Microsoft confirmed the AiTM portion of the attack chain, but said it could not confirm the device-code-phishing stage suggested by some characteristics.
  • The final destination varied between mobile and desktop users; CAPTCHAs likely impeded automated analysis and sandboxing.
  • Recommended defenses include Safe Links and Safe Attachments, Zero-hour Auto Purge, network protection, SmartScreen, and phishing-resistant or passwordless authentication.

Article Details

Attack Vectors
  • Phishing emails impersonated internal compliance or regulatory communications and attached PDFs containing a “Review Case Materials” link.
  • The PDF link sent recipients to attacker-controlled domains with CAPTCHA-gated landing pages, followed by intermediate and final pages that varied their destination based on whether the user was on mobile or desktop.
  • Selecting “Sign in with Microsoft” initiated an adversary-in-the-middle authentication flow that proxied the session and captured authentication tokens.
  • Microsoft reported that attackers signed in with stolen valid entities; the article notes that the confirmed attack chain included AiTM, while the intermediate stage had hallmarks of device-code phishing.
Defensive Notes
  • Enable Zero-hour auto purge (ZAP), Safe Links, and Safe Attachments in Microsoft Defender for Office 365; use Threat Explorer to investigate and remove delivered phishing messages.
  • Enable network protection in Microsoft Defender for Endpoint and use browsers that support Microsoft Defender SmartScreen.
  • Prefer password-less or phishing-resistant authentication, such as Windows Hello, FIDO keys, or Microsoft Authenticator.
  • Configure automatic attack disruption in Microsoft Defender XDR and use Microsoft Defender detections and advanced hunting to investigate related activity.
  • Provide user awareness training and phishing simulations.

Indicators of compromise

TypeIndicatorContext
DOMAINacceptable-use-policy-calendly[.]deAttacker-controlled landing domain hosting malicious campaign content.
DOMAINcocinternal[.]comDomain identified as hosting sender addresses used for campaign emails; the article assesses the sending domains as likely attacker-controlled.
DOMAINcompliance-protectionoutlook[.]deAttacker-controlled landing domain hosting malicious campaign content.
DOMAINgadellinet[.]comDomain identified as hosting sender addresses used for campaign emails; the article assesses the sending domains as likely attacker-controlled.
DOMAINharteprn[.]comDomain identified as hosting sender addresses used for campaign emails; the article assesses the sending domains as likely attacker-controlled.
SHA25611420d6d693bf8b19195e6b98fedd03b9bcbc770b6988bc64cb788bfabe1a49dSHA-256 hash of a campaign PDF attachment containing a phishing link.
SHA2565db1ecbbb2c90c51d81bda138d4300b90ea5eb2885cce1bd921d692214aecbc6SHA-256 hash of a campaign PDF attachment containing a phishing link.
SHA256b5a3346082ac566b4494e6175f1cd9873b64abe6c902db49bd4e8088876c9eadSHA-256 hash of a campaign PDF attachment containing a phishing link.

MITRE ATT&CK

Vendors

Products

Countries

Industries

Related Articles