Threat video1:00
GitHub Copilot CLI Device Code Phishing: Detection & IOCs
Approving a phished GitHub device code grants an attacker OAuth access to the victim's GitHub account. 9 detection rules, 9 IOCs and a free Splunk SPL rule.
Read the full threat intel for GitHub Copilot CLI Device Code Phishing: Detection & IOCs →
Chapters
- 0:00The hookLab: researchers reproduced device code phishing against Copilot.
- 0:05The storyMicrosoft published a lab proof of concept.
- 0:11Attack pathLab tests began a device code login.
- 0:28AttributionNo threat actor: this was defensive research.
- 0:33Indicators of compromise2 indicators to hunt: 2 URLs.
- 0:38MITRE ATT&CK techniques9 ATT&CK techniques, from initial access to impact.
- 0:43Remediation3 steps now: Review authorized OAuth apps in GitHub account and organization settings.
- 0:50Detection rules9 detection rules, in SPL, KQL and Sigma.
Transcript
0:00Lab: researchers reproduced device code phishing against Copilot.
0:05Microsoft published a lab proof of concept.
0:08Not seen in the wild.
0:11Lab tests began a device code login.
0:14Once approved, a client obtained access.
0:17Remote control on, it could steer a session.
0:20Cloud sessions could be read, and memory entries added.
0:23Private repos followed permissions.
0:28No threat actor: this was defensive research.
0:332 indicators to hunt: 2 URLs.
0:399 ATT&CK techniques, from initial access to impact.
0:433 steps now: Review authorized OAuth apps in GitHub account and organization settings.
0:519 detection rules, in SPL, KQL and Sigma.
0:56Threadlinqs. The unified security engineering platform.