qakbot | 205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8

General

Target
205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Size 257KB
Sample201113-m3ka8a59vj
SHA256 205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8
MD5 6c92a445d74fd978f5a6a6b49d67f908
SHA1 f397e7e137369cf78b2ebd9b9556949cc9534da9
SHA512 9101fc9e717a1c7f624c865d661d5b21c756506ca9d67630f0fa8ce4a7f68a11bcecedfc902b3c340964ae0dfe853e3ac406ffcad92a5589a5c6da7cc6c4e3b1
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\CDROM&VEN_SANU&PROD_SANU_DVD-ROM\4&37CE57BA&0&010000	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\DeviceDesc	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\CdRom&Ven_Sanu&Prod_Sanu_DVD-ROM\4&37ce57ba&0&010000\Service	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Key opened	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\DISK&VEN_&PROD_HEARTDISK\4&37CE57BA&0&000000	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\DeviceDesc	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
Key value queried	\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_&Prod_HeartDisk\4&37ce57ba&0&000000\Service	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe

Runs ping.exe 1 TTPs 1 IoCs

Remote System Discovery

pid	Process
64	PING.EXE

Suspicious behavior: EnumeratesProcesses 6 IoCs

pid	Process
3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
3184	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
3184	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
3184	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe
3184	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe

Suspicious use of WriteProcessMemory 9 IoCs

description	pid	Process	procid_target
PID 3980 wrote to memory of 3184	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	79
PID 3980 wrote to memory of 3184	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	79
PID 3980 wrote to memory of 3184	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	79
PID 3980 wrote to memory of 2500	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	80
PID 3980 wrote to memory of 2500	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	80
PID 3980 wrote to memory of 2500	3980	205bce31e90caea0f3ef82a0bfb30f276f69fcbbcea5c2ff5d857a573e88eff8.exe	80
PID 2500 wrote to memory of 64	2500	cmd.exe	82
PID 2500 wrote to memory of 64	2500	cmd.exe	82
PID 2500 wrote to memory of 64	2500	cmd.exe	82