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