Analysis
-
max time kernel
304s -
max time network
331s -
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 22:58
Static task
static1
Behavioral task
behavioral1
Sample
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe
Resource
win10v2004-20221111-en
General
-
Target
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe
-
Size
251KB
-
MD5
43cf64094b7e0e7a7a0496bf6cdf6b67
-
SHA1
a5ec32a0750538f9b0fbed5f80f799244833f25f
-
SHA256
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81
-
SHA512
8314869e899d05f36352be2bf0ba585cc0226426fd4b16700baff380154fdf385bcf1a06f3d3235ab64c80d291fa44f00b611edb624ad31b70cf40980b5a40f1
-
SSDEEP
6144:qtBYZYw7uV3WUV7ArlAh0vlAResGlnGFo:qtBA7uVfy00GMuo
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exedescription pid process target process PID 4360 set thread context of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exepid process 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exedescription pid process target process PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe PID 4360 wrote to memory of 3640 4360 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe 837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe"C:\Users\Admin\AppData\Local\Temp\837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4360 -
C:\Users\Admin\AppData\Local\Temp\837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe"C:\Users\Admin\AppData\Local\Temp\837cd68e59a256d1ccc462ea72ad632b310e9c89bbd7a1b7a127f50a68200c81.exe"2⤵PID:3640