Attack Chain

1. The attacker sends a phishing email to the victim, impersonating a legitimate service.
2. The email contains a link that redirects the victim to a fake application authorization page.
3. The fake page prompts the victim to enter a device code.
4. Unbeknownst to the victim, the device code is associated with a malicious OAuth application controlled by the attacker.
5. The victim is redirected to a legitimate Microsoft login page, where they enter the provided code and authenticate.
6. Upon successful authentication, the malicious application receives an access token.
7. The attacker uses the access token to access the victim’s account and sensitive data.
8. The attacker may then perform actions such as reading emails, accessing files, or initiating further malicious activity within the compromised account.

Impact

This OAuth device code phishing campaign affected numerous organizations across multiple sectors and regions in early April 2026. Successful attacks grant threat actors unauthorized access to user accounts, potentially leading to data exfiltration, financial fraud, and further compromise of internal systems. Due to the nature of OAuth, attackers can maintain persistent access even after password changes, posing a significant long-term risk.

Recommendation

• Monitor Azure AD sign-in logs for device code flow usage to identify suspicious authentications (logsource: azuread, category: authentication).
• Implement the Sigma rule provided below to detect suspicious application registrations in Azure AD (logsource: o365, category: configuration).
• Educate users on the risks of device code phishing and how to identify malicious authorization requests.
• Regularly audit OAuth applications authorized within your environment and revoke access for any suspicious or unused applications.
• Investigate any alerts related to anomalous OAuth application activity promptly.