Skip to main content
Mallory
MalwareRansomwareUsed by 18 actorsExploits 6 CVEs

QakBot

Also known asPinkslipbotQBotQuackBot

QakBot, also known as QBot, QuakBot, and Pinkslipbot, is a modular banking trojan and information stealer first seen in 2007 that has evolved into a malware distributor and ransomware precursor. It is associated with financially motivated cybercriminal activity and has been linked in reporting to Russian operators. QakBot targets Microsoft Windows systems and has been used at scale, including infrastructure associated with the Avalanche fast-flux botnet ecosystem.

Observed initial access commonly involves phishing or hijacked email threads delivering malicious HTML attachments, password-protected ZIP archives, malicious URLs, and later ISO, IMG, or VHD disk images containing malicious LNK files. Reporting also notes a shift in some 2022 campaigns to malicious MSI packages delivered via phishing emails with password-protected ZIP attachments. QakBot execution chains abuse LOLBins including cmd.exe, wscript.exe, curl.exe, regsvr32.exe, and rundll32.exe; observed chains include LNK > CMD/CURL > PING > Regsvr32, LNK > CALC > Regsvr32 via DLL hijacking, and related regsvr32-based loader activity. QakBot has also used signed loaders to evade detection.

On execution, QakBot performs anti-analysis and defense evasion, including checking for antivirus products such as Kaspersky, Bitdefender, Sophos, Trend Micro, Windows Defender, and Avast; checking for C:\INTERNAL__empty to detect the Windows Defender sandbox; and modifying the Registry to add its binaries to the Windows Defender exclusion list. It performs process hollowing into legitimate Windows processes selected from a hardcoded list, with observed targets including wermgr.exe, explorer.exe, mobsync.exe, msra.exe, OneDriveSetup.exe, iexplore.exe, and dxdiag.exe. It enumerates processes using CreateToolhelp32Snapshot, Process32First, and Process32Next, and uses CreateProcessW, WriteProcessMemory, and NtResumeThread during injection.

Persistence has been observed via HKCU\Software\Microsoft\Windows\CurrentVersion\Run and, for higher-privileged users, scheduled tasks. QakBot stores configuration in the registry under HKCU\Software\Microsoft[RandomDir] and drops a copy of its DLL under %APPDATA%\Microsoft[RandomDir]. It may later remove persistence artifacts as an anti-forensics measure.

Capabilities described in the content include host and network discovery, lateral movement support, credential theft, browser data theft, email theft, web injection, payload delivery, proxying, and exfiltration. QakBot can execute WMI queries to gather information; run discovery commands such as net view, arp -a, ipconfig /all, net share, route print, netstat -nao, net localgroup, whoami /all, and nslookup queries for domain controller discovery; identify peripheral devices; and use PowerShell to download and execute payloads. It can collect usernames and passwords from Firefox and Chrome, abuse esentutl.exe to access Internet Explorer and Microsoft Edge web cache data, send stolen information including passwords, accounts, and emails to command-and-control nodes, and store stolen emails and other data in new folders prior to exfiltration. Its web inject module can inject JavaScript into online banking pages visited by victims. QakBot can Base64-encode system information sent to C2 and includes a module that can proxy C2 communications.

Command and control is described as HTTPS POST communications to hardcoded C2 servers, with host fingerprinting and discovery data sent upstream. QakBot infections frequently hand off to additional tooling and post-exploitation frameworks including Cobalt Strike, Brute Ratel, and fileless .NET Mimikatz, and multiple reports tie QakBot intrusions to subsequent ransomware deployment. Reported downstream ransomware associations in the content include Royal, Egregor, Black Basta, Conti, DoppelPaymer, Maze, ProLock, and REvil. CERT-FR reporting cited Qbot/QakBot as a common initial access vector for the Lockean affiliate group, often delivered via Emotet or TA551, while Sophos reported Qbot delivered by malicious emails in Egregor attacks. The content also notes that QakBot remains prevalent alongside Emotet and has been widely distributed in campaigns that lead to ransomware-as-a-service affiliate handoffs.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

EXPLOITED CVES

Vulnerabilities exploited

6 CVEs Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

