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