Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution:
kali Desktop/forensic_images » sha1sum memory.mem c95e8cc8c946f95a109ea8e47a6800de10a27abd memory.mem
Question 2:
What profile is the most appropriate for this machine? (ex: Win10x86_14393)
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
The first step of volatility is always find the image info of the memory dump.
kali Desktop/forensic_images » volatility imageinfo -f memory.mem Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search... Suggested Profile(s) : Win7SP1x64, Win7SP0x64, Win2008R2SP0x64, Win2008R2SP1x64_24000, Win2008R2SP1x64_23418, Win2008R2SP1x64, Win7SP1x64_24000, Win7SP1x64_23418 AS Layer1 : WindowsAMD64PagedMemory (Kernel AS) AS Layer2 : FileAddressSpace (/root/Desktop/forensic_images/memory.mem) PAE type : No PAE DTB : 0x187000L KDBG : 0xf800029f80a0L Number of Processors : 2 Image Type (Service Pack) : 1 KPCR for CPU 0 : 0xfffff800029f9d00L KPCR for CPU 1 : 0xfffff880009ee000L KUSER_SHARED_DATA : 0xfffff78000000000L Image date and time : 2019-03-22 05:46:00 UTC+0000 Image localdate and time : 2019-03-22 01:46:00 -0400
Got the answer as Win7SP1x64
Question 3:
What was the process ID of notepad.exe?
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution:
We indicated the profile and use the pslist plugin to print all the running process
kali Desktop/forensic_images » volatility -f memory.mem --profile=Win7SP1x64 pslist | grep notepad Volatility Foundation Volatility Framework 2.6 0xfffffa80054f9060 notepad.exe 30321432160102019-03-2205:32:22 UTC+0000
and we got the answer pid as 3032
Question 4:
Name the child processes of wscript.exe.
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution:
pstree will indicate child process using idention and periods.
Let’s grep the top and bottom 3 line of process wscript.exe
Use grep to filter localhost ip address. The owner of system process svchost.exe seems bind to ip address 10.0.0.101:55736 which is the IP address when the RAM dump is created
Question 6
Based on the answer regarding to the infected PID, can you determine what the IP of the attacker was?
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution
Going back to question 4 we found out the malicious process is UWkpjFjDzM.exe
Still using the same netscan plugin,we find out there’s a connection to 10.0.0.106 port 4444 is one of the favorite port for malicious connection from hacker
kali Desktop/forensic_images » volatility -f memory.mem --profile=Win7SP1x64 netscan | grep UWkpjFjDzM.exe Volatility Foundation Volatility Framework 2.6 0x13e397190 TCPv4 10.0.0.101:4921710.0.0.106:4444 ESTABLISHED 3496 UWkpjFjDzM.exe
So the malicious hacker ip is 10.0.0.106
Question 7
What process nameis VCRUNTIME140.dll associated with?
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution
We have to use the dlllist plugin
kali Desktop/forensic_images » volatility -f memory.mem --profile=Win7SP1x64 dlllist > dlllist
We find the keyword dll VCRUNTIME140.dll
we found the malicious software OfficeClickToRun.exe
However beware that the process name should be OfficeClickToR
Question 8
What is the md5 hash value the potential malware on the system?
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution :
We are not able to identify the hash directly in memory dump.
We have to use one of the volatility function Procdump
At first I though the malicious process is OfficeClickToR
but it appears to be UWkpjFjDzM.exe we found earlier one
kali Desktop/forensic_images » volatility -f memory.mem--profile=Win7SP1x64 procdump -p3496--dump-dir . Volatility Foundation Volatility Framework 2.6 Process(V) ImageBase Name Result ------------------ ------------------ -------------------- ------ 0xfffffa8005a1d9e0 0x0000000000400000 UWkpjFjDzM.exe OK: executable.3496.exe
kali Desktop/forensic_images » md5sum executable.3496.exe 690ea20bc3bdfb328e23005d9a80c290 executable.3496.exe
and we got the md5 hash
Question 9
What is the LM hash of bobs account?
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution :
Use the hashdump plugin
kali Desktop/forensic_images » volatility -f memory.mem --profile=Win7SP1x64 hashdump Volatility Foundation Volatility Framework 2.6 Administrator:500:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0::: Guest:501:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0::: Bob:1000:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::
and we got bob’s hash
Question 10
What protections doesthe VAD node at0xfffffa800577ba10 have?
Flag Format-flag<xyz> Everything afterthe – is what you need to submit, your answer isthe xyx.
Solution
simple
kali Desktop/forensic_images » volatility -f memory.mem --profile=Win7SP1x64 vadinfo | grep -A 5 '0xfffffa800577ba10' 130 ↵ Volatility Foundation Volatility Framework 2.6 VAD node @ 0xfffffa800577ba10 Start 0x0000000000030000 End 0x0000000000033fff Tag Vad Flags: NoChange: 1, Protection: 1 Protection: PAGE_READONLY Vad Type: VadNone ControlArea @fffffa8005687a50 Segment fffff8a000c4f870 NumberOfSectionReferences: 1 NumberOfPfnReferences: 0
The answer is PAGE_READONLY
Question 11
There was a VBS script run on the machine. What is the name of the script? (submit without file extension)
Flag Format-flag<xyz> Everything after the – is what you need to submit, your answer is the xyx.
Solution:
After some research find out that, wscript.exe is tasked with executing the VBScript files.