Analysis
-
max time kernel
147s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 00:37
Static task
static1
Behavioral task
behavioral1
Sample
751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe
Resource
win10v2004-20221111-en
General
-
Target
751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe
-
Size
1.5MB
-
MD5
8f94010e4118c0985b6849177b91614e
-
SHA1
e06e737455dea4ce35d6039220e7debe1d11e2e1
-
SHA256
751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172
-
SHA512
1667e9ef1be184bbe574521551bc5e0ff07b64c05f7a3d7812fb62e4a731b883a470112fbab960c833f39a9f1b3d8b8f68537429dac44154942f752fa35a1b38
-
SSDEEP
24576:LPEzeDWtazKrcVWv+FjisSOZYjmOdXQ+ARZoQWnQUwMlds0VwI/9Mu:LIwwImsMqQA57oQWcGdsyn
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3928 set thread context of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 940 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 940 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 940 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 940 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 940 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82 PID 3928 wrote to memory of 940 3928 751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe"C:\Users\Admin\AppData\Local\Temp\751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3928 -
C:\Users\Admin\AppData\Local\Temp\751ab8dee888f2d1c2b7241ab5e3d18bdd669fb9c686d760b968f06af9a02172.exe
- Suspicious use of SetWindowsHookEx
PID:940
-