Recory
Table of Contents
Overview
Executive Summary
Recory is a deceptive malware family that operates primarily as "Scareware" or a Fake Antivirus (Fake AV) program, while occasionally exhibiting aggressive ransomware-like behaviors. Its core objective is financial extortion. It infiltrates a system, generates fabricated security alerts claiming the machine is heavily infected, and demands immediate payment (usually via credit card) for a "premium license" to remove the non-existent threats.Infection Vector and Technical Capabilities
Recory is most commonly distributed via aggressive "malvertising" campaigns (where malicious ads redirect users to pages claiming their PC is infected) or bundled within "free" software installers downloaded from untrustworthy sources. Once executed, Recory focuses entirely on psychological manipulation and system disruption:- Fabricated Scans and Alerts: The malware launches a highly realistic, but completely fake, graphical user interface mimicking legitimate antivirus software (e.g., Windows Defender). It performs a rapid "scan" and invariably reports dozens of critical infections, utilizing flashing red warnings and alarming sound effects.
- System Disruption (Ransomware Behavior): To force the user to pay, Recory actively disrupts normal system operations. It frequently terminates legitimate executable files (like Task Manager, Registry Editor, and real antivirus software), claiming they are "infected." Some aggressive variants will hide desktop icons and the taskbar, simulating a locked system.
- Extortion Portal: The malware constantly redirects the user's web browser to a payment portal controlled by the attackers, demanding a credit card payment to "activate" the fake antivirus and restore the system.
Threat Assessment
While Recory typically does not utilize strong encryption to lock files (like true ransomware), it causes massive operational disruption and severe psychological distress for the user. Furthermore, entering credit card information into the extortion portal immediately compromises that financial data, leading to secondary fraud.Remediation and Eradication
- Safe Mode Eradication: Because Recory actively terminates security tools, the infected endpoint must usually be booted into Windows Safe Mode. From Safe Mode, a reputable, enterprise-grade anti-malware solution can be run to detect and remove the Fake AV executables and repair the hijacked registry keys.
- Do Not Pay the Ransom: Under no circumstances should the user enter their credit card information. The software is fake, and payment will simply result in stolen financial data.
- System Restoration: In severe cases where the malware has heavily damaged the registry or hidden critical system files, restoring the machine from a known-good backup or utilizing Windows System Restore may be the most efficient path to recovery.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
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-SPP | Service Protection Policies | Harden | T1489 | Configure strict DACLs on Windows Service Control Manager to prevent unauthorized termination of antivirus and backup services. |
D3-WIM | Web Interface Monitoring | Detect | T1491.001 | Deploy automated file integrity monitoring (FIM) and continuous HTTP checksum verification across public web roots. |
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. |
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_RECORY_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Recory"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "recory" ascii wide nocase
$s2 = "fakeav.recory" ascii wide nocase
$s3 = "ransom.recory" ascii wide nocase
$s4 = "scareware.win32/recory" 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 - Recory (Ransomware) Execution & Triage
id: 45f8340c-f860-5ab7-854d-f09e7190cfa5
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Recory malware family. Detects volume shadow copy deletion, boot status
tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/recory
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1491_001
- attack.t1489
- attack.t1547_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \vssadmin.exe
- \wmic.exe
- \wbadmin.exe
- \bcdedit.exe
CommandLine|contains:
- delete shadows
- shadowcopy delete
- resize shadowstorage
- recoveryenabled no
- ignoreallfailures
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_RECORY_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Recory 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 = "recory" 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.
- Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Recory from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
- Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Recory symmetric encryption keys or uncompiled payload components may still reside in memory.
- Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Recory to inhibit recovery.
- Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
- Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Recory binary and related persistence hooks are eradicated.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Recory.
- Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
- Do not connect clean backup drives or external storage to the affected network until Recory eradication is completely verified.
References & External Analysis
- Search "recory" on VirusTotal (External Analysis)
- Search "recory" on Any.Run (Sandbox Sandbox)
- Search "recory" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Recory and what threat category does it belong to?
Recory is classified as a Ransomware. 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 Recory establish persistence and evade defensive controls?
Recory 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 Recory compromise?
Security teams responding to Recory 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 cryptographic algorithms and file targeting techniques does FakeAV.Recory employ during execution?
FakeAV.Recory typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for FakeAV.Recory, and what is the recommended recovery procedure?
Decryption availability for FakeAV.Recory depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove the Recory Ransomware from Windows?
Manual removal of Recory 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 Recory a virus or a Ransomware?
Recory is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Recory typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Recory infection?
Symptoms of Recory 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 Ransomwares
Want to prevent Recory and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.
📣 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/recory.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.