Chromepass
Table of Contents
Overview
HackTool:Win32/Chromepass is a highly specific utility categorized as a Credential Dumper. While it can technically be used legitimately to recover forgotten passwords, it is overwhelmingly utilized by threat actors, embedded within larger info-stealer malware, or executed during hands-on-keyboard attacks to systematically extract all saved passwords from the Google Chrome web browser.
Understanding Chromepass (Credential Dumping)
To an end-user, this tool operates silently; they will not know their passwords have been stolen until their accounts are compromised. For a SOC analyst, the execution of Chromepass is a severe incident indicating that an attacker has gained execution privileges on the endpoint and is actively harvesting credentials (`T1003.001`) to facilitate lateral movement or data theft.
Execution and Extraction Mechanics
Google Chrome stores saved usernames and passwords in a local SQLite database file (typically located at `%LocalAppData%\Google\Chrome\User Data\Default\Login Data`). The passwords within this database are encrypted using the Windows Data Protection API (DPAPI), which ties the encryption key to the currently logged-in Windows user's credentials. Chromepass operates by programmaticly interacting with the DPAPI (`T1555.003`). Because the attacker executes Chromepass within the context of the logged-in user, the tool simply requests Windows to decrypt the database. It then parses the SQLite file and outputs a cleartext list of URLs, usernames, and passwords.
Indicators of Compromise & Impact
The impact is the total compromise of all web credentials saved in the user's browser, potentially leading to unauthorized access to corporate SSO portals, email, and financial accounts. Host-based IoCs include EDR alerts for 'Suspicious Credential Dumping Activity' or processes attempting to unexpectedly read the `Login Data` SQLite file. Command-line logging (Event ID 4688) may capture the execution of known Chromepass binaries or PowerShell scripts interacting with the `CryptUnprotectData` API.
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:
- T1003.001: Monitor for LSASS memory dumping or registry SAM extraction. Enable Credential Guard on Windows systems.
- T1059.001: Restrict execution of PowerShell. Enforce PowerShell Constrained Language Mode and Script Block Logging.
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 | LSA Protection & Credential Guard | Harden | T1003.001 | Enable Windows LSA RunAsPPL (Protected Process Light) and Credential Guard to prevent memory dumping of lsass.exe. |
D3-PSBL | PowerShell Script Block Logging | Detect | T1059.001 | Enable PowerShell event ID 4104 and Constrained Language Mode to neuter obfuscated script payloads. |
D3-CVH | Credential Vault Hardening | Harden | T1555.003 | Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers. |
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_CHROMEPASS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Chromepass"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "chromepass" 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 - Chromepass (Advanced Threat) Execution & Triage
id: 2c245784-f329-5b77-aed2-ca31d6a4005e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Chromepass 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/chromepass
- 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.t1555_003
- attack.t1059_001
- attack.t1003_001
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
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_CHROMEPASS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Chromepass 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 = "chromepass" 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.
- Mandate an immediate password reset for the compromised user, covering ALL corporate accounts and services they access.
- Force a session token revocation for the user across all SaaS applications and internal portals (e.g., Microsoft 365, Okta, VPN).
- Isolate the endpoint to prevent the extracted credentials from being used for immediate lateral movement.
- Analyze EDR telemetry to determine how Chromepass was executed (e.g., dropped by an info-stealer, or run manually via a reverse shell).
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume only the 'work' passwords were stolen; attackers will use personal credentials to access bank accounts and personal email.
- Avoid relying solely on file hashes to detect this tool; the extraction logic can easily be compiled into custom, evasive scripts.
References & External Analysis
- Search "chromepass" on VirusTotal (External Analysis)
- Search "chromepass" on Any.Run (Sandbox Sandbox)
- Search "chromepass" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Chromepass and what threat category does it belong to?
Chromepass is classified as a Advanced Threat. 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 Chromepass establish persistence and evade defensive controls?
Chromepass 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 Chromepass compromise?
Security teams responding to Chromepass 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 lateral movement and credential access tactics does Chromepass leverage in enterprise intrusions?
Chromepass frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Chromepass maintain covert communications and evade perimeter network monitoring?
Chromepass often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove Chromepass from Windows?
Manual removal of Chromepass 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 Chromepass infection?
Symptoms of Chromepass 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 Advanced_Threats
Want to prevent Chromepass and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 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/chromepass.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.