Analysis
- max time kernel
40s - max time network
44s - platform
windows7_x64 - resource
win7-20220414-en - submitted
20/05/2022, 07:47
Static task
static1
Behavioral task
behavioral1
Sample
1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe
Resource
win7-20220414-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe
Resource
win10v2004-20220414-en
0 signatures
0 seconds
General
- Target 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe
- Size 573KB
- Sample220520-jmnswaghc2
- SHA256 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293
- MD5 c9d1ee54a4f73fe963fc375449c87c1e
- SHA1 4f3a048ce14561efdab00085fa27b3ecb405f9a3
- SHA512 a62603c41d37db472e650c0e50fe5469cc1674737cdca74b1d32a9ca0f6ab8c30b80f9d19e4be71a4d5942f5d4220a29d79c6e7f5b79aa0718a24e0eafb316c9
- MD5 SHA1 SHA512
Score
3/10
Malware Config
Signatures
- Program crash 1 IoCs
pid pid_target Process procid_target 1212 1732 WerFault.exe 27 - Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 1732 wrote to memory of 1212 1732 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe 28 PID 1732 wrote to memory of 1212 1732 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe 28 PID 1732 wrote to memory of 1212 1732 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe 28 PID 1732 wrote to memory of 1212 1732 1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe"C:\Users\Admin\AppData\Local\Temp\1fa0ac0a019a301a4e8e20ad7e27b89d86540318d84ed530f1ee8a695b9fe293.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:1732 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1732 -s 6402⤵
- Program crash
PID:1212
-