Masterminds
Last updated
Was this helpful?
Last updated
Was this helpful?
Start Machine
Three machines in the Finance department at Pfeffer PLC were compromised. We suspect the initial source of the compromise happened through a phishing attempt and by an infected USB drive. The Incident Response team managed to pull the network traffic logs from the endpoints. Use Brim to investigate the network traffic for any indicators of an attack and determine who stands behind the attacks.
NOTE: DO NOT directly interact with any domains and IP addresses in this challenge.
Deploy the machine attached to this task; it will be visible in the split-screen view once it is ready.
If you don't see a virtual machine load then click the Show Split View button.
Answer the questions below
Read the above.
Completed
Start by loading the Infection1 packet capture in Brim to investigate the compromise event for the first machine. All the PCAPs can be found here: /home/ubuntu/Desktop/PCAPs
Note: For questions that require multiple answers, please separate the answers with a comma.
Answer the questions below
Provide the victim's IP address.
192.168.75.249
The victim attempted to make HTTP connections to two suspicious domains with the status '404 Not Found'. Provide the hosts/domains requested.
The victim made a successful HTTP connection to one of the domains and received the response_body_len of 1,309 (uncompressed content size of the data transferred from the server). Provide the domain and the destination IP address.
ww25.gocphongthe.com,199.59.242.153
7
/cgi-bin/JBbb8/
Provide the IP address of the malicious server and the executable that the victim downloaded from the server.
185.239.243.112, catzx.exe
Check what the Community has to say.
Emotet
Please, navigate to the Infection2 packet capture in Brim to investigate the compromise event for the second machine.
Note: For questions that require multiple answers, please separate the answers with a comma.
Answer the questions below
Provide the IP address of the victim machine.
192.168.75.146
Provide the IP address the victim made the POST connections to.
5.181.156.252
How many POST connections were made to the IP address in the previous question?
3
Provide the domain where the binary was downloaded from.
hypercustom.top
Provide the name of the binary including the full URI.
/jollion/apines.exe
Provide the IP address of the domain that hosts the binary.
45.95.203.28
There were 2 Suricata "A Network Trojan was detected" alerts. What were the source and destination IP addresses?
192.168.75.146,45.95.203.28
RedLine Stealer
Please, load the Infection3 packet capture in Brim to investigate the compromise event for the third machine.
Note: For questions that require multiple answers, please separate the answers with a comma.
Answer the questions below
Provide the IP address of the victim machine.
192.168.75.232
Provide three C2 domains from which the binaries were downloaded (starting from the earliest to the latest in the timestamp)
Start from the bottom of the output and work your way up or use '| sort ts'.
xfhoahegue.ru, afhoahegue.ru, efhoahegue.ru
Provide the IP addresses for all three domains in the previous question.
63.251.106.25, 199.21.76.77, 162.217.98.146
How many unique DNS queries were made to the domain associated from the first IP address from the previous answer?
2
How many binaries were downloaded from the above domain in total?
5
Provided the user-agent listed to download the binaries.
Try to type "user_agent" in the search bar.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0
Provide the amount of DNS connections made in total for this packet capture.
986
With some OSINT skills, provide the name of the worm using the first domain you have managed to collect from Question 2. (Please use quotation marks for Google searches, don't use .ru in your search, and DO NOT interact with the domain directly).
phorphiex
[[Lunizz CTF]]
Based on the information gathered from the second question, provide the name of the malware using .
Taking a look at .top domain in HTTP requests, provide the name of the stealer (Trojan that gathers information from a system) involved in this packet capture using .
