Skip to content

Device Code Phishing Forensics What We Learned Investigating... - #487

Merged
carlospolop merged 2 commits into
masterfrom
update_Device_Code_Phishing_Forensics_What_We_Learned_I_62c25d331a4729d9
Oct 18, 2026
Merged

carlospolop merged 2 commits into
masterfrom
update_Device_Code_Phishing_Forensics_What_We_Learned_I_62c25d331a4729d9

Conversation

@carlospolop

Copy link
Copy Markdown
Collaborator

Blog URL

https://research.eye.security/device-code-phishing-forensics

Blog Title

Device Code Phishing Forensics: What We Learned Investigating BEC in the Wild

Blog high summary

Documents a scaled device-code phishing BEC technique: an attacker places a short-lived code on a DocuSign/OneDrive-themed page, then the victim enters it on genuine Microsoft and completes MFA, authorizing attacker-controlled M365 access. The real domain, form, and MFA defeat common AitM indicators; tokens can enable Exchange compromise and further token abuse.

Provides browser detections for static pages, SPA fetch/XMLHttpRequest/window.open flows, and EvilTokens AES-GCM loaders; Sentinel KQL for device-code sign-ins and suspicious registrations; and forensics correlating non-interactive logs, linkable token IDs, IP/user-agent, and shared-session UAL activity. Conditional Access must block Device code flow across All resources to prevent Auth Broker bypass and PRT persistence.

PR changes

Errors

mdbook build unavailable

@carlospolop

Copy link
Copy Markdown
Collaborator Author

Decision: keep

Microsoft documents that authentication-flow policies apply to Device Registration Service only when they target All resources. Microsoft documents a 15-minute default device-code lifetime; the base phishing page listed expires_in but did not explain its effect on delayed lures. The existing PRT page covers the Broker-to-DRS token flow, so the new Conditional Access section links to it rat…

Head: 68f56b1c1f2bef9991a99b81092b7bf40de7208c

@carlospolop

Copy link
Copy Markdown
Collaborator Author

merge

@carlospolop
carlospolop merged commit fd9bf88 into master Oct 18, 2026
2 checks passed
@carlospolop
carlospolop deleted the update_Device_Code_Phishing_Forensics_What_We_Learned_I_62c25d331a4729d9 branch October 18, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant