Qqspy

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Process Injection and API Hooking: The spyware specifically searches the system for the active `QQ.exe` process. It injects its malicious DLL into this process and hooks the specific Windows APIs used by QQ for keyboard input and screen rendering, allowing it to intercept passwords before they are securely hashed by the client.
• Data Exfiltration: QQSpy aggressively harvests chat histories, transferred files, and contact lists. It compiles this data into hidden, encrypted archives and periodically transmits it to a remote command-and-control (C2) server.
• Account Hijacking: By stealing the primary QQ token or password, the attacker can hijack the account. This hijacked account is then used to propagate the malware to the victim's contacts, lending an air of legitimacy to the phishing links.

Threat Assessment

Incident Response and Remediation

• Immediate Password Reset: Assume the QQ account is fully compromised. The user must immediately reset their QQ password from a known-clean device and forcefully terminate all active sessions within the QQ security center.
• Endpoint Scanning: Utilize an enterprise-grade anti-malware solution to perform a deep system scan. QQSpy often uses Rootkit techniques to hide its injected DLLs, requiring advanced behavioral analysis for complete removal.
• Network Monitoring: Analyze network traffic for unauthorized connections to known C2 domains associated with this spyware family to identify potentially compromised endpoints across the network.

Known aliases

Threat reports may refer to this family under multiple names:

• Spyware.QQSpy
• Trojan.PWS.QQPass
• Win32/QQSpy

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• 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.
• T1113: Monitor for frequent or unauthorized screen captures or clipboard reads. Restrict background applications from accessing desktop APIs.

MITRE D3FEND™ Defensive Countermeasures

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

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:

rule MALWARE_WIN_QQSPY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Qqspy"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "qqspy" ascii wide nocase
        $s2 = "spyware.qqspy" ascii wide nocase
        $s3 = "trojan.pws.qqpass" ascii wide nocase
        $s4 = "win32/qqspy" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Qqspy (Advanced Threat) Execution & Triage
id: 0ef773ed-a66f-54e4-a542-6b09ed4b25a6
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Qqspy malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/qqspy
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1055_001
- attack.t1113
- attack.t1048
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_QQSPY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Qqspy 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 = "qqspy" 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.

1. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Qqspy adversary activity.
2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Qqspy C2 infrastructure IP/domain lists.
3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Qqspy.
4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Qqspy operators.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Qqspy dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Qqspy until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Search "qqspy" on VirusTotal (External Analysis)
• Search "qqspy" on Any.Run (Sandbox Sandbox)
• Search "qqspy" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Advanced Threat)

Explore other documented threats in the same operational category:

• Doyo
• Xscan
• Regcure
• Menti
• Daum
• Mutabaha
• Deepsea
• Lineage

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/qqspy.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.