Analysis
-
max time kernel
142s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
21/11/2022, 20:36
Static task
static1
Behavioral task
behavioral1
Sample
2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe
Resource
win10v2004-20221111-en
General
-
Target
2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe
-
Size
1.0MB
-
MD5
a25d0dd78aed10ed7aac1e229807cf27
-
SHA1
89b15510dfa6c85de762c242cadbfbe2b7618c69
-
SHA256
2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24
-
SHA512
bb80c732bd88921236a9615718638731ec6d19034c9f45dc2aa3babc13d6114e9f1b8886cc1a4da41dcfede81035328dc3da6d9ca6cb524933302e24692ab1c1
-
SSDEEP
24576:/J0FPl0XoDnqgEdhlaCT3xXGHRXjEuuMjM4jm6dVriAUli8WXHXlpo:/WFPaXGalaCTt8XjwoGji8L
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4296 set thread context of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 2140 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 2140 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 2140 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 2140 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 2140 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84 PID 4296 wrote to memory of 2140 4296 2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe"C:\Users\Admin\AppData\Local\Temp\2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4296 -
C:\Users\Admin\AppData\Local\Temp\2a891a828bdaf896eba0f773340dcdf767b7d49722de21f8b5c4ad77c48a6b24.exe
- Suspicious use of SetWindowsHookEx
PID:2140
-