api-auth-and-jwt-abuse

Tests API authentication mechanisms for JWT weaknesses, header spoofing, and rate-limit bypasses.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill api-auth-and-jwt-abuse-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-auth-and-jwt-abuse
Source: https://github.com/lNwNl/Praxis/tree/main/skills/api-auth-and-jwt-abuse
Command: npx skills add https://github.com/lNwNl/Praxis --skill api-auth-and-jwt-abuse-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? APIs that rely on JWTs, bearer tokens, API keys, or client-supplied headers often contain trust-boundary flaws that are easy to miss during manual review. This Skill provides a structured playbook for systematically probing token validation, claim trust, header spoofing, and rate-limit enforcement during authorized security assessments. ## Core Features & Use Cases - Token Triage: Inspect JWT headers and claims such as alg, kid, jku, x5u, role, scope, issuer, and audience for trust and mismatch issues. - Attack Pattern Table: Quick-reference tests for alg:none acceptance, RS256-to-HS256 confusion, kid injection, attacker-controlled jku/x5u, and weak secret cracking. - Mass Assignment & Rate-Limit Bypass: Candidate hidden fields (role, isAdmin, plan, permissions) and header families (X-Forwarded-For, X-Real-IP, Forwarded) for bypassing rate limits and abusing batch requests. - Use Case: During a web CTF or authorized pentest, you receive a JWT from a login endpoint. Use this Skill to check whether the server accepts alg:none tokens, trusts a manipulated kid parameter, or lets you bypass login rate limits with X-Forwarded-For rotation. ## Quick Start Ask the agent to analyze the JWT from the target login response and test it for algorithm confusion, kid injection, and rate-limit bypass using the api-auth-and-jwt-abuse playbook.

Frequently Asked Questions about api-auth-and-jwt-abuse

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

FAQPage Schema
How do I test a JWT for algorithm confusion attacks?▼

Algorithm confusion testing switches the token from RS256 to HS256 and signs it with the server's public key as the HMAC secret. Also test alg:none by sending an unsigned token with a trailing dot to check if the server accepts it.

What JWT header parameters should I check during a pentest?▼

Inspect alg, kid, jku, and x5u header parameters first. The kid parameter may allow path traversal or injection, while jku and x5u may let the server fetch attacker-controlled keys from remote URLs.

How can rate limits be bypassed with HTTP headers?▼

Rate limits keyed on client IP can often be bypassed by rotating X-Forwarded-For, X-Real-IP, or Forwarded header values per request. Additional techniques include User-Agent rotation and path case or slash variants.

What is mass assignment in API testing?▼

Mass assignment occurs when an API binds client-supplied JSON fields directly to internal objects. Test by adding hidden fields like role, isAdmin, verified, plan, or permissions to requests and checking whether privileges change.

When should I use a different skill instead of this one?▼

For GraphQL batching and hidden parameter attacks use the graphql-and-hidden-parameters skill, for OAuth/OIDC flow flaws use oauth-oidc-misconfiguration, and for full JWT and OAuth depth use jwt-oauth-token-attacks.