Analysis
-
max time kernel
150s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
30-10-2022 04:20
Behavioral task
behavioral1
Sample
3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe
Resource
win10v2004-20220812-en
General
-
Target
3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe
-
Size
73KB
-
MD5
426cdf9391e91416a163974d451454fb
-
SHA1
c8cf38de581b1cba597b4b3a1451b5bbe1013490
-
SHA256
3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d
-
SHA512
ccf5a2feeb9cb270eccb420f4388bf5210d696fac023bb26ed57c8bd1f595fa6b3842e6aaddc1da9f0fd36b608abb2494c5005f299b799235c821439865eab56
-
SSDEEP
1536:P55u555555555pmgSeGDjtQhnwmmB0ybMqqU+2bbbAV2/S2mr3IdE8mne0Avu5rJ:7MSjOnrmBTMqqDL2/mr3IdE8we0Avu5h
Malware Config
Signatures
-
Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-2629973501-4017243118-3254762364-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe Set value (str) \REGISTRY\USER\S-1-5-21-2629973501-4017243118-3254762364-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\jlbcxvbgjfo = "C:\\Users\\Admin\\AppData\\Local\\Temp\\3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe" 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe -
Enumerates connected drives 3 TTPs 24 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\B: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\L: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\N: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\Y: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\E: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\F: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\G: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\J: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\K: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\M: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\O: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\P: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\T: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\X: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\I: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\Q: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\R: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\W: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\Z: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\A: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\H: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\S: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\U: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe File opened (read-only) \??\V: 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe -
Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe -
Suspicious use of WriteProcessMemory 42 IoCs
description pid Process procid_target PID 1712 wrote to memory of 4116 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 82 PID 1712 wrote to memory of 4116 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 82 PID 1712 wrote to memory of 4116 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 82 PID 1712 wrote to memory of 4976 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 84 PID 1712 wrote to memory of 4976 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 84 PID 1712 wrote to memory of 4976 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 84 PID 1712 wrote to memory of 4884 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 86 PID 1712 wrote to memory of 4884 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 86 PID 1712 wrote to memory of 4884 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 86 PID 1712 wrote to memory of 3388 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 89 PID 1712 wrote to memory of 3388 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 89 PID 1712 wrote to memory of 3388 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 89 PID 1712 wrote to memory of 904 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 91 PID 1712 wrote to memory of 904 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 91 PID 1712 wrote to memory of 904 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 91 PID 1712 wrote to memory of 3988 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 93 PID 1712 wrote to memory of 3988 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 93 PID 1712 wrote to memory of 3988 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 93 PID 1712 wrote to memory of 60 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 95 PID 1712 wrote to memory of 60 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 95 PID 1712 wrote to memory of 60 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 95 PID 1712 wrote to memory of 4684 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 97 PID 1712 wrote to memory of 4684 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 97 PID 1712 wrote to memory of 4684 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 97 PID 1712 wrote to memory of 3852 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 99 PID 1712 wrote to memory of 3852 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 99 PID 1712 wrote to memory of 3852 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 99 PID 1712 wrote to memory of 4128 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 101 PID 1712 wrote to memory of 4128 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 101 PID 1712 wrote to memory of 4128 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 101 PID 1712 wrote to memory of 2680 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 103 PID 1712 wrote to memory of 2680 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 103 PID 1712 wrote to memory of 2680 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 103 PID 1712 wrote to memory of 4304 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 105 PID 1712 wrote to memory of 4304 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 105 PID 1712 wrote to memory of 4304 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 105 PID 1712 wrote to memory of 624 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 107 PID 1712 wrote to memory of 624 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 107 PID 1712 wrote to memory of 624 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 107 PID 1712 wrote to memory of 1652 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 113 PID 1712 wrote to memory of 1652 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 113 PID 1712 wrote to memory of 1652 1712 3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe 113
Processes
-
C:\Users\Admin\AppData\Local\Temp\3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe"C:\Users\Admin\AppData\Local\Temp\3cf13441ba5e165c6b39e487518c7403e0a00abeb26f469c31f8eb16039d9b1d.exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1712 -
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:4116
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:4976
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:4884
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:3388
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:904
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:3988
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:60
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:4684
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:3852
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:4128
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:2680
-
-
C:\Windows\SysWOW64\nslookup.exenslookup gandcrab.bit dns1.soprodns.ru2⤵PID:4304
-
-
C:\Windows\SysWOW64\nslookup.exenslookup nomoreransom.bit dns1.soprodns.ru2⤵PID:624
-
-
C:\Windows\SysWOW64\nslookup.exenslookup emsisoft.bit dns1.soprodns.ru2⤵PID:1652
-