hunt-session

Validates session lifecycle security through evidence-gated black-box testing of cookies and tokens.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Session management flaws like fixation, missing rotation, and improper revocation are hard to confirm without false positives. This Skill provides a disciplined, evidence-gated workflow to verify whether cookie and token lifecycle controls are actually enforced by the server. ## Core Features & Use Cases - Lifecycle Verification: Tests login, logout, password change, and permission change events to confirm old sessions are invalidated or rotated server-side. - Fixation & Revocation Checks: Runs controlled fixation and rotation comparisons using only your own test accounts and profiles. - False-Positive Filtering: Treats WAF blocks, captchas, timeouts, and client-side cookie observations as inconclusive, requiring server-side oracles for valid findings. - Use Case: During an authorized web app assessment, verify that changing a password actually kills existing sessions on other devices, with a full evidence timeline for the report. ## Quick Start Use $hunt-session to plan an evidence-gated, authorized validation of the target application's session lifecycle.

Frequently Asked Questions about hunt-session

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

FAQPage Schema
How do I test session fixation in a web application?

Session fixation testing uses your own test accounts to check whether a pre-set session ID is accepted by the server after login. This Skill runs controlled fixation and rotation comparisons and only counts server-side acceptance as a valid finding.

How to verify logout actually invalidates a session?

Replay the old session token against a protected canary endpoint after logout. If the server still grants access to the protected resource, the session was not properly invalidated, which constitutes a valid finding.

Does a missing cookie attribute mean the session is vulnerable?

No. Missing Set-Cookie attributes alone do not prove account takeover or session flaws. The Skill requires server-side oracles showing actual unauthorized access before confirming a vulnerability.

Why are WAF blocks and captchas treated as inconclusive?

WAF triggers, captchas, timeouts, and single errors do not prove or disprove a session flaw, so they are marked INCONCLUSIVE. Only reproducible server-side behavior against protected resources counts as evidence.

When should I stop a session security test?

Stop immediately if testing touches real user sessions, third-party data, token exports, or irreversible side effects. The Skill restricts all probes to owned accounts, approved rates, and reversible security events.