Analysis
-
max time kernel
91s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
30/10/2022, 18:06
Static task
static1
Behavioral task
behavioral1
Sample
b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe
Resource
win7-20220812-en
windows7-x64
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe
Resource
win10v2004-20220901-en
windows10-2004-x64
4 signatures
150 seconds
General
-
Target
b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe
-
Size
68KB
-
MD5
81f83e6c94e68d98303872bcebc71770
-
SHA1
9da82d2997e1e0717c8a371755b19dd2590c8994
-
SHA256
b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b
-
SHA512
7647ae66e5b08ae966b07d8e7ccd16dc9a36c9b9e3743a64ead4a9aebc70bc26ecae969f715be1c7700c7ff09fbcf06bb917702290b33acbeb58a89637992db5
-
SSDEEP
768:wi+PQbc0OwcEKoS9s5j9+sctjSwiHbItm6R64SnyghqeWMbno272sDsbufZ/nmaY:Qr9s99qIx6g4SnyaFDsW/TsNU6G
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4384 set thread context of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 4384 wrote to memory of 3368 4384 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 80 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37 PID 3368 wrote to memory of 2416 3368 b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe 37
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2416
-
C:\Users\Admin\AppData\Local\Temp\b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe"C:\Users\Admin\AppData\Local\Temp\b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4384 -
C:\Users\Admin\AppData\Local\Temp\b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exeC:\Users\Admin\AppData\Local\Temp\b9faaebed44b09d152309a8a5e610f8931f8d5d4303d771193ee7e912bce7c5b.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3368
-
-