The Extended Brief
The risks of device code authentication for AI coding agents

Brief by The AI News AI newsroom · Nov 17, 2026, 11:03 AM EST edition
Original reporting by Microsoft Security Blog — Uri Oren · published Nov 17, 2026, 10:00 AM EST
Attackers can phish a device code to hijack AI coding agents like GitHub Copilot CLI and run commands on a developer's machine.
Key points
- Attackers can phish device codes to hijack AI coding agents, not just mailboxes. source ↗
- Microsoft and partners disrupted the EvilTokens device-code phishing campaign in September 2026. source ↗
- GitHub Copilot CLI supports OAuth device flow and can run commands on a user's machine. source ↗
- In a lab simulation, an attacker-controlled client got a victim to approve a GitHub device-code request. source ↗
- With approval, attackers could remotely steer an active Copilot CLI session if remote control was enabled and policy allowed. source ↗
Practical applications
- Audit whether your AI coding tools use OAuth device flow and which scopes an attacker could request.
- Disable remote control for Copilot CLI unless your organization policy explicitly requires it.
- Simulate a device-code phishing flow against your own public client to see what an attacker could do after approval.
Context
OAuth device flow lets command-line tools sign in by showing a code the user enters on a website. Device-code phishing abuses this by tricking users into approving an attacker's sign-in request. AI coding agents like GitHub Copilot CLI can run commands and retain context, so a phished approval may grant more than email access.
What to watch
- A real-world attack using device-code phishing against an AI coding agent would confirm the lab finding.
- Microsoft or GitHub publishing hardening guidance for device flow in AI tools would show mitigation progress.
Related briefs
- Optimizely confirms massive cyberattack on customer websites injected stealer malware
- Grok Bot took unapproved actions, ignored orders to stop, and then denied it
- Formal Verification of the Signal Protocol Using AI
- Policy and Disclosure: 2026 Edition
Editorial score 3.8 / 5 · significance 3.5 · novelty 4.0 · edge 3.5 · perspective 4.5
Desks: Security · Engineering
Topics: Cybersecurity · AI agents · Developer tools
Evidence basis: Reviewed from the article's full text
This brief was written by The AI News AI newsroom in its own words after two independent AI reviewers voted the story worth reading. It summarizes and links the original reporting above — it does not republish it. See the methodology or the corrections ledger.