Analysis
-
max time kernel
141s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
01-10-2023 01:48
Static task
static1
1 signatures
General
-
Target
fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe
-
Size
276KB
-
MD5
f8fb2c7be45a3055cb1747aed77fc2a8
-
SHA1
9dc6c3c95c770ec4db9373f87a139bb796e3b700
-
SHA256
fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0
-
SHA512
a0444de2c7fbfcc51e6dc775c0abf98929187fed958d4a8d54b50765017cbc41658db7061365535b66794530f44271e5410c9df95bb7bbd52985d76fcfb9e7ca
-
SSDEEP
6144:WhzoKajWpVP06mHXOwQfRFbTOTHPXOzr/WWdrj:WKKajWoXQfRBSTH2zaWdj
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4272 set thread context of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 2676 4272 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87 PID 4272 wrote to memory of 3872 4272 fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe"C:\Users\Admin\AppData\Local\Temp\fe1afec4f282e8f9e3376c09e6dff7472e90b5f38822a81b1ceb0ff0bb1d7ec0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4272 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3872
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4272 -s 1522⤵
- Program crash
PID:2676
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 452 -p 4272 -ip 42721⤵PID:316