qakbot | 815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8

General

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

Runs ping.exe 1 TTPs 1 IoCs

Remote System Discovery

pid	Process
4016	PING.EXE

Suspicious behavior: EnumeratesProcesses 6 IoCs

pid	Process
2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe
2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe
204	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe
204	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe
204	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe
204	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe

Suspicious use of WriteProcessMemory 9 IoCs

description	pid	Process	procid_target
PID 2268 wrote to memory of 204	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	78
PID 2268 wrote to memory of 204	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	78
PID 2268 wrote to memory of 204	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	78
PID 2268 wrote to memory of 3720	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	79
PID 2268 wrote to memory of 3720	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	79
PID 2268 wrote to memory of 3720	2268	815d25dcda0fccbe619c385ca65e759d8bee0395a337f24bba6b05a81ea6bdf8.exe	79
PID 3720 wrote to memory of 4016	3720	cmd.exe	81
PID 3720 wrote to memory of 4016	3720	cmd.exe	81
PID 3720 wrote to memory of 4016	3720	cmd.exe	81