Individual skill

performing-account-takeover-attacks

Systematically testing authentication, recovery, and identity flows for account takeover (ATO) — including Unicode/normalization email collisions, reusable reset/magic links, pre-account-takeover, response manipulation, email-verification bypass, session/cookie reuse, and QR/device-code login abuse. Activates when assessing login, signup, password reset, email change, SSO/OAuth, or cross-device login flows.

internal/tools/skills/data/web-application-security/performing-account-takeover-attacks/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 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)
1,312
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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Account Takeover Attacks

## When to Use

- During authorized assessments of any authentication, registration, or account-recovery flow
- When testing password reset, email change, magic-link, or invite flows for token reuse and host-header poisoning
- When the app supports third-party SSO/OAuth/OIDC and may normalize emails differently than the IdP
- When testing cross-device login surfaces (desktop QR login, TV/device-code, "approve on your phone")
- When you have a limited XSS, CORS misconfig, CSRF, or subdomain takeover that could pivot into ATO

## Prerequisites

- **Authorization**: Engagement scope covering authentication and at least two test accounts (attacker + victim) you own
- **Burp Suite**: For intercepting and replaying reset/verification requests and manipulating headers/responses