|
10_extra. With all the evidence you have collected, and having to make a wild guess (attribution is hard, we know it) ... Which country did the attackers came from?
(Level 3: W10-PC5)
|
#8,
2 years, 3 months after release (2023-02-20 08:35:27)
|
150 |
|
06_extra. How many times did the attackers login on the DC from a user of this computer ?
(Level 2: W10-PC3)
|
#12,
2 years, 3 months after release (2023-02-20 08:33:07)
|
125 |
|
04. Attackers have used two Active Directory recon tools. When was the latest one first launched ?
(Level 3: W10-PC5)
|
#15,
2 years, 3 months after release (2023-02-18 18:38:32)
|
75 |
|
10. Which REAL domain/filename/underwear was used to spoof MINAF? Use the file attached
(Level 3: W10-PC5)
|
#4,
8 days, 19 hours after release (2023-02-18 18:28:36)
|
75 |
|
09. Here you have the malicious file from the previous question. What payload drops?
(Level 3: W10-PC5)
|
8 days, 20 hours after release (2023-02-18 18:27:06)
|
100 |
|
06. There is more than one malicious payloads running wild on this machine. When did the second one was deployed?
(Level 3: W10-PC5)
|
#6,
2 years, 3 months after release (2023-02-18 18:17:14)
|
75 |
|
08. This machine is plagued with evil. Name the file who drops the first malicious payload
(Level 3: W10-PC5)
|
#13,
2 years, 3 months after release (2023-02-18 18:15:30)
|
75 |
|
07. What is the first recon command made by the attackers ?
(Level 3: W10-PC5)
|
#15,
2 years, 3 months after release (2023-02-18 18:14:22)
|
75 |
|
08_extra. The attackers surely have left some persistence on this computer. Find it and give us the name/key/filename/whatever used.
(Level 2: W10-PC3)
|
#10,
2 years, 3 months after release (2023-02-18 18:07:49)
|
200 |
|
03. There are two different C2 used by the attackers. What are their IP?
(Level 3: W10-PC5)
|
#13,
2 years, 3 months after release (2023-02-18 18:00:30)
|
75 |
|
05_extra. What CVE have exploited the attackers to gain elevated privileges on the system?
(Level 3: W10-PC5)
|
#12,
2 years, 3 months after release (2023-02-18 17:57:14)
|
200 |
|
05. Which file has an exploit used by the attackers to elevate privileges?
(Level 3: W10-PC5)
|
#5,
10 days, 18 hours after release (2023-02-18 17:51:33)
|
100 |
|
02. Which script/command/thingy is used by the attackers to disable the antivirus?
(Level 3: W10-PC5)
|
#16,
2 years, 3 months after release (2023-02-18 17:25:01)
|
100 |
|
01. What "disguise" has used the executable used to run code on W10-PC3?
(Level 3: W10-PC5)
|
#17,
2 years, 3 months after release (2023-02-18 17:17:08)
|
50 |
|
09. The first question refers to a malicious code execution. What IP addresses did this attack likely came from?
(Level 2: W10-PC3)
|
#16,
2 years, 3 months after release (2023-02-18 16:49:22)
|
75 |
|
08. What EXACT authentication data from dom.adm account has been compromised ?
(Level 2: W10-PC3)
|
#4,
2 years, 3 months after release (2023-02-18 16:24:05)
|
200 |
|
07. How many different users did login on this computer on November 9 ?
(Level 2: W10-PC3)
|
#20,
2 years, 3 months after release (2023-02-18 16:07:59)
|
75 |
|
02. This malicious execution is used to launch another known threat. At what UTC time?
(Level 2: W10-PC3)
|
#18,
2 years, 3 months after release (2023-02-18 14:52:42)
|
75 |
|
05. The attackers are quite sassy ... but sloppy too. Can you locate the password for one of this accounts?
(Level 2: W10-PC3)
|
#9,
2 years, 3 months after release (2023-02-18 13:42:31)
|
100 |
|
06. Which privileged account has been used by the attackers ?
(Level 2: W10-PC3)
|
8 days, 16 hours after release (2023-02-18 13:35:43)
|
50 |
|
04. This machine is listening in a really odd port for an endpoint. Which one?
(Level 2: W10-PC3)
|
#11,
2 years, 3 months after release (2023-02-18 13:32:40)
|
50 |
|
03. What is the external IP used by the attackers?
(Level 2: W10-PC3)
|
#13,
2 years, 3 months after release (2023-02-18 13:30:07)
|
50 |
|
01. Which execution pinpoints the first lateral movement on this machine?
(Level 2: W10-PC3)
|
#11,
2 years, 3 months after release (2023-02-18 13:24:26)
|
50 |
|
04_Extra: How this file arrived to the domain controller?
(Level 1: Domain controller)
|
#13,
2 years, 3 months after release (2023-02-18 12:49:18)
|
100 |
|
08_Extra: There is a GPO in the disk that sets a value for the Group Policy Refresh. What is the time between cheks?
(Level 1: Domain controller)
|
#18,
2 years, 3 months after release (2023-02-18 12:47:25)
|
100 |
|
09_Extra. Which kind of authentication used the attacker to log into the system?
(Level 1: Domain controller)
|
#16,
2 years, 3 months after release (2023-02-18 12:47:19)
|
100 |
|
08. The GPO establish a fixed time for ransomware execution. Which time are the scheduled tasks of doom timed to start?
(Level 1: Domain controller)
|
#15,
2 years, 3 months after release (2023-02-18 12:22:40)
|
75 |
|
07. Which ransomware family are the attackers planning to deploy?
(Level 1: Domain controller)
|
#18,
2 years, 3 months after release (2023-02-18 12:16:05)
|
50 |
|
09. What is the IP used by the attackers to connect to the domain controller ?
(Level 1: Domain controller)
|
#17,
2 years, 3 months after release (2023-02-18 12:03:59)
|
25 |
|
06. Which specific threat is launched by the AV detection?
(Level 1: Domain controller)
|
8 days, 14 hours after release (2023-02-18 11:58:00)
|
75 |
|
05. The antivirus detected a malicious file around this time. Which name does it have?
(Level 1: Domain controller)
|
#30,
2 years, 3 months after release (2023-02-18 11:52:34)
|
50 |
|
04. A foul-mouthed named script was executed a little after this user login. What is its name?
(Level 1: Domain controller)
|
#29,
2 years, 3 months after release (2023-02-18 11:42:30)
|
50 |
|
03. At what time can you see a logon type 10 user login on the domain controller?
(Level 1: Domain controller)
|
#20,
2 years, 3 months after release (2023-02-18 10:47:53)
|
50 |
|
02. At which time can the second malicious GPO be considered as loaded and ready to be applied?
(Level 1: Domain controller)
|
#11,
2 years, 3 months after release (2023-02-18 10:42:37)
|
100 |
|
01- What is the name of the first anomalous GPO?
(Level 1: Domain controller)
|
8 days, 13 hours after release (2023-02-18 10:38:01)
|
75 |
