Qqshou
Table of Contents
Overview
Trojan:Win32/Qqshou is a specialized trojan designed to target users of the immensely popular Chinese instant messaging platform, Tencent QQ. Its primary objective is the theft of QQ login credentials, virtual currency (Q coins), and in-game assets linked to the account, which are then sold on underground markets.
Understanding Qqshou (Credential Stealers)
To an end-user, a Qqshou infection usually goes unnoticed until they find themselves locked out of their QQ account or discover their virtual currency has been drained. For a threat intelligence analyst, Qqshou represents a highly targeted, region-specific credential stealer that utilizes keylogging and memory scraping techniques focused entirely on a single application ecosystem.
Execution and Data Exfiltration Mechanics
Qqshou is typically distributed via malicious links sent through QQ itself, disguised as game cheats, or bundled with pirated software. Upon execution, it establishes persistence (often via Registry Run keys) and actively monitors the system for the execution of the legitimate Tencent QQ client (`qq.exe`). When detected, Qqshou employs various techniques to steal credentials: it may inject a keylogger to capture keystrokes when the QQ window is in focus (`T1056.001`), or it may use memory scraping to extract session tokens directly from the process memory (`T1003`). The stolen data is then exfiltrated to an attacker-controlled server, often via HTTP POST requests or even by sending an email.
Indicators of Compromise & Impact
The primary impact is the loss of the QQ account and associated financial assets. Host-based IoCs include EDR alerts for suspicious API calls (like `SetWindowsHookEx` for keylogging) originating from an unknown process and targeting `qq.exe`. Network IoCs involve anomalous outbound connections (often SMTP or HTTP) transmitting encrypted or encoded data immediately after the user logs into QQ.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1056.001 | Input Capture: Keylogging (Capturing keystrokes when the QQ client is active) | Collection | ATT&CK ↗ |
T1003 | OS Credential Dumping (Scraping memory for session tokens) | Credential Access | ATT&CK ↗ |
T1114 | Email Collection (Sometimes used to exfiltrate stolen data) | Collection | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1003: Monitor for LSASS memory dumping or registry SAM extraction. Enable Credential Guard on Windows systems.
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-LSA | LSASS Memory Protection | Harden | T1003 | Enable Windows Credential Guard (LsaCfgFlags) and restrict debug privileges (SeDebugPrivilege). |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-EAM | Email Access Monitoring | Detect | T1114 | Monitor Graph API and MAPI email harvesting routines and alert on bulk email downloads originating from unusual IP addresses. |
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_QQSHOU_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Qqshou"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "qqshou" 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 - Qqshou (Trojan) Execution & Triage
id: a40f2045-45e3-5edb-83ce-4b3d6518d5f3
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Qqshou malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/qqshou
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1114
- attack.t1003
- attack.t1056_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_QQSHOU_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Qqshou 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 = "qqshou" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Isolate the infected machine and use a clean device to immediately change the password for the compromised QQ account and enable two-factor authentication.
- Run a full system scan using a reputable anti-malware solution to locate and remove the Qqshou executable and its persistence mechanisms.
- Report the compromise to Tencent support to attempt recovery of any stolen virtual currency or assets.
- Review the account's recent activity for unauthorized messages sent to contacts (as Qqshou may be used to spread itself).
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not continue to use the infected machine for any secure logins (banking, email) until it has been thoroughly cleaned, as the keylogger may capture other credentials.
- Avoid clicking on unsolicited links or downloading 'cheats' from untrusted sources, even if sent by a known contact on QQ.
References & External Analysis
- Search "qqshou" on VirusTotal (External Analysis)
- Search "qqshou" on Any.Run (Sandbox Sandbox)
- Search "qqshou" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Qqshou and what threat category does it belong to?
Qqshou is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Qqshou establish persistence and evade defensive controls?
Qqshou typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Qqshou compromise?
Security teams responding to Qqshou should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Qqshou?
Qqshou frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Qqshou across enterprise endpoints?
Defenders should hunt for Qqshou by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Qqshou Trojan from Windows?
Manual removal of Qqshou 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 Qqshou a virus or a Trojan?
Qqshou is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Qqshou typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Qqshou infection?
Symptoms of Qqshou 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 Trojans
Want to prevent Qqshou 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/qqshou.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.