03. There are two different C2 used by the attackers. What are their IP?
(Level 3: W10-PC5)
|
#8,
2 years, 3 months after release (2023-02-18 17:27:22)
|
75 |
02. Which script/command/thingy is used by the attackers to disable the antivirus?
(Level 3: W10-PC5)
|
#8,
2 years, 3 months after release (2023-02-18 17:10:06)
|
100 |
04. Attackers have used two Active Directory recon tools. When was the latest one first launched ?
(Level 3: W10-PC5)
|
#5,
2 years, 3 months after release (2023-02-18 17:07:34)
|
75 |
01. What "disguise" has used the executable used to run code on W10-PC3?
(Level 3: W10-PC5)
|
#8,
2 years, 3 months after release (2023-02-18 16:57:18)
|
50 |
09. The first question refers to a malicious code execution. What IP addresses did this attack likely came from?
(Level 2: W10-PC3)
|
#12,
2 years, 3 months after release (2023-02-18 16:48:15)
|
75 |
08. What EXACT authentication data from dom.adm account has been compromised ?
(Level 2: W10-PC3)
|
#6,
2 years, 3 months after release (2023-02-18 16:36:59)
|
200 |
07. How many different users did login on this computer on November 9 ?
(Level 2: W10-PC3)
|
#18,
2 years, 3 months after release (2023-02-18 16:06:25)
|
75 |
05. The attackers are quite sassy ... but sloppy too. Can you locate the password for one of this accounts?
(Level 2: W10-PC3)
|
#11,
2 years, 3 months after release (2023-02-18 14:08:18)
|
100 |
04. This machine is listening in a really odd port for an endpoint. Which one?
(Level 2: W10-PC3)
|
#20,
2 years, 3 months after release (2023-02-18 14:03:22)
|
50 |
06. Which privileged account has been used by the attackers ?
(Level 2: W10-PC3)
|
#6,
8 days, 16 hours after release (2023-02-18 14:01:59)
|
50 |
03. What is the external IP used by the attackers?
(Level 2: W10-PC3)
|
#16,
2 years, 3 months after release (2023-02-18 13:36:51)
|
50 |
02. This malicious execution is used to launch another known threat. At what UTC time?
(Level 2: W10-PC3)
|
#9,
2 years, 3 months after release (2023-02-18 13:30:51)
|
75 |
01. Which execution pinpoints the first lateral movement on this machine?
(Level 2: W10-PC3)
|
#10,
2 years, 3 months after release (2023-02-18 13:19:51)
|
50 |
09. What is the IP used by the attackers to connect to the domain controller ?
(Level 1: Domain controller)
|
#21,
2 years, 3 months after release (2023-02-18 12:34:01)
|
25 |
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)
|
#16,
2 years, 3 months after release (2023-02-18 12:31:07)
|
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)
|
#17,
2 years, 3 months after release (2023-02-18 12:29:27)
|
75 |
07. Which ransomware family are the attackers planning to deploy?
(Level 1: Domain controller)
|
#19,
2 years, 3 months after release (2023-02-18 12:16:39)
|
50 |
06. Which specific threat is launched by the AV detection?
(Level 1: Domain controller)
|
#6,
8 days, 15 hours after release (2023-02-18 12:06:13)
|
75 |
05. The antivirus detected a malicious file around this time. Which name does it have?
(Level 1: Domain controller)
|
#29,
2 years, 3 months after release (2023-02-18 11:51:37)
|
50 |
04. A foul-mouthed named script was executed a little after this user login. What is its name?
(Level 1: Domain controller)
|
#26,
2 years, 3 months after release (2023-02-18 11:38:07)
|
50 |
03. At what time can you see a logon type 10 user login on the domain controller?
(Level 1: Domain controller)
|
#31,
2 years, 3 months after release (2023-02-18 11:11:54)
|
50 |
02. At which time can the second malicious GPO be considered as loaded and ready to be applied?
(Level 1: Domain controller)
|
#22,
2 years, 3 months after release (2023-02-18 10:56:51)
|
100 |
01- What is the name of the first anomalous GPO?
(Level 1: Domain controller)
|
#13,
8 days, 14 hours after release (2023-02-18 10:47:09)
|
75 |