qakbot | ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703

General

Target
ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Size 270KB
Sample201113-zyc4vtr5d6
SHA256 ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703
MD5 68f2e7b629d512f47ebdccce14b12363
SHA1 1aa7866c9df0b02b0c3ad59b972c51dc7e38bccf
SHA512 4ea1573356ae658b4696eb00b8890158c06ce1fa2e3c328d1548646f973c2213d04f253f2e5bd04780d07332341c170cb08ae6587543b868b71ebec3a5a7b5ff
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 opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\DISK&VEN_&PROD_HEARTDISK\4&37CE57BA&0&000000	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\DeviceDesc	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\Service	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CDROM&VEN_SANU&PROD_SANU_DVD-ROM\4&37CE57BA&0&010000	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\DeviceDesc	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\Service	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe

Runs ping.exe 1 TTPs 1 IoCs

Remote System Discovery

pid	Process
2708	PING.EXE

Suspicious behavior: EnumeratesProcesses 6 IoCs

pid	Process
3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
3060	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
3060	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
3060	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe
3060	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe

Suspicious use of WriteProcessMemory 9 IoCs

description	pid	Process	procid_target
PID 3160 wrote to memory of 3060	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	78
PID 3160 wrote to memory of 3060	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	78
PID 3160 wrote to memory of 3060	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	78
PID 3160 wrote to memory of 2292	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	79
PID 3160 wrote to memory of 2292	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	79
PID 3160 wrote to memory of 2292	3160	ff667c99e95a9fa0f612d894cf416de55c8c32a0cbf16f4ea0167718cb591703.exe	79
PID 2292 wrote to memory of 2708	2292	cmd.exe	81
PID 2292 wrote to memory of 2708	2292	cmd.exe	81
PID 2292 wrote to memory of 2708	2292	cmd.exe	81