Analysis
-
max time kernel
414s -
max time network
446s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
25-11-2022 12:24
Static task
static1
Behavioral task
behavioral1
Sample
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe
Resource
win10v2004-20221111-en
General
-
Target
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe
-
Size
935KB
-
MD5
0bb2baefd71ed453d88035b24565b84b
-
SHA1
b8a6e8d1690f8657128a27d5ab266b5c0feccbec
-
SHA256
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599
-
SHA512
372768fb7b965a1e955658de8c2cbeff61d1269ea94a07d3b3b29504f4d75f988544c3d9a8c98cd0ae8f367a125a666071788ee2fd5968ecb026632023e57f7d
-
SSDEEP
12288:I5Yr15f753d5QWIDz/Wz9NCyzHinLipNDJ5eoFb0OZ/WiGaks+HL63S27x4f:IyHv5Z+Wzv7AiBll0OBWi6si9GO
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/384-133-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/384-135-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/384-136-0x0000000000400000-0x00000000004F2000-memory.dmp upx behavioral2/memory/384-137-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:
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exedescription pid process target process PID 4156 set thread context of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exepid process 384 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 384 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 384 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exedescription pid process target process PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe PID 4156 wrote to memory of 384 4156 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe 666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe"C:\Users\Admin\AppData\Local\Temp\666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4156 -
C:\Users\Admin\AppData\Local\Temp\666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe"C:\Users\Admin\AppData\Local\Temp\666b4d8390108f4b9ee9b8dfc5322ed9da5f8620e03576d243cf59ff30cc3599.exe" Track="0001101000"2⤵
- Suspicious use of SetWindowsHookEx
PID:384
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/384-132-0x0000000000000000-mapping.dmp
-
memory/384-133-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/384-135-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/384-136-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB
-
memory/384-137-0x0000000000400000-0x00000000004F2000-memory.dmpFilesize
968KB