Analysis
-
max time kernel
117s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240508-en -
resource tags
arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system -
submitted
06-06-2024 23:26
Static task
static1
Behavioral task
behavioral1
Sample
3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe
Resource
win7-20240508-en
windows7-x64
2 signatures
300 seconds
General
-
Target
3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe
-
Size
352KB
-
MD5
a74811b7e2d71612463144c69c0ca7e2
-
SHA1
900132a2213f70aed06e9982e47cfdcc8964b710
-
SHA256
3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f
-
SHA512
c4c5bef04693f000ae1f45d2a2d28f67609f36a635464d5025a50b939eaf9cc8d7766355990847f5679375f3d4b760e035dd92914f754ae64df6923da1cecebe
-
SSDEEP
6144:IsCv/QNuZNjDPp9XC2Fgd6dwiJLR8ATGb5gBJYgEltzK5d5Sw+tuhdZUui/EO:I/+uZNjDPNGeR85+YgEf25CtuhLi/EO
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 836 2932 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2932 wrote to memory of 836 2932 3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe 28 PID 2932 wrote to memory of 836 2932 3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe 28 PID 2932 wrote to memory of 836 2932 3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe 28 PID 2932 wrote to memory of 836 2932 3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe"C:\Users\Admin\AppData\Local\Temp\3d07b09f83f2fc5dcb7f2429cac9a37160181da77df5a429e37b98dd685f239f.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2932 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2932 -s 522⤵
- Program crash
PID:836
-