Anavem
Languagefr
Laptop screen showing fake Microsoft login page in dark office setting

EvilTokens Kit Targets Microsoft Accounts with Device Code Phishing

New EvilTokens malicious toolkit exploits device code phishing to hijack Microsoft accounts for business email compromise attacks.

1 April 2026, 21:42 5 min read

Last updated 2 April 2026, 02:00

SEVERITYHigh
EXPLOITActive Exploit
PATCH STATUSUnavailable
VENDORMicrosoft
AFFECTEDMicrosoft 365, Azure Active Di...
CATEGORYCyber Attacks

Key Takeaways

EvilTokens Kit Emerges as Advanced Microsoft Account Hijacking Tool

Cybersecurity researchers discovered a sophisticated malicious toolkit called EvilTokens on April 1, 2026, designed specifically to exploit Microsoft's device code authentication flow for account takeover attacks. The kit represents a significant evolution in phishing techniques, moving beyond traditional credential harvesting to abuse legitimate OAuth authentication mechanisms built into Microsoft's ecosystem.

Device code phishing exploits Microsoft's device code flow, a legitimate authentication method designed for devices without web browsers or input capabilities. The attack begins when threat actors send phishing emails containing malicious links that redirect victims to fake Microsoft login pages. These pages prompt users to visit the legitimate Microsoft device login portal and enter a device code, creating the illusion of a secure authentication process.

The EvilTokens kit automates this entire attack chain, providing cybercriminals with pre-built phishing templates, token management systems, and post-compromise tools for business email compromise operations. Security researchers from The Hacker News documented how the toolkit integrates multiple attack vectors into a single platform, making sophisticated Microsoft account hijacking accessible to less technical threat actors.

What makes EvilTokens particularly dangerous is its ability to bypass traditional security measures. Since the authentication occurs through Microsoft's legitimate device code portal, the process appears normal to both users and security monitoring systems. The toolkit captures OAuth tokens that provide persistent access to victim accounts, often maintaining access even after password changes.

Related: Dutch Police Confirm Phishing Attack Breach

Related: Russian APT TA446 Targets iOS with DarkSword Exploit Kit

Related: PayPal Amazon Phishing Campaign Targets Customer Support

Related: GitHub Accounts Breached in VS Code GlassWorm Aftermath

The kit includes advanced features for post-compromise activities, including automated email forwarding rules, mailbox searching capabilities, and tools for conducting convincing business email compromise attacks. Researchers noted that EvilTokens appears designed specifically for financial fraud operations, with built-in templates for invoice fraud and wire transfer scams targeting corporate finance departments.

Microsoft 365 Organizations Face Widespread Exposure Risk

All organizations using Microsoft 365, Azure Active Directory, and Office 365 services are potentially vulnerable to EvilTokens attacks. The toolkit specifically targets business accounts rather than personal Microsoft accounts, focusing on environments where successful compromise can lead to significant financial gain through business email compromise schemes.

Enterprise customers face the highest risk, particularly organizations in finance, healthcare, legal services, and manufacturing sectors that regularly process large financial transactions via email. The device code authentication flow is enabled by default across Microsoft's business platforms, meaning virtually every Microsoft 365 tenant is exposed to this attack vector without additional security controls.

Small and medium businesses represent prime targets for EvilTokens operators due to typically weaker security awareness training and limited security monitoring capabilities. These organizations often lack the advanced threat protection features available in Microsoft's higher-tier security offerings, making detection and prevention more challenging.

The attack's effectiveness doesn't depend on specific software versions or configurations, as it exploits the fundamental design of Microsoft's device code authentication system. Organizations using multi-factor authentication aren't immune, since the device code flow can bypass traditional MFA implementations when users are tricked into completing the authentication process themselves.

Defending Against Device Code Phishing and EvilTokens Attacks

Organizations must implement multiple defensive layers to protect against EvilTokens and similar device code phishing attacks. The primary defense involves disabling device code authentication flow entirely for organizations that don't require it. Microsoft administrators can disable this feature through Azure Active Directory conditional access policies or by modifying application registration settings to prevent device code grant types.

For organizations that must maintain device code authentication, implementing strict conditional access policies becomes critical. These policies should require device compliance, restrict access from unknown locations, and mandate additional verification steps for device code authentications. Microsoft's CISA Known Exploited Vulnerabilities catalog provides additional guidance on securing OAuth authentication flows.

Security teams should monitor Azure AD sign-in logs for suspicious device code authentication attempts, particularly those originating from unusual geographic locations or occurring outside normal business hours. Microsoft's Cloud App Security platform can detect anomalous authentication patterns and automatically block suspicious device code requests.

User education remains crucial for preventing successful EvilTokens attacks. Organizations should train employees to recognize device code phishing attempts and establish clear procedures for legitimate device authentication scenarios. Security awareness programs should specifically address the risks of entering device codes from unsolicited emails or suspicious websites.

Email security solutions must be configured to detect and block phishing emails that initiate device code attacks. Advanced threat protection platforms can analyze email links and identify redirects to malicious sites designed to harvest device codes. Organizations should also implement email authentication protocols like DMARC, SPF, and DKIM to prevent domain spoofing attempts commonly used in these attacks.

Frequently Asked Questions

How does EvilTokens device code phishing work against Microsoft accounts?+
EvilTokens tricks users into visiting legitimate Microsoft device login portals and entering malicious device codes. This exploits Microsoft's OAuth authentication system to capture tokens that provide persistent account access, bypassing traditional security measures.
Can multi-factor authentication prevent EvilTokens attacks?+
Traditional MFA doesn't fully protect against EvilTokens because the attack uses Microsoft's legitimate device code authentication flow. Users complete the authentication process themselves, making it appear normal to security systems.
How can organizations disable device code authentication in Microsoft 365?+
Administrators can disable device code authentication through Azure Active Directory conditional access policies or by modifying application registration settings to prevent device code grant types. This eliminates the attack vector entirely for organizations that don't need this feature.

Discussion

Share your thoughts and insights

Sign in to join the discussion