Analysis
-
max time kernel
150s -
max time network
162s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
27-11-2022 13:07
Static task
static1
Behavioral task
behavioral1
Sample
f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe
Resource
win10v2004-20220812-en
General
-
Target
f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe
-
Size
1.1MB
-
MD5
fd8630d7372a1a43cbc5d032af138c90
-
SHA1
c02a5e4e0eb3e2acd06813e215a589dfc880bf48
-
SHA256
f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539
-
SHA512
d05179163c8a784801a987eeb4bb56f4af025ec913c9e3aa6e09573b9fee97ad4b4a4c7e6ba6640a9edb5b30fa49c63ce6a3e7e648f1008bb3f0347f84c75b0e
-
SSDEEP
24576:iPG8EA2isNtNV++7K/czm0KqIAWUs3JIHphl3JOi:iPpsxVfG0SVlU+SlIi
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3912 set thread context of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 5052 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83 PID 3912 wrote to memory of 5052 3912 f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe"C:\Users\Admin\AppData\Local\Temp\f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3912 -
C:\Users\Admin\AppData\Local\Temp\f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe"C:\Users\Admin\AppData\Local\Temp\f41164b103c6c686792b4b6a737a3418ee2a3ad4a73b7d1472b133ba0ad91539.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:5052
-