Analysis
-
max time kernel
146s -
max time network
127s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
02/06/2024, 05:33
Static task
static1
Behavioral task
behavioral1
Sample
674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe
Resource
win10v2004-20240508-en
General
-
Target
674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe
-
Size
9.2MB
-
MD5
d8f37867de99e4975fcbe9b8fc0d9ba4
-
SHA1
7bf53547f01ee2b9250407bb64f5b090d24bc190
-
SHA256
674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf
-
SHA512
51e52d5176a16eea070311df322644d96cce04f69dd05c64328a307d6423957eea4c33f2010f962e3a35300a607c09cffd91e79da2fb45083c25ea05162b94e9
-
SSDEEP
196608:JYe4Ffq7631UhiCM5DKQ8KKls8yXFHlKqol0m7JTjhO3ewo+m4XiGPh:JYtNaUCsvcyX1lcl0shO3y+ms
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 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe -
Enumerates connected drives 3 TTPs 23 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\M: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\P: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\Q: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\R: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\V: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\S: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\T: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\O: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\U: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\W: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\A: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\B: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\H: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\I: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\K: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\Y: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\Z: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\X: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\E: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\G: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\J: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\L: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe File opened (read-only) \??\N: 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\CentralProcessor\0 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe -
Enumerates system info in registry 2 TTPs 5 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\BIOS 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemManufacturer 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemVersion 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\BIOSVersion 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102 PID 3304 wrote to memory of 2616 3304 674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe 102
Processes
-
C:\Users\Admin\AppData\Local\Temp\674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe"C:\Users\Admin\AppData\Local\Temp\674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3304 -
C:\Users\Admin\AppData\Local\Temp\674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe"C:\Users\Admin\AppData\Local\Temp\674a338a72aeb79df6b94fc847444df22fff800cfaa5cefd64a3aa58cae6c7cf.exe"2⤵
- Checks BIOS information in registry
- Enumerates connected drives
- Checks processor information in registry
- Enumerates system info in registry
PID:2616
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --field-trial-handle=4200,i,10373433614523925616,13586256558317053467,262144 --variations-seed-version --mojo-platform-channel-handle=4036 /prefetch:81⤵PID:2260