Analysis
-
max time kernel
153s -
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
27/11/2022, 20:01
Static task
static1
Behavioral task
behavioral1
Sample
e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe
Resource
win10v2004-20220812-en
General
-
Target
e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe
-
Size
1.2MB
-
MD5
e61aaa3199c6a383cc2edb46f7cf8358
-
SHA1
29d7dd7164c607299cdf283eb670333225c410a4
-
SHA256
e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e
-
SHA512
864076ca20107a0356002368c99930788a2dd9c8d254fd20c02700f929b50d9a372951899cc39abdb578676a8e8cbca03d4a25b0fde39f8e6554f631bfd46573
-
SSDEEP
24576:5QA0E/VE5yC3mBzZqGLqzwaYyuL2scvhSf64TWJqHRYAF2aSwk8bdbd5Iz9x:5QA0E/e59YoGWz1YEs6C6qHRYAFGwhbM
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 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.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 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4648 set thread context of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 4752 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79 PID 4648 wrote to memory of 4752 4648 e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe"C:\Users\Admin\AppData\Local\Temp\e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4648 -
C:\Users\Admin\AppData\Local\Temp\e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe"C:\Users\Admin\AppData\Local\Temp\e52fd274017e567400eb5ac35eedd9c4d3b50013871e4c0b9ec98c68d6eb0d3e.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:4752
-