Security

EvilTokens Device Code Phishing: Microsoft Guidance

3 min read

Summary

Microsoft has detailed how the EvilTokens phishing-as-a-service platform industrialized device code phishing to steal tokens and compromise more than 12,000 inboxes across 10,000 organizations. The report matters for security teams because it includes mitigation guidance, Defender XDR detections, and hunting recommendations to reduce risk from token theft and post-compromise persistence.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published a deep dive into EvilTokens, a phishing-as-a-service platform that rapidly became a major threat in 2026. The campaign is notable because it abuses the legitimate device code authentication flow to capture tokens, bypass traditional MFA expectations, and maintain access to Microsoft 365 accounts.

For IT and security administrators, this is an important reminder that modern phishing increasingly targets session tokens and OAuth flows, not just usernames and passwords.

What’s new in Microsoft’s findings

Microsoft says EvilTokens:

  • Compromised more than 12,000 inboxes across over 10,000 organizations worldwide
  • Used AI-assisted phishing lures and inbox analysis to identify high-value targets
  • Abused the device code flow to trick users into authorizing attacker-controlled sessions
  • Enabled post-compromise activity such as email exfiltration, malicious inbox rules, and Microsoft Graph reconnaissance
  • Supported large-scale campaigns with short-lived infrastructure and automated backend logic designed to evade detection

Microsoft also linked the development and support of the platform to Storm-2992 and said its Digital Crimes Unit helped disrupt infrastructure used by the service.

Why device code phishing is effective

Device code authentication is designed for devices like smart displays, Teams devices, and conference systems that cannot complete a normal interactive sign-in. Attackers exploit this by initiating the sign-in themselves, then convincing a user to enter the code through a phishing lure.

Because the user completes a legitimate Microsoft authentication step, the attacker can obtain access without stealing the password directly. That makes this technique especially dangerous in environments that rely heavily on MFA as a primary defense.

Impact on administrators

Organizations using Microsoft 365, Entra ID, and Defender should review whether device code flow is truly required in their environment. Industries affected by EvilTokens campaigns included financial services, healthcare, higher education, construction, and real estate, showing that the threat is broad rather than niche.

Security teams should also assume that a successful token theft may lead to:

  • Persistent mailbox access
  • Hidden inbox rules
  • Internal reconnaissance through Microsoft Graph
  • Follow-on business email compromise activity

Microsoft’s guidance is clear:

  • Block device code flow wherever possible
  • If required for Teams devices, scope exceptions narrowly to specific resource accounts
  • Review Conditional Access configuration, including exclusions for the Device Registration Service only where needed
  • Use Microsoft Defender XDR detections and hunting queries from the Microsoft report
  • Strengthen mail flow rules, spoof protection, and connector configuration to reduce phishing delivery
  • Train users to be cautious of requests to enter device codes outside expected sign-in scenarios

Bottom line

EvilTokens shows how attackers are operationalizing token theft at scale using AI, automation, and legitimate authentication workflows. For defenders, the priority is to reduce unnecessary device code usage, tighten Conditional Access, and improve detection for suspicious token-based activity.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Securityphishingdevice code phishingMicrosoft Defender XDREntra ID

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.