hunt-misc

Identify authorization, token lifecycle, and SSO logic vulnerabilities across web targets.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-misc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-misc
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/hunt-misc
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-misc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hunting for high-impact but less “obvious” vulnerability classes (misc access control failures, token/scope issues, invitation and SSO logic bugs, and misconfiguration-driven auth failures) is slow and often gets stuck on incomplete validation.

Core Features & Use Cases

  • Role and permission boundary validation to confirm privilege differences with response-body differentials and concrete repro steps.
  • Token, invitation, and post-removal access testing to detect stale sessions, multi-use tokens, and authorization gaps across user lifecycle events.
  • Integration and config-driven vulnerability probing for SSRF/token exfil paths, header injection surfaces, SSO parsing weaknesses, and package-registry misconfigurations.

Quick Start

Ask the AI to hunt for misc vulnerabilities on https://target.example, focusing on invitation, token scope, SSO/callback logic, and cross-tenant access with a reproducible report.

Frequently Asked Questions about hunt-misc

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

FAQPage Schema
How do I test SSO and SAML callback logic for authorization bypasses?

To hunt for invitation bypass vulnerabilities, you test invitation acceptance flows without proper verification and validate token scopes across user lifecycle events. This requires mapping role boundaries and checking response-body differentials to confirm privilege differences and stale session persistence.

What is the best way to find header injection and misconfiguration-driven auth failures?

Hunting for token scope and session lifecycle vulnerabilities involves validating end-to-end token workflows and testing post-removal access persistence. You detect stale sessions and multi-use tokens by applying structured role-boundary mapping and response-body differential checking across real web targets.

Can I use this methodology to probe undocumented and internal APIs for cross-tenant access?

Hunting for misc access control failures involves mapping role boundaries and validating permission differences with response-body differentials. You detect authorization gaps, multi-use tokens, and post-removal access persistence by systematically probing endpoints and integration coverage across real web targets.

How do I validate privilege differences when testing authorization logic?

Hunting for SSO signature logic mistakes involves validating end-to-end token workflows and testing callback logic for authorization bypasses. You detect signature parsing weaknesses and configuration-driven vulnerabilities by probing integration surfaces and checking response-body differentials across user lifecycle events.

What is the best way to find header injection and misconfiguration vulnerabilities?

Hunting for post-removal access persistence involves testing user lifecycle events to detect stale sessions and authorization gaps. You validate token and session lifecycle workflows by mapping role boundaries and checking response-body differentials to confirm privilege differences with concrete repro steps.

Can I probe undocumented APIs to detect cross-tenant access vulnerabilities?

Yes, you can probe undocumented and internal APIs to detect cross-tenant access vulnerabilities by applying systematic endpoint and integration coverage. You validate authorization logic and token scope boundaries using structured role-boundary mapping and response-body differential checking across real web targets.