Qbot

Category: banking_trojan · Aliases: Qakbot, Pinkslipbot, Trojan.Qbot, Banking.Qakbot, Win32/Qakbot, qbot · Sample count (EMBER 2018): 1,758 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: Banking_TrojanStatus: Automated Signature🔥 Active Emerging ThreatPlatform: WINDOWS_PEStage: Credential Access, Collection, ExfiltrationFirst seen: 2007Status: disrupted 2023 resurgedActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
QakBot (widely referenced as Qbot or Pinkslipbot) is an aggressive, modular banking trojan and malware loader that operated for over 16 years, emerging around 2007 and evolving into one of the most prolific initial access vectors for enterprise ransomware operators.

Table of Contents

Overview

QakBot (widely referenced as Qbot or Pinkslipbot) is an aggressive, modular banking trojan and malware loader that operated for over 16 years, emerging around 2007 and evolving into one of the most prolific initial access vectors for enterprise ransomware operators. QakBot spreads primarily via weaponized email phishing campaigns featuring malicious OneNote documents, hijacked email thread replies, and weaponized archives (ZIP, ISO, VHD). Once running on an endpoint, QakBot injects into legitimate processes (such as wermgr.exe or mobsync.exe), steals stored web browser credentials, harvests emails to conduct thread-hijacking for secondary spreading, and performs automated Active Directory and network reconnaissance. In high-value corporate intrusions, QakBot operators historically brokered access to major ransomware syndicates, including Black Basta, Conti, REvil, and MegaCortex. In August 2023, the U.S. Department of Justice, FBI, and Europol executed 'Operation Duck Hunt', seizing 52 C2 servers, recovering $8.6 million in illicit cryptocurrency, and sending uninstallation instructions to over 700,000 compromised host computers worldwide.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Known Derivatives & Downstream Variants: Pinkslipbot

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027.006Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-STMScheduled Task Creation AnalysisDetectT1053.005Audit task creation targeting system and hidden service directories; verify task author credentials.
D3-DIADLL Injection AnalysisDetectT1055.001Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe).
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTPS
Observed ports443, 995, 2222
Infrastructure modelMulti-tiered peer-to-peer (P2P) proxy mesh consisting of infected residential and small-business routers/workstations routing traffic to hidden primary backend Tier-2/Tier-3 C2 servers.
Encryption / encodingRC4 encrypted configurations with static keys and hardcoded salts; TLS transport with dynamically generated self-signed SSL/TLS certificates.
Traffic fingerprintDirect outbound TLS sessions from enterprise client endpoints to residential dynamic IP ranges on non-standard TLS ports (such as 995, 2222, and 443) featuring low-entropy self-signed certificates.
Identifiable from traffic aloneHigh

Network detection ideas

Sources: US DOJ Operation Duck Hunt Announcement, abuse.ch Feodo Tracker

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Detection Guidance

Detection ideas drawn from public reporting. Tune to your environment before deploying.

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_QBOT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Qbot"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "qbot" ascii wide nocase
        $s2 = "qakbot" ascii wide nocase
        $s3 = "pinkslipbot" ascii wide nocase
        $s4 = "trojan.qbot" ascii wide nocase
        $s5 = "banking.qakbot" ascii wide nocase
        $s6 = "win32/qakbot" ascii wide nocase
        $s7 = "qbot" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Qbot (Banking Trojan) Execution & Triage
id: a9930fcf-bcad-5f93-8bfa-237b0ffc9f9e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Qbot malware family. Detects recon staging, certutil file payload staging,
  and web-inject process proxying characteristic of banking trojan initial loaders.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/qbot
- https://malware-families-catalog.systemhelpdesk.com/defensive/banking-trojan-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.banking-trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1055
- attack.t1078
- attack.t1185
- attack.t1003_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \svchost.exe
    - \explorer.exe
    - \msiexec.exe
    - \certutil.exe
    CommandLine|contains:
    - -urlcache
    - -split -f
    - ipconfig /all
    - route print
    - netstat -ano
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_QBOT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Qbot tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "qbot" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Run FBI-distributed Qakbot uninstaller (where applicable per the 2023 takedown)
  2. Isolate the host and block C2 IP ranges
  3. Rotate credentials in browser stores and email clients on host
  4. Hunt for Cobalt Strike beacons and follow-on ransomware staging

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not rely solely on AV signatures; Qbot updates frequently
  2. Do not restore from backups without verifying the backup pre-dates infection
  3. Do not ignore email reply-chain hijacking — notify recipients

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: AA23-242A: QakBot Malware Disrupted in International Cyber Takedown ↗

Frequently Asked Questions

What is QakBot (Qbot)?

QakBot is a modular banking trojan and malware loader active since 2007 that steals corporate credentials, hijacks email conversation threads, and delivers high-impact ransomware payloads like Black Basta and Conti.

What was Operation Duck Hunt?

Operation Duck Hunt was an August 2023 multinational law enforcement action led by the FBI and DOJ that seized QakBot's C2 infrastructure, seized $8.6 million in crypto, and disinfected over 700,000 infected computers.

How does QakBot move laterally across enterprise networks?

QakBot harvests domain credentials using LSASS memory dumping, exploits Zerologon (CVE-2020-1472), and uses SMB/PsExec to propagate automatically across administrative network shares.

What network ports does QakBot C2 utilize?

In addition to standard HTTPS port 443, QakBot commonly routes encrypted C2 beacons through proxy bots on ports 995 (traditionally POP3S) and 2222.

How can organizations mitigate QakBot delivery?

Block inbound emails containing ISO, VHD, or OneNote attachments, enforce multi-factor authentication on all remote access endpoints, and isolate workstations exhibiting abnormal TLS beaconing to residential IP subnets.

How do I remove the Qbot Banking_Trojan from Windows?

Manual removal of Qbot is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Qbot a virus or a Banking_Trojan?

Qbot is classified as a Banking_Trojan. Unlike traditional viruses that infect files, modern malware like Qbot typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Qbot infection?

Symptoms of Qbot can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Banking_Trojans

Want to prevent Qbot and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/qbot.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.