PCAP Practice Capture: answer key
Every question with its answer and the reasoning. Work the drill first, or the key only tells you what, not how.
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. How many packets are in the capture?
Packets: 152 Bytes: 15666 First seen: 2026-09-14T13:02:11Z Last seen: 2026-09-14T13:14:11Z Protocol mix: UDP 26, TCP 126
Answer: 152
152 packets. Record the count and the time window before anything else: they bound every later claim ("no other traffic to that host in the capture") and they are what the next analyst checks your copy against.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. One domain is queried repeatedly for TXT records, each time with a different random-looking label in front. What is that parent domain?
DNS queries Name Type Count --------------------------- ---- ----- www.example.com A 2 updates.example.org A 2 portal.example-sso.test A 2 4d5a9000.q.sync.example.net TXT 2 03000000.q.sync.example.net TXT 2 04000000.q.sync.example.net TXT 2 ffff0000.q.sync.example.net TXT 2 b8000000.q.sync.example.net TXT 2 0e1fba0e.q.sync.example.net TXT 2 00b409cd.q.sync.example.net TXT 2 21b8014c.q.sync.example.net TXT 2 cd215468.q.sync.example.net TXT 2
Answer: q.sync.example.net
q.sync.example.net. 9 TXT queries, each with a unique, hex-looking leftmost label under the same parent. The constant parent is the attacker-controlled zone; the varying label is the payload.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. What does that run of TXT lookups most likely represent?
DNS queries Name Type Count --------------------------- ---- ----- www.example.com A 2 updates.example.org A 2 portal.example-sso.test A 2 4d5a9000.q.sync.example.net TXT 2 03000000.q.sync.example.net TXT 2 04000000.q.sync.example.net TXT 2 ffff0000.q.sync.example.net TXT 2 b8000000.q.sync.example.net TXT 2 0e1fba0e.q.sync.example.net TXT 2 00b409cd.q.sync.example.net TXT 2 21b8014c.q.sync.example.net TXT 2 cd215468.q.sync.example.net TXT 2
Answer: DNS tunnelling: data carried in the query names and TXT answers
Unique high-entropy labels under one parent, requested as TXT, from a workstation rather than a mail server. SPF/DKIM lookups go to the sending domain's _domainkey or apex, not to random subdomains; retries repeat the same name. No single query here is suspicious. The pattern is.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. What host and URI did the one HTTP GET request ask for? Answer as host/uri.
HTTP requests Method Host URI Count ------ ------------------- -------------------- ----- GET updates.example.org /pkg/agent-2.4.1.msi 1
Answer: updates.example.org/pkg/agent-2.4.1.msi
updates.example.org/pkg/agent-2.4.1.msi. The Host header plus the request URI is the full resource. A .bin pulled over cleartext HTTP is either an update mechanism doing something unwise or a stager. The next step is the proxy logs and the file itself, not the packet.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. The TLS session is encrypted. Which server name can you still read from its ClientHello?
TLS server names SNI Servers Count ----------------------- ------------ ----- portal.example-sso.test 203.0.113.80 1
Answer: portal.example-sso.test
portal.example-sso.test. Server Name Indication rides in the cleartext ClientHello so the server can pick a certificate. It is client-asserted, so it says what the client asked for, not what it reached, and Encrypted Client Hello removes it entirely.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. One external address receives a long run of small, near-identical TCP conversations. Which address and port? Answer as ip:port.
Conversations Source Destination Proto Packets Bytes First seen ---------------- ------------------ ----- ------- ----- -------------------- 192.0.2.50:123 198.51.100.123:123 UDP 2 180 2026-09-14T13:02:11Z 192.0.2.1:53 192.0.2.50:50001 UDP 2 166 2026-09-14T13:02:12Z 192.0.2.50:49811 198.51.100.10:443 TCP 6 1664 2026-09-14T13:02:12Z 192.0.2.1:53 192.0.2.50:50002 UDP 2 174 2026-09-14T13:02:31Z 192.0.2.50:49820 198.51.100.20:80 TCP 6 517 2026-09-14T13:02:31Z 192.0.2.1:53 192.0.2.50:50003 UDP 2 182 2026-09-14T13:02:52Z 192.0.2.50:49833 203.0.113.80:443 TCP 6 570 2026-09-14T13:02:52Z 192.0.2.1:53 192.0.2.50:53100 UDP 2 189 2026-09-14T13:03:11Z 192.0.2.1:53 192.0.2.50:53101 UDP 2 189 2026-09-14T13:03:13Z 192.0.2.1:53 192.0.2.50:53102 UDP 2 189 2026-09-14T13:03:16Z 192.0.2.1:53 192.0.2.50:53103 UDP 2 189 2026-09-14T13:03:18Z 192.0.2.1:53 192.0.2.50:53104 UDP 2 189 2026-09-14T13:03:21Z 192.0.2.1:53 192.0.2.50:53105 UDP 2 189 2026-09-14T13:03:23Z 192.0.2.1:53 192.0.2.50:53106 UDP 2 189 2026-09-14T13:03:26Z 192.0.2.1:53 192.0.2.50:53107 UDP 2 189 2026-09-14T13:03:28Z 192.0.2.1:53 192.0.2.50:53108 UDP 2 189 2026-09-14T13:03:31Z 192.0.2.50:50300 203.0.113.99:9443 TCP 6 432 2026-09-14T13:03:41Z 192.0.2.50:50301 203.0.113.99:9443 TCP 6 432 2026-09-14T13:04:26Z 192.0.2.50:49900 198.51.100.10:443 TCP 6 1344 2026-09-14T13:04:31Z 192.0.2.50:50302 203.0.113.99:9443 TCP 6 432 2026-09-14T13:05:11Z 192.0.2.50:50303 203.0.113.99:9443 TCP 6 432 2026-09-14T13:05:56Z 192.0.2.50:50304 203.0.113.99:9443 TCP 6 432 2026-09-14T13:06:41Z 192.0.2.50:50305 203.0.113.99:9443 TCP 6 432 2026-09-14T13:07:26Z 192.0.2.50:50306 203.0.113.99:9443 TCP 6 432 2026-09-14T13:08:11Z 192.0.2.50:49901 198.51.100.10:443 TCP 6 1344 2026-09-14T13:08:28Z 192.0.2.50:50307 203.0.113.99:9443 TCP 6 432 2026-09-14T13:08:56Z 192.0.2.50:50308 203.0.113.99:9443 TCP 6 432 2026-09-14T13:09:41Z 192.0.2.50:50309 203.0.113.99:9443 TCP 6 432 2026-09-14T13:10:26Z 192.0.2.50:50310 203.0.113.99:9443 TCP 6 432 2026-09-14T13:11:11Z 192.0.2.50:50311 203.0.113.99:9443 TCP 6 432 2026-09-14T13:11:56Z 192.0.2.50:49902 198.51.100.10:443 TCP 6 1344 2026-09-14T13:12:23Z 192.0.2.50:50312 203.0.113.99:9443 TCP 6 432 2026-09-14T13:12:41Z 192.0.2.50:50313 203.0.113.99:9443 TCP 6 432 2026-09-14T13:13:26Z 192.0.2.50:50314 203.0.113.99:9443 TCP 6 432 2026-09-14T13:14:11Z
Answer: 203.0.113.99:9443
203.0.113.99:9443. 15 short conversations, same size each time, asymmetric (a small POST out, a small reply back). Grouping the conversation table by destination is what makes it visible; in packet order it is interleaved with everything else.
Read more: PCAP Triage
-
Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. Those conversations to 203.0.113.99:9443 start at a fixed interval. How many seconds apart are they?
Conversations Source Destination Proto Packets Bytes First seen ---------------- ------------------ ----- ------- ----- -------------------- 192.0.2.50:123 198.51.100.123:123 UDP 2 180 2026-09-14T13:02:11Z 192.0.2.1:53 192.0.2.50:50001 UDP 2 166 2026-09-14T13:02:12Z 192.0.2.50:49811 198.51.100.10:443 TCP 6 1664 2026-09-14T13:02:12Z 192.0.2.1:53 192.0.2.50:50002 UDP 2 174 2026-09-14T13:02:31Z 192.0.2.50:49820 198.51.100.20:80 TCP 6 517 2026-09-14T13:02:31Z 192.0.2.1:53 192.0.2.50:50003 UDP 2 182 2026-09-14T13:02:52Z 192.0.2.50:49833 203.0.113.80:443 TCP 6 570 2026-09-14T13:02:52Z 192.0.2.1:53 192.0.2.50:53100 UDP 2 189 2026-09-14T13:03:11Z 192.0.2.1:53 192.0.2.50:53101 UDP 2 189 2026-09-14T13:03:13Z 192.0.2.1:53 192.0.2.50:53102 UDP 2 189 2026-09-14T13:03:16Z 192.0.2.1:53 192.0.2.50:53103 UDP 2 189 2026-09-14T13:03:18Z 192.0.2.1:53 192.0.2.50:53104 UDP 2 189 2026-09-14T13:03:21Z 192.0.2.1:53 192.0.2.50:53105 UDP 2 189 2026-09-14T13:03:23Z 192.0.2.1:53 192.0.2.50:53106 UDP 2 189 2026-09-14T13:03:26Z 192.0.2.1:53 192.0.2.50:53107 UDP 2 189 2026-09-14T13:03:28Z 192.0.2.1:53 192.0.2.50:53108 UDP 2 189 2026-09-14T13:03:31Z 192.0.2.50:50300 203.0.113.99:9443 TCP 6 432 2026-09-14T13:03:41Z 192.0.2.50:50301 203.0.113.99:9443 TCP 6 432 2026-09-14T13:04:26Z 192.0.2.50:49900 198.51.100.10:443 TCP 6 1344 2026-09-14T13:04:31Z 192.0.2.50:50302 203.0.113.99:9443 TCP 6 432 2026-09-14T13:05:11Z 192.0.2.50:50303 203.0.113.99:9443 TCP 6 432 2026-09-14T13:05:56Z 192.0.2.50:50304 203.0.113.99:9443 TCP 6 432 2026-09-14T13:06:41Z 192.0.2.50:50305 203.0.113.99:9443 TCP 6 432 2026-09-14T13:07:26Z 192.0.2.50:50306 203.0.113.99:9443 TCP 6 432 2026-09-14T13:08:11Z 192.0.2.50:49901 198.51.100.10:443 TCP 6 1344 2026-09-14T13:08:28Z 192.0.2.50:50307 203.0.113.99:9443 TCP 6 432 2026-09-14T13:08:56Z 192.0.2.50:50308 203.0.113.99:9443 TCP 6 432 2026-09-14T13:09:41Z 192.0.2.50:50309 203.0.113.99:9443 TCP 6 432 2026-09-14T13:10:26Z 192.0.2.50:50310 203.0.113.99:9443 TCP 6 432 2026-09-14T13:11:11Z 192.0.2.50:50311 203.0.113.99:9443 TCP 6 432 2026-09-14T13:11:56Z 192.0.2.50:49902 198.51.100.10:443 TCP 6 1344 2026-09-14T13:12:23Z 192.0.2.50:50312 203.0.113.99:9443 TCP 6 432 2026-09-14T13:12:41Z 192.0.2.50:50313 203.0.113.99:9443 TCP 6 432 2026-09-14T13:13:26Z 192.0.2.50:50314 203.0.113.99:9443 TCP 6 432 2026-09-14T13:14:11Z
Answer: 45
45 seconds, with no jitter at all. Real implants usually add jitter to defeat exactly this check, so a perfectly regular interval is either unsophisticated tooling or a legitimate heartbeat. The destination decides which.
Read more: PCAP Triage
-
Why can the beacon not be spotted by inspecting any single packet?
Answer: Each packet is small and ordinary; the signal is the repetition and the timing across many conversations
Beaconing is a property of the aggregate: count, size regularity and inter-arrival time. That is why triage starts from conversations and not from packets, and why the same analysis on Zeek conn.log is the standard hunt at scale.
Read more: PCAP Triage
-
Match each finding to the panel of the tool that shows it.
Answer: The 45-second check-ins to 203.0.113.99:9443 → Conversations · Random-looking labels under q.sync.example.net → DNS queries · The download of /pkg/agent-2.4.1.msi → HTTP requests · The name portal.example-sso.test on an encrypted session → TLS server names · Which pair of hosts moved the most bytes → Conversations
The four panels map onto the four questions of first-pass network triage. Byte volume and timing live in Conversations; content-level indicators only exist where the protocol is readable (DNS, HTTP) or where the handshake leaks it (TLS SNI).
Read more: PCAP Triage
-
You are handed an unfamiliar capture. Order the first-pass triage steps.
Answer: Note the packet count, time window and protocol mix Rank conversations by volume and look for regular timing Read DNS, HTTP and TLS names for indicators Pull the full packets for the few flows that matter
Scope, then shape, then content, then detail. Opening packets first is the classic way to spend an hour on a capture and miss the beacon, because packet order interleaves every flow. Each step decides which small part of the capture the next step reads.
Read more: PCAP Triage