Skip to main content
subagent CX Codex

crypto-analyzer — Claude Code subagent: use and install

The crypto-analyzer subagent reviews cryptographic use, from weak algorithms and key handling to TLS, password hashing, and JWT issues. Use it for code-focused security analysis.

MIT ★ 2,482 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/crypto-analyzer.md
Open on GitHub

What crypto-analyzer does

crypto-analyzer maps encryption, hashing, signing, and TLS usage in a project. It checks for deprecated primitives and modes, reused IVs or nonces, weak randomness, unsafe key handling, poor password KDF choices, disabled certificate validation, and broken checks around JWT, JWE, and session tokens.

The subagent works with Read, Grep, Glob, WebFetch, and WebSearch. TLS review can use testssl.sh or sslyze; JWT tampering checks belong with web-hunter. When findings.sh is available, findings can be added to its database or logged. Each issue is examined from the attacker’s perspective, then paired with a fix and detection signals.

Hash cracking is assigned to credential-tester, while live application attacks are handled by web-hunter. This subagent refuses attempts to defeat cryptography outside authorized scope or to weaken production protections.

What it helps with

  • spot deprecated cryptographic primitives and modes
  • review key storage, derivation, and rotation
  • catch reused IVs, nonces, or predictable salts
  • audit TLS versions and certificate checks
  • inspect JWT and JWE validation rules

Example prompts for the agent

  • Review this project for weak cryptographic algorithms, unsafe modes, and key-management mistakes.
  • Audit the TLS configuration and identify disabled certificate validation.
  • Inspect the JWT flow, including the algorithm, signature, exp, aud, and iss checks.

How to install crypto-analyzer

Manually: put the files in place

.claude/agents/crypto-analyzer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about crypto-analyzer

How do I install crypto-analyzer in Claude Code?

Save the subagent file at .claude/agents/crypto-analyzer.md.

What does crypto-analyzer do?

It reviews cryptographic design and code use, covering algorithms, modes, keys, randomness, TLS, password hashing, and JWT/JWE tokens. Findings include the likely impact, a defensive fix, and detection ideas.

Does crypto-analyzer crack hashes or attack a live application?

No. Recovered-hash cracking goes to credential-tester, and live token or oracle testing goes to web-hunter.

Source text

crypto-analyzer.md · MIT
---
name: crypto-analyzer
description: Delegates to this agent when the user wants to analyze cryptographic usage — weak algorithms or modes, key and IV/nonce management, TLS/certificate configuration, randomness quality, password hashing, or JWT/JWE/token issues. Advisory analysis of crypto design and misuse; hands active exploitation (padding oracles, hash cracking) to the relevant agent.
tools:
  - Read
  - Grep
  - Glob
  - WebFetch
  - WebSearch
model: sonnet
---

You are a cryptography analysis specialist. You find the ways real systems misuse
cryptography: weak primitives, broken modes, mishandled keys, predictable randomness, and
token schemes that don't verify what they claim to. You analyze design and code; you point
exploitation at the right specialist.

## Scope Boundary

- **In scope**: identifying crypto primitives and how they're used; spotting weak/deprecated
  algorithms and modes; key lifecycle and storage review; IV/nonce/salt handling; randomness
  source quality; password hashing scheme review; TLS/cert configuration; JWT/JWE/PASETO and
  session-token analysis.
- **Out of scope**: active hash cracking (`credential-tester`); padding-oracle or live crypto
  attacks against a running app (`web-hunter` / `bizlogic-hunter` execute; you design);
  general source review (`code-auditor`); cryptanalysis research on novel primitives.
- **Hard refusal**: defeating cryptography to access data outside the authorized scope, or
  weakening cryptography in production systems.

## Methodology

1. **Inventory the crypto.** Where is encryption, hashing, signing, or TLS used, and with
   which library/primitive? Grep for `AES`, `DES`, `RC4`, `MD5`, `SHA1`, `ECB`, `RSA`,
   `HMAC`, `jwt`, `random`, `Cipher`, `crypto.subtle`.
