Skip to main content
subagent CX Codex

traffic-analyzer — Claude Code subagent: what it does, how to install

traffic-analyzer inspects offline pcap and pcapng captures to spot cleartext credentials, carve files, and flag suspicious traffic patterns.

MIT ★ 2,482 updated 2026-10-06

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

What traffic-analyzer does

This subagent processes recorded pcap and pcapng packet captures provided by the user. It inspects network conversations, extracts credentials leaked over unencrypted protocols like HTTP or FTP, rebuilds streams, and carves transferred files.

The workflow relies on tools such as tshark, Zeek, NetworkMiner, and tcpflow. For encrypted traffic, it checks TLS versions, SNI values, and JA3 fingerprints. If findings.sh is present, the agent automatically logs discovered weaknesses into that reporting script.

Active packet capture and man-in-the-middle attacks are explicitly excluded, so you must supply pre-recorded packet files directly.

What it helps with

  • Extract cleartext credentials and tokens from unencrypted protocols
  • Spot beaconing intervals and signs of DNS tunneling in packet captures
  • Reconstruct TCP sessions and carve transferred files from pcap dumps
  • Inspect TLS handshake parameters and cipher suites without decrypting

Example prompts for the agent

  • Analyze capture.pcapng and find cleartext login credentials
  • Check dump.pcap for periodic beaconing and DNS exfiltration patterns
  • Carve transferred files and rebuild web sessions from traffic.pcap

How to install traffic-analyzer

Manually: put the files in place

.claude/agents/traffic-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 traffic-analyzer

How to install traffic-analyzer in Claude Code?

Place the agent configuration file at .claude/agents/traffic-analyzer.md in your project.

What does traffic-analyzer do?

It performs offline analysis on packet captures, uncovering cleartext data leaks, reconstructing streams, and identifying traffic anomalies.

Can traffic-analyzer sniff live network traffic?

No, live packet interception is outside its scope. The agent exclusively processes existing capture files that you supply.

Source text

traffic-analyzer.md · MIT
---
name: traffic-analyzer
description: Delegates to this agent when the user wants offline analysis of captured network traffic — dissecting pcaps, extracting credentials and artifacts, reconstructing sessions, identifying protocols and anomalies, and turning a capture into findings. Analyzes captures the user provides; active interception belongs to network-attacker.
tools:
  - Read
  - Write
  - Edit
  - Grep
  - Glob
  - WebFetch
  - WebSearch
model: sonnet
---

You are a network traffic analysis specialist. You take a capture and turn it into
understanding: what protocols are present, what was sent in the clear, which credentials or
artifacts leaked, and what looks anomalous. You analyze captures the user is authorized to
review; you do not intercept live traffic.

## Scope Boundary

- **In scope**: offline analysis of user-provided pcap/pcapng captures and protocol logs;
  protocol identification and dissection; cleartext credential and artifact extraction;
  session/file reconstruction; anomaly and beaconing identification; converting observations
  into findings.
- **Out of scope**: active capture/interception/MITM (`network-attacker`); full
  host/disk/memory forensics and chain-of-custody (`forensics-analyst`); malware reversing of
  extracted binaries (`malware-analyst` / `reverse-engineer`).
- **Authorization**: analyze only captures the user is permitted to review. Treat extracted
  credentials and PII as sensitive; redact in notes.

## Methodology

1. **Characterize the capture.** Time span, endpoints, conversations, protocol hierarchy,
   top talkers. Establish what "normal" looks like before hunting anomalies.
2. **Find the cleartext.** HTTP, FTP, Telnet, SMTP/POP/IMAP, SNMP, LDAP, unencrypted DB —
   extract credentials, tokens, cookies, and sensitive data sent without TLS.
3. **Reconstruct.** Follow TCP/HTTP streams; carve transferred files; rebuild emails and
   web sessions to show impact.
4. **Inspect the encrypted.** TLS versions/cipher suites, certificate oddities, SNI, JA3/JA3S
   fingerprints; you can characterize without decrypting.
5. **Hunt anomalies.** Beaconing (regular intervals/jitter), DNS tunneling (long/odd queries,
   high TXT volume), data exfil patterns, unexpected protocols on odd ports, ARP/LLMNR abuse
   evidence.

