binary background

TryHackMe — Warzone2

A medium-difficulty network forensics challenge that tests your ability to analyze malicious traffic, IDS alerts, and incident patterns using Wireshark and Brim.

TryHackMe Warzone2 banner
The Warzone banner above links to the official TryHackMe room.

Hello everyone! This challenge on TryHackMe has a difficulty rating of medium. Depending on your experience, it may feel easier or harder. You’re currently working as a T1 Security Analyst for an MSSP investigating alerts: Misc activity, A Network Trojan Was Detected, and Potential Corporate Privacy Violation.

Typically, such alerts would originate from an IDS or IPS, but in this case, you must manually verify whether they are true positives or false positives. Once you spawn the provided machine, you’ll find a Tools directory and a Zone2.pcap file on the desktop. Open Wireshark (Applications → Wireshark → File → Open) and load the PCAP to begin analysis.

I started with Wireshark to spot anything suspicious before touching Brim or Network Miner — and indeed, I found something: an IP address that downloaded an odd-looking file. Right-click packet #6 and select Follow → HTTP Stream to inspect the full transfer sequence.

Next, we’ll go through the challenge questions step by step.

Investigation Process

For the first two questions, I used Brim — a fantastic tool for packet analysis that I plan to use more at work. Launch it from the Applications menu or via terminal. Once open, drag in Zone2.pcap and search using the IP you observed in Wireshark (from packet #6). You’ll see the alerts populate. Double-clicking any of them opens a detailed alert view.

Alert Signature 1
  1. Q1. What was the alert signature for “A Network Trojan was Detected”?
    Ans: ET MALWARE Likely Evil EXE download from MSXMLHTTP non-exe extension M2
  2. Alert Signature 2
  3. Q2. What was the alert signature for “Potential Corporate Privacy Violation”?
    Ans: ET POLICY PE EXE or DLL Windows file download HTTP
For the questions that follow, answers must be defanged. In CyberChef, use the Defang functions for URLs or IPs as appropriate.
  1. Q3. What was the IP that triggered either alert (defanged)?
    Ans: 185[.]118[.]164[.]8
  2. Malicious URI screenshot
    You’ll need both parts from the HTTP alert to build this answer.
  3. Q4. Provide the full URI for the malicious downloaded file (defanged).
    Ans: awh93dhkylps5ulnq-be[.]com/czwih/fxla[.]php?l=gap1[.]cab
  4. To get the next answer, find the file hash and check it in VirusTotal. You can extract the file from Wireshark and compute its hash with: sha1sum <filename>
  5. Q5. What is the name of the payload within the CAB file?
    Ans: draw.dll
  6. Q6. What is the User-Agent associated with this network traffic?
    Ans: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; WOW64; Trident/8.0; .NET4.0C; .NET4.0E)
The following query helps reveal other hostnames observed in HTTP GETs:
method=="GET" | cut ip, host, status_code
Check those hosts on VirusTotal to confirm malicious domains.
  1. Q7. What other domains were labeled as malicious by VirusTotal? (alphabetical, defanged)
    Ans: a-zcorner[.]com, knockoutlights[.]com
  2. For IPs flagged as “Not Suspicious Traffic”, review Suricata alerts by Source/Destination and note the corresponding IPs.
  3. Q8. Which IPs were flagged as Not Suspicious Traffic? (defanged, numerical order)
    Ans: 64[.]225[.]65[.]166, 142[.]93[.]211[.]176
  4. To find the domains associated with the first IP, run in Brim:
    replace-with IP Addr | cut query
    Domain Query output
  5. Q9. For the first IP flagged as Not Suspicious Traffic, what malicious domains are associated with it? (defanged, alphabetical)
    Ans: safebanktest[.]top, tocsicambar[.]xyz, ulcertification[.]xyz
  6. Repeat the same query for the second IP and review reputations on VirusTotal.
  7. Q10. For the second IP, what domain appeared in network traffic (defanged)?
    Ans: 2partscow[.]top

I know this was a lengthy write-up — but Warzone2 is a long challenge. It’s also one of the best examples of connecting alerts, packets, and external intel. Huge thanks to ujohn for creating it.

Happy hacking!