Analysis
-
max time kernel
122s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20240903-en -
resource tags
arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system -
submitted
14-10-2024 19:24
Static task
static1
Behavioral task
behavioral1
Sample
Loader.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
Loader.exe
Resource
win10v2004-20241007-en
General
-
Target
Loader.exe
-
Size
16.3MB
-
MD5
d9729d3757c9edd6d37491d1add7bda8
-
SHA1
a61840c5ef149490b026faf2482fc6bd67c84f5d
-
SHA256
e75ae07c7b4a7e5e5eaaa0121bc9a46cd81297694b54ccf963c655b10ecf9c0b
-
SHA512
04f3878927d51ad56e82ec3d3a93554388ac176c7d2cc373f78e06559be8684c7dabcad2a6e4e3a6d378cc9f735bf9dcef6520580114cee838f5714bc3218d60
-
SSDEEP
393216:gOv5dqEU9B/ZTQLy2n912K8O7myy4QUd9laJ3r:gedszmb4K7myygXlaJ7
Malware Config
Signatures
-
Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 1 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\ACPI\DSDT\VBOX__ Loader.exe -
Creates new service(s) 2 TTPs
-
Drops file in Drivers directory 2 IoCs
description ioc Process File created C:\Windows\System32\drivers\winhb.sys Loader.exe File opened for modification C:\Windows\System32\drivers\winhb.sys Loader.exe -
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 Loader.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion Loader.exe -
description ioc Process Key value queried \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA Loader.exe -
Drops file in System32 directory 6 IoCs
description ioc Process File opened for modification C:\Windows\System32\config\RegBack\{69CD1F2D-DF68-4E23-9108-1B70783F2859} Loader.exe File opened for modification C:\Windows\System32\config\RegBack\{69CD1F2D-DF68-4E23-9108-1B70783F2869} Loader.exe File opened for modification C:\Windows\System32\IME\IMETC\{69CD1F2D-DF68-4E23-9108-1B70783F2879} Loader.exe File opened for modification C:\Windows\System32\config\RegBack\{69CD1F2D-DF68-4E23-9108-1B70783F2899} Loader.exe File opened for modification C:\Windows\System32\config\RegBack\{69CD1F2D-DF68-4E23-9108-1B70783F2444} Loader.exe File opened for modification C:\Windows\System32\config\RegBack\{69CD1F2D-DF68-4E23-9108-1B70783F2879} Loader.exe -
Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
pid Process 2668 Loader.exe -
Drops file in Windows directory 4 IoCs
description ioc Process File opened for modification C:\Windows\schemas\Provisioning\{69CD1F2D-DF68-4E23-9108-1B70783F2892} Loader.exe File opened for modification C:\Windows\schemas\Provisioning\{69CD1F2D-DF68-4E23-9108-1B70783F2859} Loader.exe File opened for modification C:\Windows\schemas\Provisioning\{69CD1F2D-DF68-4E23-9108-UPDATE} Loader.exe File opened for modification C:\Windows\schemas\Provisioning\{69CD1F2D-DF68-4E23-9108-1B70783F2893} Loader.exe -
Launches sc.exe 4 IoCs
Sc.exe is a Windows utlilty to control services on the system.
pid Process 2692 sc.exe 1628 sc.exe 2928 sc.exe 2648 sc.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious behavior: EnumeratesProcesses 16 IoCs
pid Process 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe 2668 Loader.exe -
Suspicious use of WriteProcessMemory 39 IoCs
description pid Process procid_target PID 2668 wrote to memory of 2864 2668 Loader.exe 32 PID 2668 wrote to memory of 2864 2668 Loader.exe 32 PID 2668 wrote to memory of 2864 2668 Loader.exe 32 PID 2668 wrote to memory of 2932 2668 Loader.exe 33 PID 2668 wrote to memory of 2932 2668 Loader.exe 33 PID 2668 wrote to memory of 2932 2668 Loader.exe 33 PID 2668 wrote to memory of 2836 2668 Loader.exe 34 PID 2668 wrote to memory of 2836 2668 Loader.exe 34 PID 2668 wrote to memory of 2836 2668 Loader.exe 34 PID 2836 wrote to memory of 2708 2836 cmd.exe 37 PID 2836 wrote to memory of 2708 2836 cmd.exe 37 PID 2836 wrote to memory of 2708 2836 cmd.exe 37 PID 2836 wrote to memory of 2584 2836 cmd.exe 38 PID 2836 wrote to memory of 2584 2836 cmd.exe 38 PID 2836 wrote to memory of 2584 2836 cmd.exe 38 PID 2836 wrote to memory of 1600 2836 cmd.exe 39 PID 2836 wrote to memory of 1600 2836 cmd.exe 39 PID 2836 wrote to memory of 1600 2836 cmd.exe 39 PID 2864 wrote to memory of 2692 2864 cmd.exe 40 PID 2864 wrote to memory of 2692 2864 cmd.exe 40 PID 2864 wrote to memory of 2692 2864 cmd.exe 40 PID 2932 wrote to memory of 1628 2932 cmd.exe 41 PID 2932 wrote to memory of 1628 2932 cmd.exe 41 PID 2932 wrote to memory of 1628 2932 cmd.exe 41 PID 2668 wrote to memory of 2712 2668 Loader.exe 42 PID 2668 wrote to memory of 2712 2668 Loader.exe 42 PID 2668 wrote to memory of 2712 2668 Loader.exe 42 PID 2712 wrote to memory of 2928 2712 cmd.exe 44 PID 2712 wrote to memory of 2928 2712 cmd.exe 44 PID 2712 wrote to memory of 2928 2712 cmd.exe 44 PID 2668 wrote to memory of 2588 2668 Loader.exe 45 PID 2668 wrote to memory of 2588 2668 Loader.exe 45 PID 2668 wrote to memory of 2588 2668 Loader.exe 45 PID 2588 wrote to memory of 2648 2588 cmd.exe 47 PID 2588 wrote to memory of 2648 2588 cmd.exe 47 PID 2588 wrote to memory of 2648 2588 cmd.exe 47 PID 2668 wrote to memory of 1444 2668 Loader.exe 48 PID 2668 wrote to memory of 1444 2668 Loader.exe 48 PID 2668 wrote to memory of 1444 2668 Loader.exe 48
Processes
-
C:\Users\Admin\AppData\Local\Temp\Loader.exe"C:\Users\Admin\AppData\Local\Temp\Loader.exe"1⤵
- Identifies VirtualBox via ACPI registry values (likely anti-VM)
- Drops file in Drivers directory
- Checks BIOS information in registry
- Checks whether UAC is enabled
- Drops file in System32 directory
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Drops file in Windows directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Windows\System32\cmd.exe"C:\Windows\System32\cmd.exe" /C sc create windowsproc type=kernel binpath=C:\Windows\System32\drivers\winhb.sys2⤵
- Suspicious use of WriteProcessMemory
PID:2864 -
C:\Windows\system32\sc.exesc create windowsproc type=kernel binpath=C:\Windows\System32\drivers\winhb.sys3⤵
- Launches sc.exe
PID:2692
-
-
-
C:\Windows\System32\cmd.exe"C:\Windows\System32\cmd.exe" /C sc start windowsproc2⤵
- Suspicious use of WriteProcessMemory
PID:2932 -
C:\Windows\system32\sc.exesc start windowsproc3⤵
- Launches sc.exe
PID:1628
-
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c certutil -hashfile "C:\Users\Admin\AppData\Local\Temp\Loader.exe" MD5 | find /i /v "md5" | find /i /v "certutil"2⤵
- Suspicious use of WriteProcessMemory
PID:2836 -
C:\Windows\system32\certutil.execertutil -hashfile "C:\Users\Admin\AppData\Local\Temp\Loader.exe" MD53⤵PID:2708
-
-
C:\Windows\system32\find.exefind /i /v "md5"3⤵PID:2584
-
-
C:\Windows\system32\find.exefind /i /v "certutil"3⤵PID:1600
-
-
-
C:\Windows\System32\cmd.exe"C:\Windows\System32\cmd.exe" /C sc create windowsproc type=kernel binpath=C:\Windows\System32\drivers\winhb.sys2⤵
- Suspicious use of WriteProcessMemory
PID:2712 -
C:\Windows\system32\sc.exesc create windowsproc type=kernel binpath=C:\Windows\System32\drivers\winhb.sys3⤵
- Launches sc.exe
PID:2928
-
-
-
C:\Windows\System32\cmd.exe"C:\Windows\System32\cmd.exe" /C sc start windowsproc2⤵
- Suspicious use of WriteProcessMemory
PID:2588 -
C:\Windows\system32\sc.exesc start windowsproc3⤵
- Launches sc.exe
PID:2648
-
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c cls2⤵PID:1444
-