1-minute read
What a defender needs to know
Microsoft Security Research had a test user approve a GitHub device code initiated by an attacker-controlled client. The client then obtained an OAuth token. In the lab, that authorization reached private repositories available to the account; with separate Copilot CLI features enabled, the researchers read synced sessions, added misleading memory, and steered an active remote session. Microsoft says it has not observed these four Copilot CLI outcomes in the wild. Remote steering requires an online interactive session, remote control enabled and allowed by policy, plus the machine’s permissions and approval settings.
The GitHub verification page was real. Ask the developer whether they initiated the sign-in that produced the code. Examine the authorized OAuth app, requested scopes, repository roles, the “Store local sessions in the Cloud” policy, enabled remote sessions, and saved memory. Where Microsoft Defender XDR has the required email or Teams telemetry and GitHub Enterprise Cloud connector, correlate suspicious messages and clicks with GitHub OAuth token creation and regeneration events.
Revoke an unexpected OAuth authorization in GitHub account settings and verify the client is blocked afterward. GitHub Enterprise Managed Users deployments with Microsoft’s tested identity integration can suspend the managed identity. Investigate repositories, synced sessions, memory, and any active remote session accessible to that account; removing authorization stops future access, while copied content requires its own response.