https://tryhackme.com/room/investigatingwindows
Forensics
This is a challenge that is exactly what is says on the tin, there are a few challenges around investigating a windows machine that has been previously compromised.
Connect to the machine using RDP. The credentials the machine are as follows:
Username: Administrator Password: letmein123!
Please note that this machine does not respond to ping (ICMP) and may take a few minutes to boot up.
To check that simply type in systeminfo in command prompt to get windows version.

As you are the last person to login the username should be Administrator.
John's last login details can be grabbed using the following command from cmd.
net user john | findstr /B /C:"Last logon"
Details of each user account can be found out via the command
Administrator>net user
User accounts for \\EC2AMAZ-I8UHO76
-------------------------------------------------------------------------------
Administrator DefaultAccount Guest
Jenny John
The command completed successfully.
Administrator>net user jenny
Administrator>net user guestAgain net user jenny command can be used to check last login of jenny via command prompt.
Administrator>net user jenny
User name Jenny
Full Name Jenny
Comment
User's comment
Country/region code 000 (System Default)
Account active Yes
Account expires Never
Password last set 3/2/2019 4:52:25 PM
Password expires Never
Password changeable 3/2/2019 4:52:25 PM
Password required Yes
User may change password Yes
Workstations allowed All
Logon script
User profile
Home directory
Last logon NeverThis can be correlated to the event when a lot of processes gets suddenly started that can be viewed via event viewer.

From the event viewer, the date and time can be sorted from latest to oldest event to check when there has been an escalated logon to the system on 03/02/2019.

There was an intermittent command prompt popup execution that was holding a mimikatz session.
This can be checked by finding the hosts configuration file within the C drive.

This can be checked by looking at the www root path of IIS.

As seen in the hosts file, google was targeted for DNS poisoning.

None


