Analysis
- max time kernel
62s - max time network
17s - platform
windows7_x64 - resource
win7v20201028 - submitted
05/11/2020, 19:23
Static task
static1
Behavioral task
behavioral1
Sample
10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe
- Size 838KB
- Sample201105-ph7jkk8gca
- SHA256 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf
- MD5 c19155ad317de52254bbeca5a3ef183a
- SHA1 621f8bd284cea4647a3128188d5b2ab291d92b4f
- SHA512 02b482d91e22094d5fd19e0d2eddcfec36e82b0b04e3403fd2ab64f23c5a2cd8427aa53f423ddcc9a2e25f8935ef0ccf7dfac3843b9a49bc1beb7e1408c43bd3
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1716 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 1748 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 1748 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1824 wrote to memory of 1748 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 29 PID 1824 wrote to memory of 1748 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 29 PID 1824 wrote to memory of 1748 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 29 PID 1824 wrote to memory of 1748 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 29 PID 1824 wrote to memory of 340 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 30 PID 1824 wrote to memory of 340 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 30 PID 1824 wrote to memory of 340 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 30 PID 1824 wrote to memory of 340 1824 10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe 30 PID 340 wrote to memory of 1716 340 cmd.exe 32 PID 340 wrote to memory of 1716 340 cmd.exe 32 PID 340 wrote to memory of 1716 340 cmd.exe 32 PID 340 wrote to memory of 1716 340 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe"C:\Users\Admin\AppData\Local\Temp\10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1824 -
C:\Users\Admin\AppData\Local\Temp\10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exeC:\Users\Admin\AppData\Local\Temp\10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.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\10439cb0de42c37350bfef8e9741b90f53fdd2d48e1c9e82bf3dcd8334073abf.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:340 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1716
-
-