Skip to main content
Network forensics challenges give you a packet capture and ask you to reconstruct what happened on the wire. The flag might be sitting in plaintext inside an HTTP request body, encoded across dozens of DNS queries, transferred over FTP, or locked inside a TLS session waiting for you to apply the provided key material. Your job is to approach the capture systematically: understand the traffic landscape first, then drill into the streams and protocols most likely to carry the payload.

Challenge Setup

You receive a file — typically capture.pcap or capture.pcapng — and a brief prompt that may hint at a protocol (“someone was browsing the web”) or say nothing at all. Open it in Wireshark for a visual overview, then switch to tshark for targeted filtering and bulk extraction. Both tools read the same file format, so you can move between them freely as the analysis demands.

Common Wireshark Filters Reference

Last modified on July 23, 2026