jwt-inspector
Decode and security-audit a JSON Web Token — flag alg=none, missing/excessive expiry, symmetric-alg confusion risk, missing claims — and attempt an offline HMAC secret crack against a wordlist to detect weak signing keys. Use when the user asks to "decode this JWT", "is this toke
Install
npx skills add https://github.com/NovaCode37/claude-security-skills/tree/main/skills/jwt-inspector
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install novacode37-claude-security-skills@llmmart
git clone https://github.com/NovaCode37/claude-security-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole novacode37/claude-security-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
JWT Inspector
Decode and audit JSON Web Tokens with no third-party dependencies. It splits the token, decodes header + payload, evaluates them against a set of security checks, and (for HMAC tokens) tries a fast offline crack of the signing secret against a wordlist.
When to use this skill
- "Decode / inspect this JWT."
- "Is this token configured securely?"
- "Does this JWT use a weak/guessable secret?"
- Auditing auth tokens during a security review.
Checks performed
- alg=none (critical) — unsigned, forgeable token.
- Symmetric alg (HS)* — HMAC verification key == signing secret; HS/RS confusion and brute-force risk.
- Missing
exp/ token never expires; excessively long lifetime. iatin the future, missingnbf, missingiss/aud/sub.- Weak HMAC secret (critical) — cracked from a built-in or supplied wordlist.
How to run it
# Decode + audit
python skills/jwt-inspector/inspector.py "<token>"
# Read token from stdin
echo "<token>" | python skills/jwt-inspector/inspector.py -
# Try cracking the HMAC secret with a custom wordlist
python skills/jwt-inspector/inspector.py "<token>" --secret-list rockyou.txt
# JSON output
python skills/jwt-inspector/inspector.py "<token>" --json
# Only fail CI on high/critical (claim-hygiene notes are LOW)
python skills/jwt-inspector/inspector.py "<token>" --min-severity high
Exit codes: 0 clean · 1 issues reported · 2 malformed input.
Every reported issue fails the build. The default reports everything down to
info (including exp-past); raise --min-severity to low/medium/high
to filter advisory notes out of both the report and the exit code.
Recommended workflow for Claude
- Run the inspector and read the decoded payload to understand the token.
- Report findings ordered by severity; explain the impact of each.
- If a secret was cracked, stress that the key is compromised — rotate it and move to an asymmetric algorithm (RS256/ES256) where feasible.
- Never treat a decoded payload as trusted: decoding ≠ verifying. Remind the user that signature verification with the correct key is what matters.
Note
Cracking only runs for HMAC algorithms and only against the provided wordlist — it is a weak-key detector, not a brute-forcer. Only inspect tokens you are authorized to handle.
Files (claude-security-skills)
-
tests
-
test_inspector.py 6.5 KB
Loading…
-
-
inspector.py 8.3 KB
Loading… -
SKILL.md 2.7 KB
--- name: jwt-inspector description: >- Decode and security-audit a JSON Web Token — flag alg=none, missing/excessive expiry, symmetric-alg confusion risk, missing claims — and attempt an offline HMAC secret crack against a wordlist to detect weak signing keys. Use when the user asks to "decode this JWT", "is this token secure?", "audit a JWT", or "check if this token uses a weak secret". license: MIT --- # JWT Inspector Decode and audit JSON Web Tokens with **no third-party dependencies**. It splits the token, decodes header + payload, evaluates them against a set of security checks, and (for HMAC tokens) tries a fast offline crack of the signing secret against a wordlist. ## When to use this skill - "Decode / inspect this JWT." - "Is this token configured securely?" - "Does this JWT use a weak/guessable secret?" - Auditing auth tokens during a security review. ## Checks performed - **alg=none** (critical) — unsigned, forgeable token. - **Symmetric alg (HS*)** — HMAC verification key == signing secret; HS/RS confusion and brute-force risk. - **Missing `exp`** / token never expires; **excessively long** lifetime. - **`iat` in the future**, missing `nbf`, missing `iss`/`aud`/`sub`. - **Weak HMAC secret** (critical) — cracked from a built-in or supplied wordlist. ## How to run it ```bash # Decode + audit python skills/jwt-inspector/inspector.py "<token>" # Read token from stdin echo "<token>" | python skills/jwt-inspector/inspector.py - # Try cracking the HMAC secret with a custom wordlist python skills/jwt-inspector/inspector.py "<token>" --secret-list rockyou.txt # JSON output python skills/jwt-inspector/inspector.py "<token>" --json # Only fail CI on high/critical (claim-hygiene notes are LOW) python skills/jwt-inspector/inspector.py "<token>" --min-severity high ``` **Exit codes:** `0` clean · `1` issues reported · `2` malformed input. Every reported issue fails the build. The default reports everything down to `info` (including `exp-past`); raise `--min-severity` to `low`/`medium`/`high` to filter advisory notes out of both the report and the exit code. ## Recommended workflow for Claude 1. Run the inspector and read the decoded payload to understand the token. 2. Report findings ordered by severity; explain the impact of each. 3. If a secret was cracked, stress that the key is compromised — rotate it and move to an asymmetric algorithm (RS256/ES256) where feasible. 4. Never treat a decoded payload as trusted: decoding ≠ verifying. Remind the user that signature verification with the correct key is what matters. ## Note Cracking only runs for HMAC algorithms and only against the provided wordlist — it is a weak-key *detector*, not a brute-forcer. Only inspect tokens you are authorized to handle.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.