6 CVES
CVE-2022-30190FollinaExploited in the wild

DEV-0464 also rapidly adopted the Microsoft Support Diagnostic Tool (MSDT) vulnerability (CVE-2022-30190) in their campaigns. | September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
CVE-2020-1472ZerologonExploited in the wild

These vulnerabilities are designated as CVE-2020-1472 (Zerologon) ... In the Qbot and Zerologon Lead To Full Domain Compromise report we saw ZeroLogon. | IcedID, Qbot, and Gootloader have all been observed making use of Scheduled Tasks ... Process injection was used both by initial access malware like Qbot ... In one of the earliest reports from the year, we observed Qbot continue to steal email inboxes from infected systems for use in later campaigns.

via dfir reportthedfirreport.com
CVE-2023-28252Windows Common Log File System Driver Elevation of Privilege VulnerabilityExploited in the wild

"The threat actor gained initial access to the organization via Qakbot infection..." | The threat actor gained initial access to the organization via Qakbot infection, followed by the exploitation of a Windows CLFS vulnerability (CVE-2023-28252) to elevate their privileges on affected devices.

via microsoft security blogmicrosoft.com
CVE-2024-30051Windows DWM Core Library Elevation of Privilege VulnerabilityExploited in the wild

Microsoft previously addressed an actively exploited zero-day flaw in DWM in May 2024 (CVE-2024-30051), which was described as a privilege escalation flaw that was abused by multiple threat actors, in connection with the distribution of QakBot and other malware families.

via the hacker newsthehackernews.com
CVE-2023-21716Microsoft Word RTF Heap Corruption Remote Code Execution

Windows Office Product Spawned Uncommon Process ... CVE-2023-21716 Word RTF Heap Corruption, CVE-2023-36884 Office and Windows HTML RCE Vulnerability ...

via splunk researchresearch.splunk.com
CVE-2025-55182React2Shell

Threat Details and IOCs Malware: ... Qbot ...

via f5 communitycommunity.f5.com
THREAT ACTORS

Groups observed using it

18 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
DEV-0450

September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
DEV-0506

September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
DEV-0464

September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
DEV-0826

September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
DEV-0216

September 2022 update – New information about recent Qakbot campaigns leading to ransomware deployment. ... Another widely distributed malware, Qakbot, also leads to handoffs to RaaS affiliates.

via microsoft generalmicrosoft.com
Lockean

In most of the attacks described in the report, the threat actor gained initial access to the victim network through Qbot/QakBot, a banking trojan that changed its role to distribute other malware, including ransomware strains ProLock, Egregor, and DoppelPaymer.

via bleeping computerbleepingcomputer.com
TA577

This malware was first observed being distributed by TA577, an IAB known as a prolific Qbot distributor prior to the malware’s disruption in 2023.

via proofpoint threat insight blogproofpoint.com
Storm-1811

In several cases, Microsoft Threat Intelligence identified such activity leading to the download of Qakbot, RMM tools like ScreenConnect and NetSupport Manager, and Cobalt Strike. Qakbot has been used over the years as a remote access vector to deliver additional malicious payloads that led to ransomware deployment.

via microsoft security blogmicrosoft.com
VortexWerewolf

QakBot (Qbot/Quakbot) continues to operate well after the FBI's August 2023 "Operation Duck Hunt" takedown. Campaign tchk08, first observed February 2024, delivers QakBot via an MSI installer masquerading as Adobe Acrobat.

via breakglass intelintel.breakglass.tech
BlackBasta

“The presence of actors like Cortes, with ties to Qakbot, demonstrates how ransomware crews frequently outsource expertise, rely on external access brokers or pull in operators with malware-specific experience as needed.”

via cso onlinecsoonline.com
FIN7

In March 2023, CTU researchers observed an intrusion deploying Clop ransomware stemming from a Qakbot infection...

via secureworks threat profilessecureworks.com
MALLARD SPIDER

"...QakBot infections have led to the deployment of ransomware, including Egregor, Maze, DoppelPaymer, MedusaLocker and ProLock."

via crowdstrike bloggo.crowdstrike.com
Storm-0506

"The threat actor gained initial access to the organization via Qakbot infection..."

