hunt-password-recovery

Validates password reset and account recovery flows on authorized self-owned accounts.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-password-recovery-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-password-recovery
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-password-recovery
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-password-recovery-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers need a disciplined, evidence-gated method to assess password reset and account recovery flows without guessing tokens, spamming reset emails, or touching third-party accounts. This Skill enforces a safe, scoped methodology for finding real recovery flaws. ## Core Features & Use Cases - Full State-Machine Mapping: Records the complete request → issuance → delivery → confirmation → password set → session revoke lifecycle using two self-owned accounts. - Token Binding & Lifecycle Checks: Verifies subject binding, single-use, expiry, revocation, and rate/enumeration defenses of reset tokens and recovery codes. - Minimal Safe Validation: Replays only self-obtained consumed or revoked tokens and runs small valid/invalid email differentials, with explicit stop conditions for third parties or irreversible side effects. - Use Case: During an authorized web app assessment, use this Skill to test whether a consumed reset token remains valid or whether a token is incorrectly bound across your own two test accounts, then route confirmed takeover findings to triage. ## Quick Start Ask the agent to run the password recovery hunt route against my authorized test application using my two self-owned accounts and report any token binding or revocation flaws.

Frequently Asked Questions about hunt-password-recovery

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

FAQPage Schema
How do I test a password reset flow for security flaws?

Map the full reset state machine with two self-owned accounts: request, issuance, delivery, confirmation, password set, and session revoke. Then probe token subject binding, single-use, expiry, and revocation one variable at a time, comparing against your recorded baseline.

How to check if a reset token is properly invalidated after use?

Replay only tokens you obtained yourself after they were consumed or revoked, and observe whether the reset still succeeds. A valid finding requires the consumed or revoked token to remain usable; normal single-device resets or email delays do not count.

Can I test account recovery on accounts I do not own?

No. This methodology strictly limits testing to self-owned accounts, test data, and approved rates. Testing third-party emails, real administrator accounts, token guessing, or bulk requests triggers an immediate stop condition.

What counts as a real account recovery vulnerability versus noise?

Valid findings include a self-owned token working after consumption or revocation, cross-account or cross-session misbinding, or a reset API directly exposing a usable token. WAF blocks, captchas, timeouts, and copy differences are inconclusive, not vulnerabilities.

When should password recovery testing stop immediately?

Stop when testing would touch third-party mailboxes, real admin accounts, shared users, or cause irreversible side effects. Also stop if the work exceeds the authorized scope or requires guessing tokens or bypassing captchas.