|
04_Extra: How this file arrived to the domain controller?
(Level 1: Domain controller)
|
#14,
2 years, 3 months after release (2023-02-18 18:59:42)
|
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)
|
#8,
2 years, 3 months after release (2023-02-18 18:29:41)
|
75 |
|
07. What is the first recon command made by the attackers ?
(Level 3: W10-PC5)
|
#14,
2 years, 3 months after release (2023-02-18 18:11:05)
|
75 |
|
05_extra. What CVE have exploited the attackers to gain elevated privileges on the system?
(Level 3: W10-PC5)
|
#15,
2 years, 3 months after release (2023-02-18 18:06:34)
|
200 |
|
05. Which file has an exploit used by the attackers to elevate privileges?
(Level 3: W10-PC5)
|
#10,
10 days, 19 hours after release (2023-02-18 18:02:11)
|
100 |
|
04. Attackers have used two Active Directory recon tools. When was the latest one first launched ?
(Level 3: W10-PC5)
|
#11,
2 years, 3 months after release (2023-02-18 17:38:54)
|
75 |
|
03. There are two different C2 used by the attackers. What are their IP?
(Level 3: W10-PC5)
|
#9,
2 years, 3 months after release (2023-02-18 17:27:40)
|
75 |
|
02. Which script/command/thingy is used by the attackers to disable the antivirus?
(Level 3: W10-PC5)
|
#9,
2 years, 3 months after release (2023-02-18 17:19:20)
|
100 |
|
01. What "disguise" has used the executable used to run code on W10-PC3?
(Level 3: W10-PC5)
|
#13,
2 years, 3 months after release (2023-02-18 17:07:13)
|
50 |
|
06. Which privileged account has been used by the attackers ?
(Level 2: W10-PC3)
|
#23,
8 days, 18 hours after release (2023-02-18 16:20:36)
|
50 |
|
05. The attackers are quite sassy ... but sloppy too. Can you locate the password for one of this accounts?
(Level 2: W10-PC3)
|
#27,
2 years, 3 months after release (2023-02-18 16:20:09)
|
100 |
|
04. This machine is listening in a really odd port for an endpoint. Which one?
(Level 2: W10-PC3)
|
#32,
2 years, 3 months after release (2023-02-18 16:02:47)
|
50 |
|
03. What is the external IP used by the attackers?
(Level 2: W10-PC3)
|
#30,
2 years, 3 months after release (2023-02-18 15:37:49)
|
50 |
|
01. Which execution pinpoints the first lateral movement on this machine?
(Level 2: W10-PC3)
|
#22,
2 years, 3 months after release (2023-02-18 13:55:24)
|
50 |
|
07. Which ransomware family are the attackers planning to deploy?
(Level 1: Domain controller)
|
#32,
2 years, 3 months after release (2023-02-18 13:20:53)
|
50 |
|
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)
|
#29,
2 years, 3 months after release (2023-02-18 13:14:35)
|
75 |
|
09_Extra. Which kind of authentication used the attacker to log into the system?
(Level 1: Domain controller)
|
#21,
2 years, 3 months after release (2023-02-18 12:53:16)
|
100 |
|
09. What is the IP used by the attackers to connect to the domain controller ?
(Level 1: Domain controller)
|
#23,
2 years, 3 months after release (2023-02-18 12:46:30)
|
25 |
|
05. The antivirus detected a malicious file around this time. Which name does it have?
(Level 1: Domain controller)
|
#35,
2 years, 3 months after release (2023-02-18 12:12:43)
|
50 |
|
04. A foul-mouthed named script was executed a little after this user login. What is its name?
(Level 1: Domain controller)
|
#32,
2 years, 3 months after release (2023-02-18 12:06:15)
|
50 |
|
03. At what time can you see a logon type 10 user login on the domain controller?
(Level 1: Domain controller)
|
#23,
2 years, 3 months after release (2023-02-18 11:03:36)
|
50 |
|
02. At which time can the second malicious GPO be considered as loaded and ready to be applied?
(Level 1: Domain controller)
|
#17,
2 years, 3 months after release (2023-02-18 10:53:10)
|
100 |
|
01- What is the name of the first anomalous GPO?
(Level 1: Domain controller)
|
#15,
8 days, 14 hours after release (2023-02-18 10:50:38)
|
75 |
