threatdeck
Live 13:45 UTC ·

New Technique Medium TD-2026-0111 For CISO, SOC / IR, AppSec, AI Eng AI-assisted

Device code phishing can take over GitHub Copilot CLI sessions, memory, and repo access

Microsoft researchers simulated a device code phishing attack against GitHub Copilot CLI in a controlled lab. After a victim approved an attacker-initiated device code request, the attacker could steer an enabled remote session, add misleading memory entries, read synced sessions, and access private repositories available to the account. Microsoft states these are proof-of-concept results and not attacks observed in the wild.

Why it matters

Any user who approves a device code request they did not start can expose AI coding agent sessions, stored context, and private repositories. The GitHub verification page is genuine, so the domain alone does not reveal the request was malicious.

Do this

  1. Instruct developers to enter a device code only for sign-ins they initiated, and treat unsolicited verify or Copilot activation requests as phishing.
  2. Review authorized OAuth applications in GitHub and revoke unexpected authorizations.
  3. Review the GitHub Copilot CLI policy for storing local sessions in the cloud and remote control, and choose the least permissive setting that supports workflows.
  4. Connect GitHub Enterprise Cloud to Microsoft Defender for Cloud Apps and enable the Defender XDR device code phishing detections for email and Teams.
  5. Configure Safe Links in Microsoft Defender for Office 365 for email and Teams, and review saved Copilot Memory entries during incident response.

Signals

  • NoCISA KEV
  • 25/100Priority
  • 80%Confidence

Evidence

“These are proof-of-concept results showing how existing features, working as designed, could be abused after a phished authorization; they are not attacks we have observed in the wild.”

Microsoft Security Blog

“The verification page is genuinely hosted by GitHub; the legitimate domain alone does not establish who initiated the request.”

Microsoft Security Blog

“Enter a device code only for a sign-in you initiated yourself.”

Microsoft Security Blog

Sources

Affected / related

Device code phishing, GitHub Copilot CLI, Microsoft Defender XDR, Microsoft Defender for Cloud Apps, T1528 Steal Application Access Token

Published 2026-11-17 15:00 UTC · updated 2026-11-17 16:05 UTC · AI-assisted summary, checked against quoted sources · How we score

Following

Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

Presets

Get updates

A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.