via microsoft security blogmicrosoft.com
TA570

A threat actor designated by Proofpoint as TA570 routinely pushes Qakbot (Qbot) malware... TA570 Qakbot distribution included Word documents using the CVE-2022-30190 (Follina) exploit (ms-msdt).

via sans iscisc.sans.edu
TA542

Qbot affiliate id “partner01” is the primary payload dropped by Emotet seen almost daily.

via proofpoint threat insight blogproofpoint.com
TA551

The eSentire Security Operations Center (SOC) has intercepted several incidents stemming from a recent Qakbot campaign. Qakbot is a malware-as-a-service (MaaS) known to precede ransomware intrusions associated with Maze, Egregor, and Conti ransomware groups.

via esentire blogesentire.com
Cardinal

“It also had a strong association with the Qakbot botnet, prior to its takedown in August 2023.”

via symantec blogsecurity.com
UNC2633

"In at least two of those instances, UNC2633 used the zero-day vulnerability to distribute QAKBOT on the victims' networks."

via mandiant threat intelligencecloud.google.com
MITRE ATT&CK

Techniques & procedures

35 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

2 techniques
T1566PhishingEvidence2

In the Ryuk attacks we saw with SystemBC, initial compromise came from phishing messages that delivered the Buer Loader malware; other attacks in the same campaign used Bazar or Zloader. The Egregor attacks we saw used another loader dropped by malicious emails—Qbot.

T1566.001Spearphishing AttachmentEvidence2

Qakbot is delivered via email, often downloaded by malicious macros in an Office document.

Execution

7 techniques
T1047Windows Management InstrumentationEvidence1
TacticExecution

The content repeatedly describes threat actors and malware using WMI/WMIC/wmiexec for remote execution, lateral movement, discovery, persistence, and administrative actions; e.g., 'APT41 used WMI in several ways, including for execution of commands via WMIEXEC as well as for persistence via PowerSploit' and 'Scattered Spider used Windows Management Instrumentation (WMI) to move laterally via Impacket.'

T1053.005Scheduled TaskEvidence1

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1059.001PowerShellEvidence1
TacticExecution

The content repeatedly describes threat actors and malware using PowerShell scripts/commands for execution, download, staging, reconnaissance, persistence, credential access, lateral movement, and defense evasion; e.g., "Sandworm Team used PowerShell scripts to run a credential harvesting tool in memory to evade defenses."

T1059.003Windows Command ShellEvidence1
TacticExecution

During the 2016 Ukraine Electric Power Attack, Sandworm Team used the xp_cmdshell command in MS-SQL. During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run cmd.exe commands on multiple victim machines. Numerous malware families and groups are described as using cmd.exe, cmd /c, Windows command shell, or command-line interfaces to execute commands, payloads, reconnaissance, persistence, cleanup, and ransomware actions.

T1059.007JavaScriptEvidence1
TacticExecution

AppleSeed has the ability to use JavaScript to execute PowerShell. APT32 has used JavaScript for drive-by downloads and C2 communications. Astaroth uses JavaScript to perform its core functionalities.

T1204.002Malicious FileEvidence1
TacticExecution

For the first time, researchers saw Qbot delivered via malicious Windows Installer (MSI) packages, suggesting that at least one subset of operators may be experimenting with new ways to evade victims’ defenses. | In past campaigns, adversaries used weaponized Microsoft Office documents, which were embedded with malicious macros and delivered via phishing campaigns. Upon macro execution, victims downloaded and executed a Qbot payload, typically without knowing it.

T1569.002Service ExecutionEvidence1
TacticExecution

Qakbot was leveraged to remotely create a temporary service on a target host which was configured to execute a Qakbot DLL using regsvr32.exe.

Persistence

4 techniques
T1053.005Scheduled TaskEvidence1

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1112Modify RegistryEvidence3

The content repeatedly describes threat actors and malware modifying, creating, deleting, or storing data in Windows Registry keys and values for persistence, configuration storage, defense evasion, credential access, privilege escalation, and execution. | Many malware families store configuration, payloads, encryption keys, C2 addresses, or other operational data in Registry keys, such as QakBot storing configuration in a randomly named subkey under HKCU\Software\Microsoft and PolyglotDuke writing encrypted JSON configuration files to the Registry.

