Analysis
- max time kernel
89s - max time network
91s - platform
windows7_x64 - resource
win7v20201028 - submitted
13/11/2020, 15:12
Static task
static1
Behavioral task
behavioral1
Sample
e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe
- Size 270KB
- Sample201113-vpsdng47cx
- SHA256 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2
- MD5 b5b51b1066a864dfc72ec3f2449c9722
- SHA1 cec2ffd8b9188657934df2a28f6fb41392d01fed
- SHA512 76d4413b9cad1912b64adb1b4d66d7e71bf869e02e96f627f7ba5ee744fdb2984ba9c2785020d366568d7babb7b57c96c87a9071c199ede8cb6472378f0cf562
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1336 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 1096 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 1096 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 684 wrote to memory of 1096 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 29 PID 684 wrote to memory of 1096 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 29 PID 684 wrote to memory of 1096 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 29 PID 684 wrote to memory of 1096 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 29 PID 684 wrote to memory of 1396 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 30 PID 684 wrote to memory of 1396 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 30 PID 684 wrote to memory of 1396 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 30 PID 684 wrote to memory of 1396 684 e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe 30 PID 1396 wrote to memory of 1336 1396 cmd.exe 32 PID 1396 wrote to memory of 1336 1396 cmd.exe 32 PID 1396 wrote to memory of 1336 1396 cmd.exe 32 PID 1396 wrote to memory of 1336 1396 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe"C:\Users\Admin\AppData\Local\Temp\e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:684 -
C:\Users\Admin\AppData\Local\Temp\e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exeC:\Users\Admin\AppData\Local\Temp\e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1096
-
-
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\e417179cbf949296f1e13d3b87b2eb23398fa290f4e62e96ca7eb7ebe5ae80f2.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1396 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1336
-
-