Analysis
- max time kernel
16s - max time network
11s - platform
windows7_x64 - resource
win7v20201028 - submitted
15/11/2020, 23:07
Static task
static1
Behavioral task
behavioral1
Sample
f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe
- Size 270KB
- Sample201115-pe8rrftls2
- SHA256 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40
- MD5 89d13114e9814c3e6e3f9e6bc8de0d90
- SHA1 1e6234de911b56c4752799438cb514d2144f429d
- SHA512 eb0abb6471c620935576392cf8d182b16a56b2723c16c3abd290396a01e3e6e0706c1ca369f8d0bfb47effd5f7ec68b2c664d4ae13801e4f0402922c6f546f0f
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1660 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 836 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 836 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1876 wrote to memory of 836 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 29 PID 1876 wrote to memory of 836 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 29 PID 1876 wrote to memory of 836 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 29 PID 1876 wrote to memory of 836 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 29 PID 1876 wrote to memory of 1872 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 30 PID 1876 wrote to memory of 1872 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 30 PID 1876 wrote to memory of 1872 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 30 PID 1876 wrote to memory of 1872 1876 f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe 30 PID 1872 wrote to memory of 1660 1872 cmd.exe 32 PID 1872 wrote to memory of 1660 1872 cmd.exe 32 PID 1872 wrote to memory of 1660 1872 cmd.exe 32 PID 1872 wrote to memory of 1660 1872 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe"C:\Users\Admin\AppData\Local\Temp\f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1876 -
C:\Users\Admin\AppData\Local\Temp\f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exeC:\Users\Admin\AppData\Local\Temp\f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:836
-
-
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\f675ad41eb380ca3fc65d93ab34fad573e5e235356bc6785a0c0aa5f70a71c40.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1872 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1660
-
-