Cyber Attacking Oauth With Device Code Phishing

---
name: cyber-attacking-oauth-with-device-code-phishing
description: "[LAB-GATED; discovery is not runtime authorization; offensive/dual-use — authorized-lab gate] Run OAuth 2.0 device-code and illicit-consent phishing against Microsoft Entra ID to steal access and refresh tokens, bypass MFA, and pivot across Microsoft 365 services."
hide: true
---

<!-- GENERATED:YURI-CODEX-SKILL-ADAPTER:v1 -->

# YURI skill adapter

Authoritative source: `.claude/skills-labgated/cyber-attacking-oauth-with-device-code-phishing/SKILL.md`

Authoritative source SHA-256: `8e014ca7f9e82168c54d9bf7e9caf9b4bc2b08a7315b9dda55f5526fda89b1d1`

> AUTHORIZED-LAB ONLY. Offensive/dual-use capability. Use exclusively against systems you own or have explicit written authorization to test. Owner-authorized metadata discovery does not authorize runtime actions; use requires an explicit authorized-engagement decision.

Source class: `labgated`
Owner-authorized discovery: `true`
Runtime/action authorization: `false`
Risk gate (registry metadata): "offensive/dual-use — authorized-lab gate"

Discovery does not authorize execution. Obtain explicit current-task authorization before any offensive or dual-use action.

Before acting, read the authoritative source file above completely from beginning to end. If the governed source is absent, run `node _SYSTEM/Scripts/skill-recall.mjs --show cyber-attacking-oauth-with-device-code-phishing` and read its complete verified output. Follow that source as the skill body; this adapter is a non-authoritative metadata-and-pointer projection.