Analysis
- max time kernel
68s - max time network
66s - platform
windows7_x64 - resource
win7v20201028 - submitted
13/11/2020, 15:36
Static task
static1
Behavioral task
behavioral1
Sample
20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe
- Size 270KB
- Sample201113-4tz1vxysqx
- SHA256 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a
- MD5 13ed927e16eb8dbeba59f56e2f081392
- SHA1 1b969a09b8b38c73daeccffd73bcbe111f3ac407
- SHA512 064ca8dae81b0fcec73c8532a287097309007772b707b61a38a2d0c136f4619225c811bb131c3380d3ba9cf959518560ec78dac06e52bf7a7699833f54713940
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1364 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 1748 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 1748 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 744 wrote to memory of 1748 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 29 PID 744 wrote to memory of 1748 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 29 PID 744 wrote to memory of 1748 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 29 PID 744 wrote to memory of 1748 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 29 PID 744 wrote to memory of 1320 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 30 PID 744 wrote to memory of 1320 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 30 PID 744 wrote to memory of 1320 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 30 PID 744 wrote to memory of 1320 744 20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe 30 PID 1320 wrote to memory of 1364 1320 cmd.exe 32 PID 1320 wrote to memory of 1364 1320 cmd.exe 32 PID 1320 wrote to memory of 1364 1320 cmd.exe 32 PID 1320 wrote to memory of 1364 1320 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe"C:\Users\Admin\AppData\Local\Temp\20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:744 -
C:\Users\Admin\AppData\Local\Temp\20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exeC:\Users\Admin\AppData\Local\Temp\20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.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\20e4b614f684d9b2eff2c74348c5b22166bc33f3f89b290cc89a8f6b33ccde4a.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1320 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1364
-
-