Analysis
-
max time kernel
34s -
max time network
42s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 16:00
Static task
static1
Behavioral task
behavioral1
Sample
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe
Resource
win10v2004-20220812-en
General
-
Target
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe
-
Size
216KB
-
MD5
583a0747f62cf9e4eb0894dcd05237b0
-
SHA1
5a063bb8c3279283618a743197a190665581ef53
-
SHA256
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d
-
SHA512
7cc29cfe6bab31c01eda57883b387ed32b9ef1ce32b44dd7f0245d6e7be1943b9076467305b8aeecb6f5a3442f487cf6d397c7255af5b7075ff2a7a4195117f9
-
SSDEEP
3072:rh5/CoBruqHCjVuB+sKVUPTIwvo5otfdug8iqgnze9:rhgEruqijVE+sqU7Ikooigni
Malware Config
Signatures
-
Maps connected drives based on registry 3 TTPs 1 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 940 1368 WerFault.exe cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exepid process 1368 cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe -
Suspicious use of WriteProcessMemory 4 IoCs
Processes:
cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exedescription pid process target process PID 1368 wrote to memory of 940 1368 cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe WerFault.exe PID 1368 wrote to memory of 940 1368 cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe WerFault.exe PID 1368 wrote to memory of 940 1368 cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe WerFault.exe PID 1368 wrote to memory of 940 1368 cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe"C:\Users\Admin\AppData\Local\Temp\cb1edb26d0acdaf1c700aa9a4f3945f5fac36fc9293ac810e3f6ef8dfaa4d29d.exe"1⤵
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1368 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1368 -s 2362⤵
- Program crash
PID:940