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