Analysis
- max time kernel
95s - max time network
97s - platform
windows10-2004_x64 - resource
win10v2004-20240426-en - resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system - submitted
01/06/2024, 18:18
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe
Resource
win7-20240215-en
1 signatures
150 seconds
Behavioral task
behavioral2
Sample
79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe
Resource
win10v2004-20240426-en
5 signatures
150 seconds
General
- Target 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe
- Size 195KB
- Sample240601-wxmpsabe28
- SHA256 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49
- MD5 a0891b1792db9eb3512e51663411c0fc
- SHA1 435ed98664688f71e47533126dadcc397c13c1e6
- SHA512 5ad8ceb84d01e478f9ae6afaa1976724d7cf24f0b0b19ce95e775911923557da44003b212ebec0a6bdb7a498878f5ea5ec536ca6c1c58b67eb153b89197e6b3f
- SSDEEP 3072:35weZ6/MaaA1qtpD1rbQz+oYadrszUfU6CwtskQO8KWbjHbmO+yHto:6eQMrp5Qz+oYadaUfU6CUskH8hGO+Q
- MD5 SHA1 SHA512 SSDEEP
Score
5/10
Malware Config
Signatures
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3368 set thread context of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 - Program crash 1 IoCs
pid pid_target Process procid_target 3004 3800 WerFault.exe 92 - Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 3800 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 3800 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe Token: SeDebugPrivilege 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe - Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92 PID 3368 wrote to memory of 3800 3368 79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe 92
Processes
-
C:\Users\Admin\AppData\Local\Temp\79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe"C:\Users\Admin\AppData\Local\Temp\79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:3368 -
C:\Users\Admin\AppData\Local\Temp\79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe"C:\Users\Admin\AppData\Local\Temp\79a8fc24694a5d1b3a0e8a931f251774a485f1e0ddc913e8605d20ceebbc6e49.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
PID:3800 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3800 -s 1843⤵
- Program crash
PID:3004
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 412 -p 3800 -ip 38001⤵PID:4736