offensive-jwt

Identify and exploit JWT authentication weaknesses across web and mobile targets.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/din4e/Skills4RedTeam --skill offensive-jwt-din4e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offensive-jwt
Source: https://github.com/din4e/Skills4RedTeam/tree/main/skills/offensive-jwt
Command: npx skills add https://github.com/din4e/Skills4RedTeam --skill offensive-jwt-din4e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JWT-based authentication systems are frequently insecure due to misconfigurations and implementation flaws. This skill provides a comprehensive methodology to identify and exploit weaknesses, enabling defenders to validate and harden token handling in web and mobile apps.

Core Features & Use Cases

  • Algorithm confusion checks: detect bypasses like alg:none or confusion between RS256 and HS256.
  • Weak secret brute-forcing: assess resilience against guessable or weak HMAC secrets.
  • Header manipulation: test injection vectors via kid, jku, jwk, and x5u fields.
  • JWKS caching & trust: evaluate JWKS retrieval and cache poisoning risks.
  • JWS/JWE confusion: identify improper handling of signed vs encrypted tokens.
  • Token binding & mobile storage analysis: assess token storage risks on mobile platforms and session binding issues.
  • Use Case: Validate an API protected by JWT in a web or mobile app by applying the above techniques to identify weaknesses and propose hardening strategies.

Quick Start

Begin by locating JWT usage in the target application and apply the listed techniques to test token validation and replay protections.

Frequently Asked Questions about offensive-jwt

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

FAQPage Schema
How do I test JWT authentication for algorithm confusion vulnerabilities?

JWT algorithm confusion testing detects bypasses like alg:none or RS256/HS256 key mixing. You apply structured checks to identify improper token validation and harden authentication on target APIs.

What JWT header injection vectors should I check during penetration testing?

JWT header injection testing targets the kid, jku, jwk, and x5u fields. Manipulating these parameters exposes server-side trust issues and JWKS cache poisoning risks.

Can I brute force weak HMAC secrets in JWT tokens?

Weak HMAC secret brute-forcing assesses token resilience against guessable keys. You test token signatures to validate if applications enforce strong secret policies.

Does JWT security testing cover mobile app token storage extraction?

JWT security testing evaluates mobile platform token storage risks and session binding issues. It validates whether mobile targets expose reusable credentials insecurely.

What is the best way to identify JWS and JWE confusion in token validation?

JWS/JWE confusion testing identifies improper handling of signed versus encrypted tokens. You test server endpoints to see if encrypted tokens bypass signature validation logic.

Are there limitations when testing JWT validation without leaking credentials?

Authorized JWT testing minimizes data exposure by validating server-side protections without leaking secrets. You must ensure scope authorization before applying replay or timing attacks.