09. The first question refers to a malicious code execution. What IP addresses did this attack likely came from?
(Level 2: W10-PC3)
|
#20,
2 years, 3 months after release (2023-02-18 18:13:41)
|
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)
|
#9,
2 years, 3 months after release (2023-02-18 18:03:51)
|
200 |
08. What EXACT authentication data from dom.adm account has been compromised ?
(Level 2: W10-PC3)
|
#13,
2 years, 3 months after release (2023-02-18 17:32:41)
|
200 |
07. How many different users did login on this computer on November 9 ?
(Level 2: W10-PC3)
|
#25,
2 years, 3 months after release (2023-02-18 16:28:40)
|
75 |
06_extra. How many times did the attackers login on the DC from a user of this computer ?
(Level 2: W10-PC3)
|
#7,
2 years, 3 months after release (2023-02-18 16:07:55)
|
125 |
06. Which privileged account has been used by the attackers ?
(Level 2: W10-PC3)
|
#22,
8 days, 18 hours after release (2023-02-18 16:04:35)
|
50 |
05. The attackers are quite sassy ... but sloppy too. Can you locate the password for one of this accounts?
(Level 2: W10-PC3)
|
#26,
2 years, 3 months after release (2023-02-18 15:59:03)
|
100 |
04. This machine is listening in a really odd port for an endpoint. Which one?
(Level 2: W10-PC3)
|
#28,
2 years, 3 months after release (2023-02-18 15:44:30)
|
50 |
03. What is the external IP used by the attackers?
(Level 2: W10-PC3)
|
#24,
2 years, 3 months after release (2023-02-18 13:52:26)
|
50 |
02. This malicious execution is used to launch another known threat. At what UTC time?
(Level 2: W10-PC3)
|
#14,
2 years, 3 months after release (2023-02-18 13:51:32)
|
75 |
01. Which execution pinpoints the first lateral movement on this machine?
(Level 2: W10-PC3)
|
#20,
2 years, 3 months after release (2023-02-18 13:36:29)
|
50 |
09_Extra. Which kind of authentication used the attacker to log into the system?
(Level 1: Domain controller)
|
#27,
2 years, 3 months after release (2023-02-18 13:19:32)
|
100 |
09. What is the IP used by the attackers to connect to the domain controller ?
(Level 1: Domain controller)
|
#33,
2 years, 3 months after release (2023-02-18 13:14:06)
|
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)
|
#20,
2 years, 3 months after release (2023-02-18 13:07:14)
|
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)
|
#24,
2 years, 3 months after release (2023-02-18 12:45:00)
|
75 |
07. Which ransomware family are the attackers planning to deploy?
(Level 1: Domain controller)
|
#24,
2 years, 3 months after release (2023-02-18 12:27:22)
|
50 |
06. Which specific threat is launched by the AV detection?
(Level 1: Domain controller)
|
#13,
8 days, 15 hours after release (2023-02-18 12:15:44)
|
75 |
05. The antivirus detected a malicious file around this time. Which name does it have?
(Level 1: Domain controller)
|
#32,
2 years, 3 months after release (2023-02-18 11:58:00)
|
50 |
04_Extra: How this file arrived to the domain controller?
(Level 1: Domain controller)
|
#10,
2 years, 3 months after release (2023-02-18 11:55:36)
|
100 |
04. A foul-mouthed named script was executed a little after this user login. What is its name?
(Level 1: Domain controller)
|
#28,
2 years, 3 months after release (2023-02-18 11:41:55)
|
50 |
03. At what time can you see a logon type 10 user login on the domain controller?
(Level 1: Domain controller)
|
#33,
2 years, 3 months after release (2023-02-18 11:21:49)
|
50 |
02. At which time can the second malicious GPO be considered as loaded and ready to be applied?
(Level 1: Domain controller)
|
#30,
2 years, 3 months after release (2023-02-18 11:06:56)
|
100 |
01- What is the name of the first anomalous GPO?
(Level 1: Domain controller)
|
#22,
8 days, 14 hours after release (2023-02-18 11:03:00)
|
75 |