hunt-ato

Tests nine account takeover paths including password reset flaws, OAuth misconfigurations, and MFA bypass chains.

Updated May 29, 2026
One-click install
npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-ato-hhjkjkjk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-ato
Source: https://github.com/hhjkjkjk/Claude-skills/tree/main/skills/hunt-ato
Command: npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-ato-hhjkjkjk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug bounty hunters and penetration testers often miss account takeover (ATO) vulnerabilities because they test isolated endpoints instead of systematically covering the full taxonomy of ATO paths and chaining primitives together. ## Core Features & Use Cases - Nine-Path ATO Taxonomy: Covers password reset poisoning (host header injection, token leakage via Referer, predictable tokens, non-expiring tokens), email change without re-auth, OAuth account-link CSRF, MFA bypass, session fixation, JWT manipulation, and SSO subdomain takeover. - Chain Primitives: Combines findings like cookie theft, password oracles, OAuth open redirects, and dangling CNAME subdomain takeovers into Critical-severity ATO chains. - Severity Prioritization: Classifies ATO findings from Critical (no user interaction) down to Low (requires MitM) with validation guidance. - Use Case: While testing a target's password reset flow, inject an attacker-controlled Host header into the forgot-password request, observe the reset link pointing to your domain, and demonstrate full account takeover on a test account. ## Quick Start Ask the AI to test the target application's password reset and email change flows for account takeover vulnerabilities using the nine-path ATO taxonomy.

Frequently Asked Questions about hunt-ato

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

FAQPage Schema
How do I test password reset for account takeover?▼

Test password reset by injecting an attacker-controlled Host or X-Forwarded-Host header into the forgot-password request so the reset link points to your domain. Also check for predictable tokens, tokens leaked via the Referer header, and tokens that never expire.

What are the most common account takeover vulnerability types?▼

The nine paths covered are password reset flaws, email change without re-auth, OAuth account-link CSRF, MFA bypass, session fixation, JWT manipulation, password change without step-up, social-recovery abuse, and SSO subdomain takeover.

How does subdomain takeover lead to account takeover?▼

When OAuth redirect_uri validation accepts wildcard subdomains, a dangling CNAME on a subdomain can be claimed on services like Heroku or S3. Hosting an OAuth callback there lets an attacker steal authorization codes and exchange them for tokens.

When is an account takeover finding rated Critical severity?▼

ATO is Critical when it requires no user interaction, High when it needs one email click or an existing session, Medium when it requires phishing plus interaction, and Low when it requires the attacker to be a man-in-the-middle.

Why was my account takeover report rejected as low severity?▼

Reports get rejected when the attack requires excessive victim interaction like clicking a link, entering credentials, and completing a CAPTCHA. Validate by reproducing the full takeover on a fresh test account from an attacker session within ten minutes.