qakbot | 3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16

General

Target
3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Size 270KB
Sample201112-c2dcvb84xa
SHA256 3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16
MD5 542835d3af8ef3f9e2a8cb141f59ba36
SHA1 c4d36c8cef2f25c1824cfd38b1aec32e5ccbece4
SHA512 7f10052d7a239d9544c6d27f1d94800558f334e6f1e5346f09dfe0836265cd9cffb368247c95c4f09fc62780b5a51d08bd70d4f334b12989671c2abcebe4fe1b
MD5 SHA1 SHA512

Score

10^/10

Qakbot/Qbot
Qbot or Qakbot is a sophisticated worm with banking capabilities.
trojan banker stealer qakbot

Checks SCSI registry key(s) 3 TTPs 6 IoCs

SCSI information is often read in order to detect sandboxing environments.

Query Registry

Peripheral Device Discovery

System Information Discovery

description	ioc	Process
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\DeviceDesc	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\Service	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CDROM&VEN_SANU&PROD_SANU_DVD-ROM\4&37CE57BA&0&010000	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\DeviceDesc	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\Service	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\DISK&VEN_&PROD_HEARTDISK\4&37CE57BA&0&000000	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe

Runs ping.exe 1 TTPs 1 IoCs

Remote System Discovery

pid	Process
3108	PING.EXE

Suspicious behavior: EnumeratesProcesses 6 IoCs

pid	Process
2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
196	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
196	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
196	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe
196	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe

Suspicious use of WriteProcessMemory 9 IoCs

description	pid	Process	procid_target
PID 2432 wrote to memory of 196	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	78
PID 2432 wrote to memory of 196	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	78
PID 2432 wrote to memory of 196	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	78
PID 2432 wrote to memory of 2896	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	79
PID 2432 wrote to memory of 2896	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	79
PID 2432 wrote to memory of 2896	2432	3f16e6839fbdf02e63e892f77fc60418f49a3bf4f261385437d6a21ab305ec16.exe	79
PID 2896 wrote to memory of 3108	2896	cmd.exe	81
PID 2896 wrote to memory of 3108	2896	cmd.exe	81
PID 2896 wrote to memory of 3108	2896	cmd.exe	81