Gampass
Table of Contents
Overview
Trojan-PSW:Win32/Gampass is a specialized credential stealer designed specifically to target the lucrative online gaming market. Unlike traditional banking trojans, Gampass targets authentication credentials for platforms like Steam, Origin, Battle.net, and specific MMOs (e.g., World of Warcraft). The attacker's goal is to hijack the accounts to steal and sell valuable virtual items, in-game currency, or the accounts themselves on gray-market forums (`T1552`).
Understanding Gampass (Gaming Credential Stealers)
To an end-user, the infection often goes unnoticed until they attempt to log into their game and find their password changed or their virtual inventory emptied. For threat intelligence, Gampass represents a massive, highly organized underground economy. Because gaming platforms historically had weaker Two-Factor Authentication (2FA) adoption than banks, they became prime targets for rapid monetization.
Execution and Theft Mechanics
Gampass is usually distributed via gaming-related channels: fake 'cheats', 'aimbots', 'currency generators', or malicious links posted in gaming Discord servers or forums (`T1566.002`). Upon execution, the trojan rarely attempts deep persistence. Instead, it immediately scans the file system for specific registry keys, configuration files (`.vdf` files for Steam), or session tokens associated with targeted gaming clients (`T1005`). It also implements keylogging (`T1056.001`) to capture the username and password when the user next logs into the game client. The stolen data is quickly exfiltrated to a C2 server.
Indicators of Compromise & Impact
The impact is the loss of the gaming account and associated virtual assets, which can represent significant real-world monetary value. Host-based IoCs include EDR alerts for unknown executables accessing the specific installation directories of gaming clients (e.g., `C:\Program Files (x86)\Steam`), unauthorized API hooking of keyboard input (`SetWindowsHookEx`), and the rapid creation and deletion of temporary files used for staging stolen data. Network IoCs involve outbound HTTP/FTP traffic to exfiltrate the credentials.
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 |
|---|---|---|---|
T1552 | Unsecured Credentials (Searching for saved session tokens and config files) | Credential Access | ATT&CK ↗ |
T1056.001 | Input Capture: Keylogging (Capturing passwords entered into game clients) | Credential Access | ATT&CK ↗ |
T1005 | Data from Local System (Staging targeted files for exfiltration) | Collection | ATT&CK ↗ |
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.
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-FDM | File Data Monitoring | Detect | T1005 | Deploy Data Loss Prevention (DLP) agents to audit sensitive file access and block unauthorized batch file copying. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
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_GAMPASS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Gampass"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "gampass" 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 - Gampass (Trojan) Execution & Triage
id: f3f1641a-4d5e-5e1e-9810-b0028a431ae9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Gampass 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/gampass
- 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.t1005
- attack.t1552
- 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_GAMPASS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Gampass 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 = "gampass" 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 run a full anti-malware scan to remove the keylogger and credential stealing components.
- The victim MUST initiate account recovery procedures with the affected gaming platforms from a *different, clean device*.
- Enable Two-Factor Authentication (2FA/MFA) on all gaming platforms and associated email accounts.
- Educate users (especially younger demographics) about the severe risks of downloading 'cheats', 'cracks', or 'free currency' generators.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not attempt to change passwords on the infected machine, as the keylogger will simply capture the new password.
- Avoid reusing the same password across multiple gaming platforms, as a compromise on one will lead to a credential stuffing attack on the others.
References & External Analysis
- Search "gampass" on VirusTotal (External Analysis)
- Search "gampass" on Any.Run (Sandbox Sandbox)
- Search "gampass" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Gampass and what threat category does it belong to?
Gampass 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 Gampass establish persistence and evade defensive controls?
Gampass 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 Gampass compromise?
Security teams responding to Gampass 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 Gampass?
Gampass 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 Gampass across enterprise endpoints?
Defenders should hunt for Gampass 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 Gampass from Windows?
Manual removal of Gampass 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.
What are the main symptoms of a Gampass infection?
Symptoms of Gampass 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 Gampass 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/gampass.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.