hunt-api-misconfig

Identify API misconfigurations enabling privilege escalation and data leakage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API security misconfigurations expose organizations to privilege escalation, data leakage, and broken auth flows across APIs, microservices, and serverless functions.

Core Features & Use Cases

  • API misconfig detection: identify mass-assignment, JWT flaws, prototype pollution, CORS weaknesses, and HTTP verb tampering.
  • Risk assessment & remediation guidance: prioritize findings and propose actionable fixes for both public and internal interfaces.
  • Use Case: accelerate security validation in CI/CD by surfacing misconfig patterns before release.

Quick Start

Run API misconfig tests against your endpoints and review results for mass assignment, JWT flaws, CORS, and HTTP verb weaknesses.

Frequently Asked Questions about hunt-api-misconfig

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

FAQPage Schema
How do I identify API misconfigurations like mass-assignment and JWT flaws?

Identify API misconfigurations by testing endpoints for mass-assignment, JWT flaws, prototype pollution, and CORS weaknesses to surface privilege escalation and data leakage risks.

What is prototype pollution and how does it affect microservices and serverless endpoints?

Prototype pollution is an API misconfiguration that corrupts object prototypes, enabling privilege escalation and data leakage across microservices and serverless endpoints.

Can I use this to detect CORS weaknesses and HTTP verb tampering in web APIs?

Yes, you can detect CORS weaknesses and HTTP verb tampering in web and mobile APIs by enumerating failure patterns and exploration steps to prioritize security risks.

How do I test for API security flaws before release in a CI/CD pipeline?

Run API misconfig tests against endpoints in CI/CD to validate security by surfacing mass assignment, JWT flaws, CORS, and HTTP verb weaknesses before release.

Does this approach provide remediation guidance for broken authentication flows?

Yes, it provides remediation guidance by proposing actionable fixes for broken authentication flows and other API security flaws found in public and internal interfaces.

What is the best way to prioritize API security risks across internal and public interfaces?

Prioritize API security risks across internal and public interfaces by enumerating failure patterns, exploration steps, and guardrails to assess mass-assignment and JWT vulnerabilities.