Analysis
-
max time kernel
143s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
14-10-2023 18:05
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe
Resource
win10v2004-20230915-en
windows10-2004-x64
3 signatures
150 seconds
General
-
Target
4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe
-
Size
298KB
-
MD5
c005d591e8afb85f5470a58d2225789e
-
SHA1
a0ebdbc91fbc729eadd1965058eb930a9f5bafca
-
SHA256
4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055
-
SHA512
0b5cacdb654b35f201f801e8e7b373343676c1f65e7ae49e31bc18fad39e3250169e9452b939b247e259a32c53e6da825dbf0d8ecb6308a077a5ecb57b1b4bbd
-
SSDEEP
6144:gcJsICnU9Q85Djf0iWJOHgMd98px0zdx2Bw4QPBPoJ:gAsICnggYROcIBw4QPBPoJ
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3812 set thread context of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 3808 3812 WerFault.exe 86 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88 PID 3812 wrote to memory of 2892 3812 4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe"C:\Users\Admin\AppData\Local\Temp\4040f6c40883d3b5d3943ac50cdaf89b3ae0803cb85cf38eb7a05629c097b055.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3812 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2892
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3812 -s 1402⤵
- Program crash
PID:3808
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 448 -p 3812 -ip 38121⤵PID:1044