Memery
Table of Contents
Overview
Memery (cataloged across security software as Trojan:Win32/Memery, Backdoor:Win32/Memery, and Trojan-Spy.Win32.Memery) is an evasive memory-resident trojan and credential harvester. Engineered for stealthy persistence, Memery avoids leaving conspicuous binary artifacts on disk by executing the bulk of its malicious logic directly in host memory. Following initial infection, Memery injects execution threads into critical Windows system processes (such as explorer.exe or svchost.exe) via process hollowing or asynchronous procedure call (APC) injection. From within the memory space of trusted processes, Memery captures typed keystrokes, intercepts authentication tokens, extracts web browser session cookies, and beacons collected intelligence to cybercriminal infrastructure over encrypted C2 channels.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Memory-Resident Infostealer Architectures
Known Derivatives & Downstream Variants: Memery.A · Memery.Spy · Win32/Memery.Gen
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 |
|---|---|---|---|
T1055.012 | Process Injection: Process Hollowing | Defense Evasion | ATT&CK ↗ |
T1056.001 | Input Capture: Keylogging | Credential Access | ATT&CK ↗ |
T1555.003 | Credentials from Password Stores: Credentials from Web Browsers | Credential Access | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols | Command and Control | 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.
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
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-PHA | Process Hollowing Analysis | Detect | T1055.012 | Inspect unbacked executable memory regions (PAGE_EXECUTE_READWRITE) for replaced PE image headers inside legitimate host processes. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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. |
Exploited Vulnerabilities (CVEs)
This malware family is documented weaponizing the following common vulnerabilities and exposures:
- CVE-2012-0158 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
- CVE-2015-1641 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f
Delivery vectors
Spear-phishing emails containing malicious Office attachments exploiting CVE-2012-0158Watering hole compromise using drive-by script exploits exploiting CVE-2015-1641
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\MemeryAgentProcess injection into explorer.exe executing continuously across user sessions
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_MEMERY_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Memery"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "memery" ascii wide nocase
$s2 = "trojan:win32/memery" ascii wide nocase
$s3 = "backdoor:win32/memery" ascii wide nocase
$s4 = "trojan-spy.win32.memery" ascii wide nocase
$s5 = "win32/memery.trojan" ascii wide nocase
$s6 = "spyware.memery" 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 - Memery (Trojan) Execution & Triage
id: c734a3ff-96a5-5a2f-a225-e3593ed8b52b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Memery 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/memery
- 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.t1055_012
- attack.t1056_001
- attack.t1555_003
- attack.t1547_001
- attack.t1071_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: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_MEMERY_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Memery 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 = "memery" 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 endpoint from local networks to stop active memory-to-C2 credential exfiltration streams.
- Perform volatile physical memory acquisition before rebooting to preserve injected threads for forensic analysis.
- Terminate hollowed Windows processes exhibiting anomalous memory allocations and outbound network sockets.
- Revoke and re-issue all user account credentials, enterprise certificates, and web passwords used on the host.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not perform simple file deletion without addressing active memory injection, which can leave persistent resident hooks.
- Avoid rebooting without memory triage, as critical forensic artifacts reside solely in volatile RAM.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Trojan:Win32/Memery Details
- Trend Micro Threat Encyclopedia - Trojan.Win32.Memery
- NIST National Vulnerability Database - CVE-2015-1641
- Search "memery" on VirusTotal (External Analysis)
- Search "memery" on Any.Run (Sandbox Sandbox)
- Search "memery" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is the Memery trojan threat?
Memery is an evasive memory-resident trojan and spyware family that injects into legitimate Windows processes to harvest credentials.
How does Memery maintain stealth during execution?
It executes primarily within volatile RAM and injects code into legitimate processes like explorer.exe to evade disk-based scans.
What surveillance data does Memery harvest from endpoints?
Memery captures keystrokes, extracts stored browser passwords, intercepts session cookies, and collects system credentials.
Which CVE vulnerabilities have been linked to Memery campaigns?
Exploitation campaigns delivering Memery loaders have weaponized Office and document flaws including CVE-2012-0158 and CVE-2015-1641.
How can security analysts detect and remediate Memery?
Perform volatile physical memory triage, deploy behavioral EDR monitoring for process injection, and purge autostart Run keys.
How do I remove the Memery Trojan from Windows?
Manual removal of Memery 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.
Is Memery a virus or a Trojan?
Memery is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Memery typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Memery infection?
Symptoms of Memery 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 Memery 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/memery.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.