---
title: "Device-code phishing"
slug: device-code-phishing
kind: "Technique"
desk: cyber
maturity: "mature"
sources: 49
url: https://morningstarsecurity.com/wiki/device-code-phishing
exported: 2026-11-19 23:58 UTC
---

# Device-code phishing
Technique · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on Device-code phishing, a snapshot taken on 19 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on Device-code phishing (a snapshot from 19 Nov 2026): https://morningstarsecurity.com/wiki/device-code-phishing". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **ATT&CK ID:** T1187 (low confidence, 1 independent source)

## Tactic
- Account compromise via OAuth 2.0 device authorization flow exploitation

## Platform
- OAuth 2.0 identity providers

## Detection
- Monitor for unusual device code authentication requests from unfamiliar sources
- OAuth token capture, suspicious device code requests
- hunt for device code authentication and automated token refresh
- sign-in risk policies
- Adobe-themed authentication request
- behavioral analysis of authentication flows and infrastructure
- Anomalous authentication alerting, conditional access policies, token lifetime monitoring
- Authorization phishing variant
- Monitor for suspicious login activity; verify application authentication context
- Monitor for POST /api/device/start requests with clientMode: 'broker' parameter
- 30+ distinct kits tracked offering the technique
- bypasses multi-factor authentication and phishing-resistant mechanisms
- Fake landing pages requesting device codes for Microsoft authentication
- Kaspersky
- Legitimate authentication services and unfamiliar device code authorization process disguised as verification challenge
- limited traditional phishing indicators; legitimate Microsoft login page used
- Organizations currently lack effective detection or prevention mechanisms

## Entry
Device-code phishing is an oauth-2-0 attack that exploits the device authorization flow to compromise user accounts through social engineering [1].

### Attack Mechanism

The technique leverages legitimate authentication services by presenting fake landing pages that request device codes for Microsoft or other OAuth 2.0 identity providers [2]. Attackers disguise the unfamiliar device code authorization process as a verification challenge, exploiting users' trust in legitimate login interfaces [1]. The attack reportedly bypasses multi-factor authentication and phishing-resistant mechanisms [3], and produces limited traditional phishing indicators since legitimate authentication pages are used [4].

### Scope

Over 30 distinct kits have been tracked offering this technique [5]. Adobe-themed authentication requests have been observed in the wild.

### Detection Challenges

Organizations currently lack effective detection or prevention mechanisms for this attack [1]. Detection approaches proposed in security research include:

- Monitoring POST `/api/device/start` requests with `clientMode: 'broker'` parameter
- Tracking suspicious login activity and verifying application authentication context
- Hunting for device code authentication and automated token refresh patterns
- Monitoring unusual device code authentication requests from unfamiliar sources
- Implementing sign-in risk policies and anomalous authentication alerting
- Deploying conditional access policies and token lifetime monitoring
- Behavioral analysis of authentication flows and infrastructure
- OAuth token capture and suspicious device code request detection

### Classification

The technique is associated with MITRE ATT&CK identifier T1187 and represents account compromise via OAuth 2.0 device authorization flow exploitation [1].

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Detected by:** EvilTokens
- **Exploited by:** Kali365, WardenStealer
- **Mitigated by:** Conditional access policies, Microsoft Entra ID, Passkeys, Phishing-resistant authentication, token-revocation
- **Part of:** Credential Access
- **Used by:** Cali 365, CaptiveCrunch, CSuite, Fake AI Event Phishing Campaign, Forg365, GhostCode, Greatness, Kali365, Microsoft Phishing Campaign November 2026, Midnight Blizzard, N0va, ShinyHunters, Skyw4lker, SLTT Device Code Phishing Campaign, Storm-2372, Wazza

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
Microsoft, United States, Microsoft 365, T1566: Phishing, Use of Known Credentials, Adversary in the Middle, OAuth, Google, Healthcare sector, Telegram, Engage in Deceptive Interactions, Multifactor authentication, Session Hijacking, Australia, Cloudflare, ANY.RUN

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/device-code-phishing
- More techniques (ATT&CK): https://morningstarsecurity.com/wiki/kind/technique
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources (5 of 49)
1. Device Code Phishing: An Evolving Technique Impacting SLTTs · CIS: Security Blog · 6 Nov 2026 · https://www.cisecurity.org/insights/blog/device-code-phishing-evolving-technique-impacting-sltts
2. Russian spies turn public Wi-Fi into malware delivery systems · The Register: Security · 3 Aug 2026 · https://www.theregister.com/security/2026/08/03/russias-svr-borks-public-wi-fis-for-digital-surveillance/5282399
3. SANS Stormcast Wednesday, August 5th, 2026: Diagnostic Tool Hunt; Device Code Phishing; XCSSET; NuGet API Keys · SANS ISC: Daily Podcast (podcast) · 5 Aug 2026 · https://isc.sans.edu/podcastdetail/10038
4. Kali365 Targets US Organizations with Data Theft via Device Code Phishing · HackerNoon · 6 Aug 2026 · https://hackernoon.com/kali365-targets-us-organizations-with-data-theft-via-device-code-phishing
5. Know Your Enemy: Browser-Based Attack Techniques in 2026 · The Hacker News · 30 Sep 2026 · https://thehackernews.com/2026/09/know-your-enemy-browser-based-attack.html

---
Snapshot of https://morningstarsecurity.com/wiki/device-code-phishing taken 19 Nov 2026 23:58 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/device-code-phishing
