Hvnc

Overview

Backdoor:Win32/hVNC (Hidden Virtual Network Computing) represents a devastatingly stealthy class of Remote Access Trojans (RATs). While standard VNC is a legitimate tool allowing a user to view another computer's desktop, **hVNC is designed to create a completely separate, invisible virtual desktop session** on the infected machine. This allows an attacker to interact with the system, open web browsers, and execute transactions entirely behind the scenes, without the actual user sitting at the computer seeing any anomalous activity on their own screen.

Understanding hVNC (Hidden VNC)
To an end-user, an hVNC infection is undetectable; the mouse doesn't move on its own, and no strange windows pop up on their monitor. For a security analyst, hVNC is a nightmare scenario, often bundled as a premium module within advanced banking trojans (like TrickBot, Emotet, or DanaBot). Attackers use hVNC to bypass device fingerprinting and IP-based fraud detection; because the attacker is opening the browser *on the victim's actual machine*, the bank sees the login coming from the correct IP, the correct MAC address, and with all the victim's saved session cookies intact.

Execution and Virtual Desktop Mechanics
hVNC is typically deployed as a secondary payload after initial compromise (`T1105`). Upon execution, the malware interacts deeply with the Windows operating system APIs. It uses the `CreateDesktop` and `CreateProcess` APIs to spawn a new, hidden Window Station and Desktop object (`T1564.006`). It then launches applications (like Google Chrome) within this hidden desktop (`T1055`). The hVNC server component captures the frame buffer of this hidden desktop and streams it back to the attacker's C2 server (`T1071.001`), while intercepting the attacker's mouse and keyboard inputs and injecting them into the hidden session. This allows the attacker to log into bank accounts, bypassing 2FA if the victim's browser session is already authenticated.

Indicators of Compromise & Impact
The impact is total compromise of the endpoint and near-guaranteed financial fraud. Host-based IoCs require advanced EDR: look for anomalous processes (like a second instance of `explorer.exe` or `chrome.exe`) running under a non-default Window Station (e.g., something other than `WinSta0\Default`). Network IoCs include a constant, high-bandwidth outbound stream of encrypted traffic (the VNC video feed) to a known C2 IP address.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

Tactical Mitigations

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

• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
• T1185: Enforce strong MFA and use browser isolation or hardened browsers for sensitive financial or administrative portals to defeat session hijacking.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_HVNC {
    meta:
        description = "Detects Hvnc (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "hvnc" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Hvnc Activity
id: a2298e5b3219ded7af96845803715b17
status: experimental
description: Detects generic indicators of the hvnc malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*hvnc*"
    condition: selection
level: medium

Containment & Response Steps

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

1. Immediately isolate the endpoint from the network to terminate the active hVNC session and stop the attacker from interacting with the hidden desktop.
2. Assume all logged-in sessions (browser cookies, saved passwords, active VPN tunnels) on the infected machine have been compromised and abused by the attacker.
3. Contact financial institutions immediately to freeze accounts if the infected machine was used for banking or cryptocurrency management.
4. Perform a complete wipe and reimage of the machine, as hVNC modules are often part of larger rootkit or banking trojan infections.

What to Avoid

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

1. Do not assume a machine is safe just because you don't 'see' the attacker moving the mouse; hVNC operates in a completely parallel, invisible desktop.
2. Avoid relying solely on multi-factor authentication (MFA) to protect accounts; if the attacker uses hVNC while the victim is already logged in, the MFA challenge has already been bypassed.

References & External Analysis

• Search "hvnc" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Sphinx
• Netwire
• Onesyscare
• Mmorpg
• Hpcubestlr

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/hvnc.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.