hunt-ato

Map and chain security primitives to validate account takeover vulnerabilities.

13|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/pdparchitect/rook --skill hunt-ato-pdparchitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ato
Source: https://github.com/pdparchitect/rook/tree/main/skills/hunt-ato
Command: npx skills add https://github.com/pdparchitect/rook --skill hunt-ato-pdparchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of identifying and chaining account takeover (ATO) vulnerabilities, which often involve multi-step logic flaws that are difficult to track manually.

Core Features & Use Cases

  • Taxonomy Mapping: Provides a structured framework for 9 distinct ATO paths, including password reset poisoning, email change flaws, and OAuth misconfigurations.
  • Chain Analysis: Enables the identification of complex attack chains by combining primitives like cookie theft, password oracles, and missing step-up authentication.
  • Use Case: Use this skill when auditing authentication flows to determine if a seemingly low-impact bug can be escalated into a critical account takeover by chaining it with other identified primitives.

Quick Start

Use the hunt-ato skill to analyze the current authentication workflow for potential account takeover chains and provide a validation plan.

Frequently Asked Questions about hunt-ato

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

FAQPage Schema
How do I identify account takeover vulnerabilities in authentication flows?

To identify account takeover vulnerabilities, systematically test password reset, email change, MFA, and OAuth mechanisms to map complex attack paths and chain security primitives for critical impact validation.

What is an account takeover chain in web application security?

An account takeover chain combines security primitives like cookie theft, password oracles, and missing step-up authentication to escalate low-impact bugs into critical account takeovers during authentication flow audits.

Can I use this approach to test OAuth misconfigurations and password reset poisoning?

Yes, you can test OAuth misconfigurations and password reset poisoning by applying a structured taxonomy of nine distinct account takeover paths to systematically validate vulnerabilities in authentication workflows.

What is the best way to escalate low-impact authentication bugs into full account takeover?

The best way to escalate low-impact authentication bugs is chain analysis, mapping complex attack paths by combining primitives like cookie theft and missing step-up authentication to demonstrate critical account takeover.

When do I need to audit MFA and email change mechanisms for account takeover paths?

You need to audit MFA and email change mechanisms during web application security audits when testing authentication flows for privilege escalation research and validating multi-step logic flaws.