T1547Boot or Logon Autostart ExecutionEvidence1

Examples include 'adds Registry Run keys to establish persistence', 'creates a shortcut in the Startup folder', and 'RunOnce Registry key to run itself on safe mode.'

T1547.001Registry Run Keys / Startup FolderEvidence2

Examples include: 'APT18 establishes persistence via the HKCU\Software\Microsoft\Windows\CurrentVersion\Run key'; 'APT28 has deployed malware that has copied itself to the startup directory for persistence'; 'FIN7 malware has created Registry Run and RunOnce keys to establish persistence, and has also added items to the Startup folder.' | The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, or .lnk files in the Startup folder.

T1053.005Scheduled TaskEvidence1

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1547Boot or Logon Autostart ExecutionEvidence1

Examples include 'adds Registry Run keys to establish persistence', 'creates a shortcut in the Startup folder', and 'RunOnce Registry key to run itself on safe mode.'

T1547.001Registry Run Keys / Startup FolderEvidence2

Examples include: 'APT18 establishes persistence via the HKCU\Software\Microsoft\Windows\CurrentVersion\Run key'; 'APT28 has deployed malware that has copied itself to the startup directory for persistence'; 'FIN7 malware has created Registry Run and RunOnce keys to establish persistence, and has also added items to the Startup folder.' | The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, or .lnk files in the Startup folder.

Stealth

6 techniques
T1027Obfuscated Files or InformationEvidence1
TacticStealth

The content repeatedly describes malware and threat actors using obfuscated code, encrypted strings, Base64/XOR/RC4/AES encoding, VMProtect/ConfuserEx/SmartAssembly, stack strings, control-flow flattening, opaque predicates, and hidden payloads to evade analysis and detection.

T1027.009Embedded PayloadsEvidence1
TacticStealth

JPIN uses a encrypted and compressed payload that is disguised as a bitmap within the resource section of the installer. Ramsay has base64-encoded its portable executable and hidden itself under a JPG header. TEARDROP created and read from a file with a fake JPG header.

T1070Indicator RemovalEvidence1
TacticStealth

Examples throughout the content include deleting tools, logs, malware-related files, staged archives, screenshots, temporary files, and exfiltrated data 'to cover their tracks,' 'reduce their footprint,' 'remove traces of activity,' or as part of 'post-intrusion cleanup.'

T1070.004File DeletionEvidence2
TacticStealth

The content repeatedly describes threat actors and malware deleting files, tools, scripts, logs, droppers, staged data, and artifacts from compromised systems to cover tracks, remove evidence, or self-delete.

T1218.010Regsvr32Evidence2
TacticStealth

Qakbot was leveraged to remotely create a temporary service on a target host which was configured to execute a Qakbot DLL using regsvr32.exe: regsvr32.exe -s \\SYSVOL\\.dll

T1564.004NTFS File AttributesEvidence1
TacticStealth

QakBot has hidden code within Excel spreadsheets by turning the font color to white and splitting it across multiple cells. Ramsay can also embed information within document footers.

T1112Modify RegistryEvidence3

The content repeatedly describes threat actors and malware modifying, creating, deleting, or storing data in Windows Registry keys and values for persistence, configuration storage, defense evasion, credential access, privilege escalation, and execution. | Many malware families store configuration, payloads, encryption keys, C2 addresses, or other operational data in Registry keys, such as QakBot storing configuration in a randomly named subkey under HKCU\Software\Microsoft and PolyglotDuke writing encrypted JSON configuration files to the Registry.

Credential Access

3 techniques
T1003OS Credential DumpingEvidence1

The content references collection of credential material from local systems, including "Bumblebee can capture and compress stolen credentials from the Registry and volume shadow copies," "GALLIUM collected ... password hashes from the SAM hive in the Registry," and "Windigo has used a script to gather credentials in files left on disk by OpenSSH backdoors."

T1555Credentials from Password StoresEvidence1

Operation MidnightEclipse stole saved cookies and login data from targeted systems; IceApple can collect files, passwords, and other data from a compromised host; RedLine Stealer collected chat logs and files associated with chat services.

