qakbot | 382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147

General

Target
382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Size 270KB
Sample201111-t9tpszz3a2
SHA256 382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147
MD5 0632349f4fe10b86f18d6f05cbc7661c
SHA1 600a17edcfb8e9fcb6e84ce6f84be4525f3fba6f
SHA512 1de96bf26f7e93a26ecb205d2e4abc09df8657ec3f7016ee9825c5f83bd08c48acbd22fca8d410cb5fab8845bbb87b7464631874de489ca35862300fa1ab46ad
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	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\Service	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CDROM&VEN_SANU&PROD_SANU_DVD-ROM\4&37CE57BA&0&010000	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\DeviceDesc	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\Service	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\DISK&VEN_&PROD_HEARTDISK\4&37CE57BA&0&000000	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe

Runs ping.exe 1 TTPs 1 IoCs

Remote System Discovery

pid	Process
3320	PING.EXE

Suspicious behavior: EnumeratesProcesses 6 IoCs

pid	Process
3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
3208	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
3208	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
3208	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe
3208	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe

Suspicious use of WriteProcessMemory 9 IoCs

description	pid	Process	procid_target
PID 3160 wrote to memory of 3208	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	78
PID 3160 wrote to memory of 3208	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	78
PID 3160 wrote to memory of 3208	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	78
PID 3160 wrote to memory of 204	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	79
PID 3160 wrote to memory of 204	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	79
PID 3160 wrote to memory of 204	3160	382c080a15bdba1dc3973ee299ab6d9fe170e453634fc65f2b6c62e8f524d147.exe	79
PID 204 wrote to memory of 3320	204	cmd.exe	81
PID 204 wrote to memory of 3320	204	cmd.exe	81
PID 204 wrote to memory of 3320	204	cmd.exe	81