Skip to main content
Mallory
← Back to News
loader-delivery-mechanismphishing-campaign-intelligencecommand-and-control-methodremote-access-implant

Qakbot Infections Led to Cobalt Strike and VNC Access on Windows Hosts

Malware Intelligence · 9 sources · Updated 3mo ago · First seen Mar 14, 2022

Qakbot Infections Led to Cobalt Strike and VNC Access on Windows Hosts

Multiple incident reports describe Qakbot infections delivered through phishing emails that linked to ZIP archives containing malicious Excel files, often using Excel 4.0 macros to fetch DLL payloads. On compromised Windows systems, the malware executed downloaded DLLs with regsvr32.exe, contacted multiple command-and-control servers, and in some cases used distribution tags such as obama166 and aa. Researchers observed Qakbot storing artifacts on disk, changing persistence behavior compared with earlier variants, and in broader campaigns stealing Outlook credentials, adding Windows Defender exclusions, and using internal email threads to spread further inside organizations.

Follow-on activity showed operators deploying Cobalt Strike and VNC-based remote access, including DarkVNC traffic over TCP 443 and VNC beaconing detected after the initial compromise. In one analyzed case, Cobalt Strike and VNC activity appeared about 17 hours after infection, indicating a second-stage intrusion after Qakbot established foothold. Additional reporting ties these intrusions to hands-on-keyboard actions such as reconnaissance, lateral movement over SMB admin shares, service-based persistence, and preparation for ransomware deployment, while one campaign also reportedly abused PrintNightmare (CVE-2021-34527) for SYSTEM-level execution and may have leveraged ProxyLogon and ProxyShell to help distribute malicious emails in enterprise environments.

Hunt this familyPull IOCs and campaign context straight into your stack.
Get the IOCs
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

9 events · 2007 – Mar 14, 2022
  1. Reported Apr 9, 20267mo ago

    Cynet reports Quakbot operators exploiting PrintNightmare

    Cynet reported Quakbot intrusions in which operators used phishing-delivered Excel documents, regsvr32.exe execution, persistence mechanisms, Cobalt Strike, and later-stage exploitation of PrintNightmare to gain SYSTEM-level execution by planting a malicious DLL in the spooler driver path. The report also noted suspected abuse of ProxyLogon and ProxyShell in some enterprise environments.

    Quakbot Strikes with QuakNightmare Exploitation
  2. Reported Jan 1, 202611mo ago

    Secureworks documents Qakbot-to-Cobalt Strike intrusion chain

    Secureworks described incidents in which GOLD LAGOON used phishing-delivered Excel 4.0 macros to install Qakbot, which then downloaded Cobalt Strike Beacon for reconnaissance, lateral movement, persistence, and potential ransomware deployment. The report also contrasted a REvil ransomware case with another intrusion contained before ransomware execution.

    Detecting Cobalt Strike: Cybercrime Attacks | SOPHOS
  3. Reported May 8, 20243y ago

    Cobalt Strike and VNC activity follow Qakbot compromise

    About 17 hours after the 2022-03-14 Qakbot infection, the host generated Cobalt Strike traffic to 190.123.44[.]113 over port 4444 using runfs[.]icu and VNC beacon traffic to 45.153.241[.]142 over port 443. Security Onion produced ETPRO alerts identifying the VNC activity as VNCStartServer command-and-control beaconing.

    Qakbot infection with Cobalt Strike and VNC activity
  4. Reported Apr 20, 20225y ago

    Qakbot infection leads to DarkVNC follow-on traffic

    A phishing email led to a ZIP archive and malicious Excel spreadsheet that downloaded multiple Qakbot DLLs, executed them with regsvr32.exe, and generated post-infection C2 traffic. The same intrusion also produced DarkVNC traffic to 45.153.241[.]142 over TCP 443, indicating follow-on remote access activity.

    "aa" distribution Qakbot (Qbot) infection with DarkVNC traffic
  5. Mar 14, 20225y ago

    Qakbot infects Windows host via malicious email and ZIP link

    On 2022-03-14, a vulnerable Windows host was infected with Qakbot after a malicious email linked to a ZIP archive containing an Excel spreadsheet whose macro downloaded DLL payloads. The payloads were saved locally and executed via regsvr32.exe.

    Qakbot infection with Cobalt Strike and VNC activity
  6. Dec 9, 20215y ago

    Microsoft details Qakbot phishing via Craigslist relay and embedded-image lures

    Microsoft reported that recent Qakbot campaigns used embedded-image phishing lures impersonating Craigslist notifications and abused Craigslist’s legitimate email relay system to send anonymized messages from the craigslist.org domain. The analysis also described related delivery and post-infection building blocks, including Excel 4.0 macro documents, regsvr32-based process injection, scheduled-task persistence, credential theft, and email exfiltration.

    A closer look at Qakbot’s latest building blocks (and how to knock them down) | Microsoft Security Blog
  7. Jul 1, 20215y ago

    Microsoft publishes advisory for PrintNightmare CVE-2021-34527

    Microsoft's Security Update Guide published an advisory for the Windows Print Spooler Remote Code Execution Vulnerability tracked as CVE-2021-34527.

    Windows Print Spooler Remote Code Execution Vulnerability
  8. Dec 8, 20206y ago

    SANS documents 2020-12-08 Qakbot infection after late-November update

    SANS analyzed a Qakbot infection generated on 2020-12-08 in which fake-reply malspam delivered a ZIP archive containing a malicious Excel spreadsheet that downloaded a Qakbot DLL and executed it via Rundll32.exe. The report highlighted behavioral changes from a late-November 2020 update, including a switch from EXE to DLL payloads and new encoded registry persistence under HKCU\SOFTWARE\Microsoft instead of the Run key.

    Recent Qakbot (Qbot) activity - SANS Internet Storm Center
  9. 2007

    Quakbot malware becomes active as a banking trojan

    A Cynet report states Quakbot has been active since the end of 2007 as a modular banking trojan.

    Quakbot Strikes with QuakNightmare Exploitation
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Threat actors

2 linked

Malware

2 linked

Observables

86 linked

Indicator values are masked on this page. View all 86 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
Hunt This Malware
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.