hunt-api-misconfig

Identify and validate API security misconfigurations including mass assignment, JWT flaws, and CORS bypasses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of manually auditing complex API surfaces for subtle security flaws like mass assignment, JWT misconfigurations, and prototype pollution that often bypass standard automated scanners.

Core Features & Use Cases

  • Vulnerability Hunting: Detects mass assignment, JWT algorithm confusion, prototype pollution, and CORS misconfigurations.
  • OData & OpenAPI Analysis: Maps attack surfaces in OData query layers and exposed Swagger/OpenAPI documentation.
  • Use Case: Use this skill to audit a target API for mass assignment vulnerabilities by testing if extra fields like role or is_admin are accepted in profile update requests.

Quick Start

Use the hunt-api-misconfig skill to audit the target API endpoint for mass assignment and JWT vulnerabilities.

Frequently Asked Questions about hunt-api-misconfig

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

FAQPage Schema
How do I audit a REST API for mass assignment vulnerabilities?

To audit a REST API for mass assignment vulnerabilities, you systematically probe profile update requests with extra fields like role or is_admin to detect if the endpoint improperly accepts and processes unauthorized parameter modifications.

What is JWT algorithm confusion and how does it expose API endpoints?

JWT algorithm confusion is a security misconfiguration where attackers manipulate the token header to bypass signature verification, exposing API endpoints by downgrading the validation logic to accept unsigned or symmetrically signed tokens.

How do I test for prototype pollution in modern web architectures?

You test for prototype pollution in modern web architectures by systematically probing API payloads to inject properties into base object prototypes, uncovering potential privilege escalation paths and logic vulnerabilities in the application layer.

Does this approach find CORS bypasses in OpenAPI documentation?

Yes, this approach maps attack surfaces by analyzing exposed OpenAPI documentation and systematically probing API responses to identify CORS bypasses and other security misconfigurations in RESTful interfaces.

What is the best way to map attack vectors in OData query layers?

The best way to map attack vectors in OData query layers is to audit the exposed OData interfaces and OpenAPI documentation, systematically probing query parameters to uncover authorization flaws and logic vulnerabilities.

When should I manually probe APIs instead of using standard automated scanners?

You should manually probe APIs to uncover subtle security flaws like mass assignment, JWT misconfigurations, and prototype pollution that often bypass standard automated scanners due to their complex and logic-dependent nature.