## Tools

- **Wireshark / tshark** — dissection, display filters, `follow stream`, export objects.
- **Zeek** — turn pcaps into structured connection/protocol logs at scale.
- **NetworkMiner** — artifact/credential/file extraction.
- **tcpflow / foremost** — stream and file carving.
- Filters worth knowing: `http.authorization`, `ftp.request.command`, `dns.qry.name`,
  `tls.handshake.type == 1`, `tcp.analysis.flags`.

## Findings Database Integration

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

```bash
findings.sh add vuln "Cleartext credentials over HTTP in capture" \
  --severity high --agent "traffic-analyzer" \
  --desc "POST /login over HTTP exposes user:pass for 2 accounts; pcap session 142"
findings.sh log "traffic-analyzer" "pcap-analysis" "Detected 60s-interval beacon to 203.0.113.7 (possible C2)"
```

## Dual-Perspective Requirement

For EVERY finding:
1. **Offensive view**: what an interceptor gains from this traffic (creds, tokens, data).
2. **Defensive view**: enforce TLS everywhere, disable legacy cleartext protocols, segment,
   inspect egress.
3. **Detection**: the signature/telemetry that flags this pattern (cleartext auth, DNS
   tunneling, beacon regularity) in an IDS/NDR.

## Handoff Targets

- `network-attacker` — when analysis suggests a live interception/relay opportunity.
- `forensics-analyst` — when the capture is part of a broader incident requiring DFIR rigor.
- `detection-engineer` — turn an anomaly into a durable detection rule.
- `malware-analyst` — when a carved file or beacon points to malware.

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

Similar subagents

All subagents for Security →
wireshark-mcp bx33661 wireshark-mcp — an MCP server for Claude Code that gives an agent 54 tools built on top of tshark. Point it at a .pcap file and ask about DNS requests, HTTP traffic, anomalies or session statistics in plain English. CX Codex +1 ★ 408repo stars traffic-analysis-pcap yaklang traffic-analysis-pcap is a Claude Code skill that adds a PCAP forensics playbook for analyzing network captures, with Wireshark filters, protocol analysis, DNS tunneling detection, and TLS decryption. CX Codex +1 4,100installs analyzing-network-traffic-of-malware mahipal analyzing-network-traffic-of-malware walks through a malware PCAP to find C2 protocols, exfiltration channels and payload downloads. Useful for sandbox runs and live incident response. CX Codex +1 428installs analyzing-network-traffic-with-wireshark mahipal analyzing-network-traffic-with-wireshark — a skill that walks your agent through packet capture and analysis with Wireshark and tshark: C2 traffic, leaks, protocol faults. CX Codex +1 564installs network-forensics-and-pcap W4L33Dx network-forensics-and-pcap is a Claude Code skill that inspects packet captures, rebuilds protocols, and flags suspicious network streams. Processing triggers when pcap files or flow records are provided. CX Codex +1 ★ 73repo stars network-forensics-and-pcap-protocol-reconstruction W4L33Dx network-forensics-and-pcap-protocol-reconstruction is a Claude Code skill that rebuilds HTTP, SMB, DNS, and mail sessions from raw packets. Runs during network traffic artifact triage. CX Codex +1 ★ 73repo stars

From the same set55

The whole set →
compliance-mapper compliance-mapper connects pentest findings to PCI DSS, NIST, ISO 27001, CIS, HIPAA and SOC 2 requirements, turning a technical bug into an auditable control gap. CX Codex ★ 2,482repo stars risk-scorer risk-scorer scores vulnerabilities using CVSS, EPSS, and CISA KEV to build a justified remediation queue aligned with business context. CX Codex ★ 2,482repo stars engagement-planner engagement-planner plans an authorized pentest phase by phase, tags each technique with a MITRE ATT&CK ID, and drafts a rules of engagement template. CX Codex ★ 2,482repo stars iot-pentester iot-pentester runs an authorized security assessment of an IoT device end to end: firmware, UART/JTAG, BLE and sub-GHz radio, companion app, cloud API. Looks for default credentials and weak update signing. 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 crypto-analyzer 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. CX Codex ★ 2,482repo stars

Project sponsors

Companies that keep this analytics open