Analysis
-
max time kernel
190s -
max time network
191s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
06/12/2022, 10:17
Behavioral task
behavioral1
Sample
e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe
Resource
win7-20220812-en
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe
Resource
win10v2004-20220812-en
5 signatures
150 seconds
General
-
Target
e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe
-
Size
132KB
-
MD5
73c0dad3c6b0af88ab3c815141563792
-
SHA1
c05a9c91fc4e12f89f807f5bcd19ef0ff7ddfc6d
-
SHA256
e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba
-
SHA512
119fb02915496a7b19b0357ea8f1fbf01400e2d49d289acbecf99a5b050e3f97a1f2e9f1aaedac7082107f852551a1708bbd25351963d70f652586d476208a35
-
SSDEEP
768:BIwV+V+VcIVcVBHCXye6H7fhm6mPpOlNpvANDF5fixnAdc5o0G5saW0GgxNbPr:/V+V+VVV2cXmbfAzwiDWSBW0z
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4768-132-0x0000000000400000-0x0000000000421000-memory.dmp aspack_v212_v242 behavioral2/memory/4768-138-0x0000000000400000-0x0000000000421000-memory.dmp aspack_v212_v242 -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4768 set thread context of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 -
Program crash 1 IoCs
pid pid_target Process procid_target 4432 4748 WerFault.exe 79 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79 PID 4768 wrote to memory of 4748 4768 e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe"C:\Users\Admin\AppData\Local\Temp\e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4768 -
C:\Users\Admin\AppData\Local\Temp\e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exeC:\Users\Admin\AppData\Local\Temp\e19428082cb09c0af6a2a564f634a338cbe0c8b896f2053ec70d8d25294bbfba.exe2⤵PID:4748
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4748 -s 4603⤵
- Program crash
PID:4432
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 4748 -ip 47481⤵PID:4412