hunt-ato

Hunt account takeover paths across authentication and OAuth workflows.

2|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-ato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ato
Source: https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda/tree/main/.agent/skills/hunt-ato
Command: npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-ato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify, test, and prioritize account takeover (ATO) attack paths by organizing common ATO primitives into actionable hunt and validation steps.

Core Features & Use Cases

  • ATO taxonomy for hunting: Covers nine distinct ATO paths, including reset/account-email flaws, OAuth linking and redirect issues, MFA/session problems, token manipulation, and SSO subdomain takeover scenarios.
  • Chain primitive framing: Breaks common ATO “chains” into reusable building blocks (e.g., cookie theft + password oracle + missing step-up, OAuth redirect_uri takeover for code theft).
  • Critical validation guidance: Emphasizes reproducing a real takeover against a test victim session/account to separate Critical-paid findings from lower-tier cases.

Quick Start

Run the hunt workflow for account takeover taxonomy and validate an ATO chain by demonstrating account takeover on test account B using attacker A’s session.

Frequently Asked Questions about hunt-ato

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

FAQPage Schema
How do I map account takeover paths during security testing?

Validating an ATO chain requires reproducing a complete account takeover on a controlled test account. You must demonstrate taking over test victim account B using attacker account A's session to confirm the exploit chain works end-to-end and qualifies as a critical finding.

What authentication mechanisms are vulnerable to account takeover?

Authentication mechanisms vulnerable to account takeover include password reset flows, email change procedures, MFA bypass, session handling, JWT manipulation, and OAuth redirect_uri or callback control. SSO subdomain takeover scenarios also present exploitable paths for unauthorized access.

How do I validate an account takeover chain for a bug bounty report?

Validating an account takeover chain requires reproducing a complete account takeover on a controlled test account. You demonstrate accessing test victim account B from attacker account A's session to confirm the exploit chain works end-to-end and qualifies as a critical finding.

What is the best way to test OAuth redirect_uri vulnerabilities for ATO?

Testing OAuth redirect_uri vulnerabilities involves checking callback control configurations for code theft opportunities. You map the OAuth linking and redirect issues as chain primitives, validating whether an attacker can intercept authorization codes to achieve account takeover.

Do I need a controlled test environment to hunt for MFA bypass chains?

Hunting for MFA bypass chains requires a controlled test environment with at least two accounts. You need attacker account A and victim account B to reproduce the missing step-up authentication or session handling flaws and validate the complete takeover safely.