Individual skill
o365-credential-harvest
Harvest and replay O365 / Entra ID access via the OAuth device-code flow and captured tokens (TokenTactics-style), skipping the password + MFA prompts.
packages/decepticon/decepticon/skills/standard/phisher/o365-credential-harvest/SKILL.md
Source commit cc6044561ff32188dc0aa899bcc7d3666ffcfd1c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 6,563
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- phishing Declared skill tag
- o365 Declared skill tag
- oauth Declared skill tag
- token-replay Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# O365 / Entra Credential & Token Harvest
Two Microsoft-identity initial-access paths that avoid a fake password
page: the **device-code** flow and **token replay**. Both are favored
because the victim authenticates on the genuine Microsoft endpoint.
## Device-code flow
The attacker requests a device code; the victim is social-engineered
to enter it at the real `microsoft.com/devicelogin`. After they
complete sign-in (MFA included), the attacker polls and receives
access + refresh tokens.
```bash