Analysis
- max time kernel
16s - max time network
9s - platform
windows7_x64 - resource
win7v20201028 - submitted
12/11/2020, 14:12
Static task
static1
Behavioral task
behavioral1
Sample
ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe
- Size 270KB
- Sample201112-zz7te2akss
- SHA256 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f
- MD5 1b5d25bc4fc833423b76f037f1719103
- SHA1 ea95e75117cd00a6b49cf015e567df7b4ec551bc
- SHA512 3b7920722c427dfa2509d775cc45f9829577207e02858b4ed0cecf895a469f64dca837b7c37ddd65b6700c9e133bb18250ddb05eaf1498d48b415ca7993bf339
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1420 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 1748 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 1748 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1668 wrote to memory of 1748 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 29 PID 1668 wrote to memory of 1748 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 29 PID 1668 wrote to memory of 1748 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 29 PID 1668 wrote to memory of 1748 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 29 PID 1668 wrote to memory of 1700 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 30 PID 1668 wrote to memory of 1700 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 30 PID 1668 wrote to memory of 1700 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 30 PID 1668 wrote to memory of 1700 1668 ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe 30 PID 1700 wrote to memory of 1420 1700 cmd.exe 32 PID 1700 wrote to memory of 1420 1700 cmd.exe 32 PID 1700 wrote to memory of 1420 1700 cmd.exe 32 PID 1700 wrote to memory of 1420 1700 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe"C:\Users\Admin\AppData\Local\Temp\ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1668 -
C:\Users\Admin\AppData\Local\Temp\ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exeC:\Users\Admin\AppData\Local\Temp\ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1748
-
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c ping.exe -n 6 127.0.0.1 & type "C:\Windows\System32\calc.exe" > "C:\Users\Admin\AppData\Local\Temp\ea930eca5a6f379663768ced609a217bfab8d0c5633e012855f16d848022232f.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1700 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1420
-
-