Analysis
-
max time kernel
148s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
28/11/2022, 07:58
Static task
static1
Behavioral task
behavioral1
Sample
f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe
Resource
win10v2004-20220812-en
General
-
Target
f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe
-
Size
959KB
-
MD5
8b6eca89acebe14a292462d3eaf65c9e
-
SHA1
54393bdfb32dd24869fb146c8eca9bc32dc65fa5
-
SHA256
f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc
-
SHA512
1e9e0d9a8c4e2523980a5da226deb8f722c8fd3d66ebb440c63a32e724c7014f7009671871f0841a1110b81bb4ab0f5440464daef02f03e18c1a6c94b66ae376
-
SSDEEP
24576:8kb9GXioEE6FY5fQ5emJYeXOxXzF6oHU9gG:8khGXiBE6FY1ps656tgG
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 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.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 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2740 set thread context of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 2988 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81 PID 2740 wrote to memory of 2988 2740 f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe"C:\Users\Admin\AppData\Local\Temp\f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2740 -
C:\Users\Admin\AppData\Local\Temp\f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe"C:\Users\Admin\AppData\Local\Temp\f051357e8d51b2b4fa402730614ba1a39344e8ee68326eb04106a0c0ead341cc.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:2988
-