hunt-ato

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

1|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-ato-marcboggs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-ato
Source: https://github.com/marcboggs/BMAD-AppSec-Orchestrator/tree/main/.claude/skills/hunt-ato
Command: npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-ato-marcboggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug bounty hunters and penetration testers need a systematic taxonomy for finding account takeover (ATO) vulnerabilities, which are among the highest-severity findings but easy to miss without structured coverage of reset flows, email change, OAuth, MFA, and session handling. ## Core Features & Use Cases - Nine ATO Attack Paths: Covers password reset poisoning via host header injection, token leakage through referer headers, predictable reset tokens, non-expiring tokens, email change without re-authentication, OAuth account-link CSRF, MFA bypass, session fixation, and SSO subdomain takeover. - Chain Primitives: Documents how to combine findings such as cookie theft plus password oracle plus missing step-up authentication into Critical-severity persistent ATO, and OAuth open redirect with subdomain takeover into auth code theft. - Severity Prioritization: Provides a priority model ranking no-interaction ATO as Critical down to MitM-dependent paths as Low, with validation requiring actual takeover demonstration on a test account. - Use Case: While testing a target's password reset flow, send a forgot-password request with a modified Host header to check whether the reset link is constructed from the attacker-controlled domain, then chain with subdomain enumeration for an OAuth redirect_uri takeover. ## Quick Start Ask the agent to test the target application's password reset and email change endpoints for account takeover paths using the hunt-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 for password reset poisoning vulnerabilities?▼

Send a POST request to the forgot-password endpoint with a modified Host or X-Forwarded-Host header pointing to an attacker-controlled domain. If the reset email link is constructed from that header, the token is delivered to the attacker, enabling account takeover.

What are the main account takeover attack paths in bug bounty hunting?▼

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

How do I chain IDOR into a full account takeover?▼

Use an IDOR on the user update endpoint to change a victim's email to an attacker-controlled address using the victim's UID with your own session. Then trigger a password reset so the reset email arrives at the attacker's inbox, yielding zero-interaction ATO.

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 man-in-the-middle positioning. Validation requires demonstrating takeover on a test account.

Can subdomain takeover lead to OAuth account takeover?▼

Yes. If OAuth redirect_uri validation accepts subdomain matches and a dangling CNAME exists on an in-scope subdomain, claiming it lets an attacker host an OAuth callback that receives the victim's authorization code, which is exchanged for a session token.