Analysis
-
max time kernel
171s -
max time network
189s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
25-11-2022 12:40
Static task
static1
Behavioral task
behavioral1
Sample
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe
Resource
win10v2004-20220812-en
General
-
Target
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe
-
Size
935KB
-
MD5
cf69bb76aec3df4bb7b2f86cb4ea678e
-
SHA1
e9f94456cc35d1f9b9aed0ae4f54c7502d0b710b
-
SHA256
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c
-
SHA512
e003db972ed674b8bcd17e6ad815fdc818b5c84e6e788eb86350b909a7680a3b975f6e43ebecd8ce6370de5e83093f0206ef0202802f42458d879163ac3a1423
-
SSDEEP
12288:J5Yr15f753d5QWIDz/Wz9NCyzHinLipNDJ5eoFb0OZ/WiGaks+HL63S27x4F:JyHv5Z+Wzv7AiBll0OBWi6si9GU
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/4240-133-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/4240-135-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/4240-136-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/4240-137-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/4240-138-0x0000000000400000-0x00000000004F2000-memory.dmp upx -
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exedescription pid process target process PID 3596 set thread context of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exepid process 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 4240 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exedescription pid process target process PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe PID 3596 wrote to memory of 4240 3596 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe 5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe"C:\Users\Admin\AppData\Local\Temp\5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3596 -
C:\Users\Admin\AppData\Local\Temp\5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe"C:\Users\Admin\AppData\Local\Temp\5faa54d8b5f46409ccbbd36d455cc3bb978c83049bae3687fd962fe78ac4ad8c.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:4240
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/4240-132-0x0000000000000000-mapping.dmp
-
memory/4240-133-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/4240-135-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/4240-136-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/4240-137-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/4240-138-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB