Analysis
-
max time kernel
149s -
max time network
158s -
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:19
Static task
static1
Behavioral task
behavioral1
Sample
da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe
Resource
win10v2004-20221111-en
General
-
Target
da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe
-
Size
1.0MB
-
MD5
22ed7e2f910b74266164947a08041c80
-
SHA1
3c2dc4a420e6904388010ed51eb5b8d56ad7eb4f
-
SHA256
da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4
-
SHA512
c2f6e549ac7690bc51a7a379b0856a8e2633125cb6c1c546f1045e707e83bcf78999e64c8cf8d411f7b3d60c14be6078c0dae4ffed7da2d2df2a203a42c14e3c
-
SSDEEP
24576:eZafNPaNMDJOpKROZRpulZBVOkeOLimGHCmO+:uaANaRGRpuHetmGimZ
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\SystemBiosVersion da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.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 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4256 set thread context of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 5016 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84 PID 4256 wrote to memory of 5016 4256 da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe"C:\Users\Admin\AppData\Local\Temp\da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4256 -
C:\Users\Admin\AppData\Local\Temp\da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe"C:\Users\Admin\AppData\Local\Temp\da17dfd4aeaded248e7d4587f384eeb67a69eb1a15f0842f536a55256ae947e4.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:5016
-