Analysis
-
max time kernel
138s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
27/11/2022, 05:03
Static task
static1
Behavioral task
behavioral1
Sample
b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe
Resource
win10v2004-20221111-en
General
-
Target
b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe
-
Size
853KB
-
MD5
2250c281148fd38deb3f830c2718a487
-
SHA1
0ad177da0e51b0228439b27f6c2db87b6a968749
-
SHA256
b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4
-
SHA512
bc25a47738b295f691a43346ee688fdfe5bd5e2188725ae85be137c4a46133ca78adaeda090a123e70fa0cc58a9fbb1aa0dac78b050a5272a458cd3a2f4cb6c5
-
SSDEEP
24576:1Yq2/9nnr5cDNsOQfKJL9ki1arPvi/cjaBYfvk:mqaxyDC2JmSoPvikO8k
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 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.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 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3416 set thread context of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 2248 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83 PID 3416 wrote to memory of 2248 3416 b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe"C:\Users\Admin\AppData\Local\Temp\b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3416 -
C:\Users\Admin\AppData\Local\Temp\b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe"C:\Users\Admin\AppData\Local\Temp\b1bf1b839233d6bc833970d9e5ecc1df9f505a6b5e2aaee756e767339a2c4fe4.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:2248
-