Gamehuck

Overview

PWS:Win32/Gamehuck is a highly specialized Password Stealer (PWS) trojan designed specifically to target, harvest, and exfiltrate credentials and valuable digital assets from online gaming platforms (such as Steam, Battle.net, Origin, and various MMOs). The primary motivation behind Gamehuck is financial; stolen accounts with rare in-game items or linked credit cards are rapidly sold on underground forums.

Understanding Gamehuck
To an end-user, the infection often begins when they download a 'cheat', 'aimbot', or 'currency generator' for a popular video game. The malware operates silently in the background, specifically monitoring for the launch of targeted gaming clients. For security analysts, while Gamehuck might seem like a consumer-focused threat, its presence on a corporate endpoint indicates a severe violation of acceptable use policies and proves that the user is actively bypassing security controls to execute untrusted binaries.

Execution and Credential Harvesting Mechanics
Gamehuck is almost exclusively distributed via deceptive social engineering on gaming forums, Discord servers, and YouTube videos advertising game hacks (`T1204.002`). Upon execution, the malware establishes persistence via the `HKCU\Software\Microsoft\Windows\CurrentVersion\Run` registry key (`T1547.001`). Its core functionality revolves around credential access (`T1555`). It scans the file system for specific configuration files (like Steam's `ssfn` authorization files) and uses keylogging (`T1056.001`) when the user types their password into the gaming client. Advanced variants also attempt to steal session cookies from web browsers to bypass Multi-Factor Authentication (MFA) on the gaming platforms (`T1539`). The harvested data is then encrypted and exfiltrated to a C2 server or dropped into a Telegram channel (`T1041`).

Indicators of Compromise & Impact
The primary impact is the loss of personal gaming accounts and potential financial loss, though on a corporate network, it represents a compromised endpoint. IoCs include EDR alerts for keylogging activity (API hooks on `SetWindowsHookEx`) originating from a recently downloaded binary. Network analysts might observe unauthorized FTP or HTTP POST requests containing encrypted archives sent to unusual IP addresses.

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:

• 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.

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_GAMEHUCK {
    meta:
        description = "Detects Gamehuck (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "gamehuck" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

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

Containment & Response Steps

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

1. Isolate the endpoint to prevent further exfiltration of credentials or the download of secondary payloads.
2. Force a password reset for all corporate accounts used by the individual, as the keylogger may have captured more than just gaming credentials.
3. Use EDR to locate and terminate the Gamehuck process, and remove the associated Registry Run keys.
4. Investigate how the user was able to download and execute an untrusted, unapproved binary (the 'game hack') on the corporate network.

What to Avoid

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

1. Do not assume only gaming credentials were stolen; keyloggers capture everything typed, including corporate VPN passwords and sensitive emails.
2. Avoid dismissing the incident as 'just a game hack'; the endpoint is fully compromised and must be treated as a security breach.

References & External Analysis

• Search "gamehuck" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Staem
• Tinukebot
• Bitmin
• Infinitetear
• Termite

Machine-readable

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