Analysis
-
max time kernel
144s -
max time network
164s -
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 08:03
Static task
static1
Behavioral task
behavioral1
Sample
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe
Resource
win10v2004-20221111-en
General
-
Target
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe
-
Size
1.1MB
-
MD5
791f9c3e7a21a4f2bb1f71d9abe54ed1
-
SHA1
e9a89ad33511e0c60a11d1a7548ed99f62bc1dba
-
SHA256
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f
-
SHA512
9b3118e2adc8251929f06545bcfaa7a26da68d3c1d41ef95b2e81980f4a76162992fa53ddb1e18fe22d8966dba570e3d9ece29efc2f91c46aa288deb01f0aad8
-
SSDEEP
12288:cxm03dDATu3TtKUhG3QQkrEcdvMqH1dznOotRldDfHbg5+MH/QTK7ufrncquNGsm:cgS73RKUsaVdzOotdDfStfsKafIgsm
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exedescription pid process target process PID 212 set thread context of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exepid process 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe 1452 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exedescription pid process target process PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe PID 212 wrote to memory of 1452 212 aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe"C:\Users\Admin\AppData\Local\Temp\aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:212 -
C:\Users\Admin\AppData\Local\Temp\aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe"C:\Users\Admin\AppData\Local\Temp\aa22f040bf4dbb9ebef447fb3fe4d1fcaa72a37eb3770abf3311ab101e8b2b6f.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:1452
-