Analysis
- max time kernel
73s - max time network
110s - platform
windows10_x64 - resource
win10v20201028 - submitted
10/11/2020, 11:22
Static task
static1
Behavioral task
behavioral1
Sample
4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe
Resource
win7v20201028
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe
Resource
win10v20201028
0 signatures
0 seconds
General
- Target 4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe
- Size 368KB
- Sample201110-vndzyaq1qa
- SHA256 4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004
- MD5 b75bef12ec67c6f29cf37d93bffca3c1
- SHA1 f4dd206ff298a0018c610705fabb360889a2e966
- SHA512 5cb19512ca433964322e62b8365db7ed6a18b29508390436ce7f270d78ac6dbf5fb6aa8e6ee3b70e1320d3a55ed14b1166d5d0bbd18b59cd57a883368ca19f8a
- MD5 SHA1 SHA512
Score
1/10
Malware Config
Signatures
- Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 580 wrote to memory of 3156 580 4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe 76 PID 580 wrote to memory of 3156 580 4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe 76 PID 580 wrote to memory of 3156 580 4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe 76
Processes
-
C:\Users\Admin\AppData\Local\Temp\4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe"C:\Users\Admin\AppData\Local\Temp\4cb0a9cadfa57ca281f8d3ea45085fcfe0682f2bfc6c184d192a05d983269004.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:580 -
C:\Windows\SysWOW64\cmd.exeC:\Windows\system32\cmd.exe /c cls2⤵PID:3156
-