Security

Device Code Phishing: AI-Driven Campaign Escalates

3 min read

Summary

Microsoft Defender Security Research detailed a large-scale phishing campaign that abuses the OAuth device code flow using AI-generated lures, dynamic code generation, and automated backend infrastructure. The campaign raises the risk for organizations because it improves attacker success rates, bypasses traditional detection patterns, and enables token theft, inbox rule persistence, and Microsoft Graph reconnaissance.

Need help with Security?Talk to an Expert

Introduction

Microsoft has disclosed a major evolution in device code phishing, showing how attackers are combining generative AI, automation, and cloud-hosted infrastructure to compromise Microsoft accounts at scale. For security teams and Microsoft 365 administrators, this matters because the campaign targets legitimate authentication flows rather than stealing passwords directly, making it harder to detect with traditional controls.

What’s new in this campaign

According to Microsoft Defender Security Research, the activity builds on earlier device code phishing tradecraft but adds several important advances:

  • AI-enabled phishing lures: Attackers used generative AI to create highly personalized emails tied to job roles and business scenarios such as invoices, RFPs, and manufacturing workflows.
  • Dynamic device code generation: Instead of relying on pre-generated codes that expire in 15 minutes, the device code is created only when the user clicks the phishing link.
  • Automated cloud infrastructure: Threat actors used platforms such as Railway, Vercel, Cloudflare Workers, and AWS Lambda to deploy short-lived infrastructure and redirect chains.
  • Blended-in traffic: Redirects through trusted cloud services help the activity avoid simple blocklists and reputation-based defenses.
  • Post-compromise token abuse: Once a victim completes the device login flow, attackers use the token for email exfiltration, inbox rule creation, and Microsoft Graph reconnaissance.

Why this is different

Traditional phishing usually tries to capture credentials. In this case, the attacker tricks the user into approving a legitimate Microsoft device login session that the attacker initiated. Because the authentication happens on Microsoft’s real device login page, users may be less suspicious, and MFA can be less effective if the session is not strongly bound to the original context.

Microsoft also links this trend to EvilToken, a phishing-as-a-service toolkit driving broader device code abuse. The use of automation and AI marks a significant step up from the Storm-2372 campaign documented in 2025.

Impact on IT administrators

Security and identity teams should expect:

  • More convincing phishing emails targeting high-value users
  • Increased abuse of legitimate OAuth and Microsoft sign-in flows
  • Token-based compromise without password theft
  • Persistence through malicious inbox rules and hidden mail redirection
  • Reconnaissance against organizational structure via Microsoft Graph

Administrators should review Microsoft’s mitigation guidance and prioritize:

  • Monitoring for suspicious device code authentication activity
  • Investigating unexpected inbox rules and token-based access patterns
  • Hardening conditional access and sign-in risk policies where possible
  • Training users to treat unsolicited device login prompts as suspicious
  • Hunting for suspicious redirects, impersonation domains, and cloud-hosted phishing infrastructure

This research is a reminder that phishing defenses must now account for legitimate authentication workflows being abused, not just fake login pages and stolen passwords.

Need help with Security?

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

Talk to an Expert

Stay updated on Microsoft technologies

device code phishingMicrosoft DefenderOAuthtoken theftphishing

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.