performing-account-takeover-attacks

Tests authentication, recovery, and identity flows for account takeover vulnerabilities during authorized assessments.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-account-takeover-attacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-account-takeover-attacks
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/web-application-security/performing-account-takeover-attacks
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-account-takeover-attacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Account takeover bugs rarely live in the login form itself; they hide in password reset, email change, magic-link, SSO, and cross-device login flows that scanners miss. This Skill provides a systematic methodology for finding and confirming ATO vulnerabilities during authorized penetration tests, so findings are proven with concrete post-auth evidence rather than guessed.

Core Features & Use Cases

  • Nine ATO Variant Coverage: Tests Unicode/normalization email collisions, reusable reset and magic links, pre-account-takeover, host-header poisoning, response manipulation, open redirects, session persistence, QR/device-code abuse, and privileged-parameter IDOR in recovery flows.
  • Confirmation Guidance: Each variant includes explicit steps to confirm a real hit (e.g., verifying the session resolves to the victim's userId) and avoid false positives from cosmetic UI changes.
  • Structured Reporting: Outputs findings in a consistent format with severity, OWASP category, reproduction steps, evidence tables, impact, and remediation advice.
  • Use Case: During an authorized web app assessment, you intercept a password-reset request in Burp Suite, poison the Host header, and confirm the reset link points to your controlled domain, proving token leakage and full account takeover.

Quick Start

Ask the agent to test the target application's password reset and email change flows for account takeover vulnerabilities using my two authorized test accounts.

Frequently Asked Questions about performing-account-takeover-attacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a web application for account takeover vulnerabilities?

Map all login, signup, reset, email change, and SSO endpoints, then test nine variants: Unicode email collisions, reusable reset links, pre-account-takeover, host-header poisoning, response manipulation, open redirects, session persistence, QR code abuse, and IDOR in recovery flows. Confirm each hit with a post-auth action.

How to find password reset token reuse bugs with Burp Suite?

Capture a valid reset link in Burp Suite, then redeem it from a second browser or after the victim changes their email. If the same token authenticates across contexts or survives credential changes, the reset flow lacks single-use and session binding.

What is a Unicode email collision attack in authentication?

A Unicode email collision occurs when an app normalizes addresses inconsistently across UI, database, SMTP, and identity provider layers. An attacker registers a confusable address like vić[email protected] and receives reset artifacts bound to the victim's account.

Does this testing require authorization and special tooling?

Yes, it requires an engagement scope covering authentication plus two test accounts you own. Tooling includes Burp Suite for interception, two browser profiles, gau or waybackurls for link discovery, and a domain you control for out-of-band token capture.

Why do account takeover tests produce false positives?

False positives happen when response manipulation only changes cosmetic UI state without advancing authentication. Always confirm by reaching a post-auth page, obtaining a valid session cookie, and reading victim-only data such as the victim's userId.