T1555.003Credentials from Web BrowsersEvidence2

PowerLess has the ability to exfiltrate data, including Chrome and Edge browser database files, from compromised machines. QakBot can use esentutl.exe to steal sensitive data from Internet Explorer and Microsoft Edge.

Discovery

4 techniques
T1016System Network Configuration DiscoveryEvidence1
TacticDiscovery

Atomic Test #9 - DNS Server Discovery Using nslookup Identify System domain dns controller on an endpoint using nslookup ldap query. This tool is being abused by qakbot malware to gather information on the domain controller of the targeted or compromised host. | T1016 - System Network Configuration Discovery Description from ATT&CK ... Adversaries may look for details about the network configuration and settings, such as IP and/or MAC addresses, of systems they access ... Examples include Arp, ipconfig/ifconfig, nbtstat, and route.

T1057Process DiscoveryEvidence1
TacticDiscovery

The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.

T1082System Information DiscoveryEvidence3
TacticDiscovery

The content repeatedly describes malware and threat actors collecting host details such as OS version, hostname, architecture, CPU, memory, BIOS, domain, language, and other configuration data; e.g., "APT41 uses multiple built-in commands such as systeminfo and net config Workstation to enumerate victim system basic configuration information."

T1120Peripheral Device DiscoveryEvidence1
TacticDiscovery

The content repeatedly describes malware and threat actors identifying, monitoring, or enumerating connected peripheral devices such as USB mass storage, Bluetooth devices, printers, smart card readers, cameras, Apple devices, VGA/display devices, and removable drives.

Collection

4 techniques
T1005Data from Local SystemEvidence2

The content repeatedly describes threat actors and malware collecting, stealing, identifying, copying, or staging files, documents, credentials, logs, databases, and other information from compromised hosts or local systems.

T1074Data StagedEvidence1

The content repeatedly describes adversaries and malware storing collected data, command output, credentials, archives, or files in local temporary folders, working directories, hidden directories, registry locations, recycle bins, or specific files prior to exfiltration.

T1114Email CollectionEvidence1

Qakbot’s initial actions include profiling the system and the network, and exfiltrating emails (.eml files) for later use as templates in its malware distribution campaigns.

T1185Browser Session HijackingEvidence1

The QakBot web inject module can inject Java Script into web banking pages visited by the victim.

T1071Application Layer ProtocolEvidence2

Qakbot was the primary method utilised by the threat actor to maintain their presence on the network. The threat actor was also observed using Cobalt Strike beacons during the compromise.

T1090.003Multi-hop ProxyEvidence1

APT28 used other victims as proxies to relay command traffic, for instance using a compromised Georgian military email server as a hop point to NATO victims.

T1105Ingress Tool TransferEvidence2

Matanbuchus mainly downloads and executes different payloads like Qbot and Cobalt Strike beacons... It downloads the attacker’s payload from the given URL, saves it to the disk and executes it... the loader can download the attacker’s payload from any remote server like free hosting services.

T1132Data EncodingEvidence2

C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding... APT19 HTTP malware variant used Base64 to encode communications to the C2 server... APT33 has used base64 to encode command and control traffic.

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence2

ADVSTORESHELL exfiltrates data over the same channel used for C2... Agrius exfiltrated staged data using tools such as Putty and WinSCP, communicating with command and control servers... numerous malware and groups sent victim data, files, credentials, or host information over existing C2 channels.

Other

1 technique
T1562Impair DefensesEvidence1

The content repeatedly describes threat actors and malware disabling, stopping, uninstalling, or modifying antivirus, EDR, Windows Defender, AMSI, logging, and other security controls.

INDICATORS OF COMPROMISE

IOCs tracked for this family

465 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
394 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
67 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

Other
4 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app3 months ago
domain●●●●●●●●●●●●View more in app3 months ago
hash.md5●●●●●●●●●●●●View more in app3 months ago
hash.md5●●●●●●●●●●●●View more in app3 months ago
hash.sha1●●●●●●●●●●●●View more in app3 months ago
hash.sha1●●●●●●●●●●●●View more in app3 months ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching465

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution18

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities6

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping35

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.