Tool Files & Artifacts
PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
A first pass over a capture: who talked to whom, how much moved, which names were looked up and which TLS servers were asked for. It is not Wireshark, and it does not reassemble streams or decrypt anything.
This runs in your browser. Nothing you type or open is uploaded.
How to read it
Sort conversations by bytes to find the big transfer. Look for many short connections to one host at a regular interval, which is the shape of a beacon.
Read the DNS list for names that look generated, then match them to the TLS SNI list.
Packets the parser could not descend into are counted, not hidden. The note above the tables says how many and why.
Terms behind it
- Packet Capture: Recording raw network frames off the wire for later analysis.
- Beaconing: Malware 'phoning home' on a regular interval.
- DNS Tunneling: Smuggling data or C2 inside DNS queries and responses.
- TLS Handshake: The negotiation that sets up an encrypted TLS connection.
- JA3 Fingerprinting: Hashing TLS handshake fields to fingerprint the client software.
- Command and Control: The channel an attacker uses to control compromised hosts.
Sources
- PCAP Next Generation (pcapng) specification. The block structure this tool reads for .pcapng files: section header, interface description and enhanced packet blocks, including the timestamp-resolution option.
- tcpdump / libpcap. The classic capture format's home, and the tool that writes most of the files you will open here.
Worth using too
- Wireshark. The real dissector. Everything this page deliberately does not do (stream reassembly, thousands of protocol dissectors, decryption with keys) it does properly.
- Zeek. Turns a capture into structured logs instead of packets, which is the right move once a capture is too large to page through.