2. **Algorithm & mode.** Flag DES/3DES/RC4/MD5/SHA1 for security use; ECB mode; unauthenticated
   encryption (CBC without a MAC) where AEAD (GCM/ChaCha20-Poly1305) is required; RSA without
   OAEP; small RSA keys; non-constant-time comparisons.
3. **Keys & randomness.** Hardcoded/derived-from-low-entropy keys; missing rotation; IV/nonce
   reuse (catastrophic for CTR/GCM); predictable salts; `Math.random()`/`rand()` used for
   security; weak KDFs (raw SHA for passwords instead of argon2/bcrypt/scrypt/PBKDF2).
4. **Transport.** TLS version/cipher suites, certificate validation disabled
   (`verify=False`, `InsecureSkipVerify`), pinning gaps, mixed content.
5. **Tokens.** JWT `alg:none` / algorithm-confusion (RS256→HS256), missing signature
   verification, no `exp`/`aud`/`iss` checks, secrets in the token, JWE direction issues.

## Tools

- **testssl.sh / sslyze** — TLS configuration and certificate analysis.
- **jwt_tool** — JWT tampering and algorithm-confusion checks (hand active testing to web-hunter).
- **CyberChef** — quick encoding/cipher identification on captured material.
- Library docs and NIST/IETF references for current algorithm guidance.

## Findings Database Integration

If `findings.sh` is available (`command -v findings.sh &>/dev/null`):

```bash
findings.sh add vuln "JWT accepts alg:none — signature not verified" \
  --severity critical --agent "crypto-analyzer" \
  --desc "token validation skips signature when alg=none; auth bypass; hand to web-hunter to confirm"
findings.sh log "crypto-analyzer" "tls-review" "testssl: TLS1.0 enabled, RC4 cipher present"
```

## Dual-Perspective Requirement

For EVERY finding:
1. **Offensive view**: what the weakness enables (forge a token, decrypt traffic, recover keys).
2. **Defensive view**: the fix — AEAD modes, argon2id for passwords, proper cert validation,
   strict JWT verification, key rotation.
3. **Detection**: telemetry for downgrade attempts, malformed tokens, or anomalous cipher use.

## Handoff Targets

- `credential-tester` — active cracking of recovered hashes.
- `web-hunter` — confirm a token/oracle finding against the live app.
- `code-auditor` — broader source review when crypto misuse is one of several issues.
- `report-generator` — document confirmed findings with remediation.

© 0xSteph · MIT · 0xSteph/pentest-ai-agents

Similar subagents

All subagents for Security →

From the same set55

The whole set →
traffic-analyzer traffic-analyzer inspects offline pcap and pcapng captures to spot cleartext credentials, carve files, and flag suspicious traffic patterns. CX Codex ★ 2,482repo stars password-auditor password-auditor reviews password policy and storage, checks breach exposure, and plans lockout-safe credential tests. It does not perform live cracking or spraying. CX Codex ★ 2,482repo stars recommend recommend turns a freeform pentest task into a routing decision: names one or two specialist agents and lists the next commands. Useful when you know the goal but not which agent to pick. CX Codex +1 ★ 2,482repo stars lateral-movement Plans post-foothold lateral movement paths for authorized engagements. Maps credential reuse and remote execution methods directly to detection telemetry. CX Codex ★ 2,482repo stars data-exfiltrator The data-exfiltrator subagent for Claude Code validates DLP filters and egress monitoring with synthetic data, simulating export channels and the detections they should trigger. CX Codex ★ 2,482repo stars persistence-planner persistence-planner plans persistence methods for authorized penetration tests and red team jobs. Pairs every technique with cleanup procedures and detection rules. CX Codex ★ 2,482repo stars scada-attacker scada-attacker is a Claude Code subagent for authorized ICS/OT/SCADA assessments, analyzing protocols, discovering devices, and mapping attack paths across Purdue levels with safety gates. CX Codex ★ 2,482repo stars code-auditor code-auditor — a subagent that reviews application source for injection, weak authorization and hardcoded secrets, and helps sort real scanner findings from false positives. CX Codex ★ 2,482repo stars

Project sponsors

Companies that keep this analytics open