Analysis
-
max time kernel
179s -
max time network
183s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
06/11/2022, 15:46
Static task
static1
Behavioral task
behavioral1
Sample
8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe
Resource
win10v2004-20220812-en
General
-
Target
8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe
-
Size
52KB
-
MD5
03efc3aa4e6f7fabe075ce2772fecf98
-
SHA1
2a33da7c27d6256fb1259242f076df60aab366d2
-
SHA256
8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0
-
SHA512
fb3e859447498824617d928be64d2faaa331cc7e3a0acf9d33764f84bb1bf0321f4f978f1df62fc4c0bf7f4e6f967af502808f42b83b12fff20edfc0b50b77e8
-
SSDEEP
768:v+RQSYAF9A/YBCvmiB/vcUY/CSXQ6Nhirqbbm0t03:v+wAYgBwpGCV6OyF8
Malware Config
Signatures
-
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 value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1380 set thread context of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 5004 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 5004 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77 PID 1380 wrote to memory of 5004 1380 8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe 77
Processes
-
C:\Users\Admin\AppData\Local\Temp\8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe"C:\Users\Admin\AppData\Local\Temp\8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1380 -
C:\Users\Admin\AppData\Local\Temp\8e94939e0cb64ed4903f74789210127192f572f575d3e4724cddb6f1a7ee9be0.exea|2⤵
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
PID:5004
-