Analysis
-
max time kernel
91s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
04-12-2022 03:53
Static task
static1
Behavioral task
behavioral1
Sample
b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe
Resource
win10v2004-20220812-en
General
-
Target
b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe
-
Size
853KB
-
MD5
2aed1db7b68ab7b0b0154bd70b327eaa
-
SHA1
8b0c0ff2324a47be1fc29aad5a5fe3ce076fc083
-
SHA256
b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47
-
SHA512
ac9d822ee72d577673df8d6b8b4fb852f43d984bda55f7d6c284a6c55b55030f54a729150b2fcc0af6ddf3a8913bb7054ed26fdb95fca0b7ba0ff103b1957dec
-
SSDEEP
24576:1Yq2/9nnr5cDNsOQfKJL9ki1arPvi/cjaBYfv8:mqaxyDC2JmSoPvikO88
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\VideoBiosVersion b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.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 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1164 set thread context of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 2800 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79 PID 1164 wrote to memory of 2800 1164 b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe"C:\Users\Admin\AppData\Local\Temp\b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1164 -
C:\Users\Admin\AppData\Local\Temp\b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe"C:\Users\Admin\AppData\Local\Temp\b025a580468d6ed5ae95481e758614ddcc996526da78530b0b52c2a5a43c3b47.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:2800
-