Fakeransom
Table of Contents
Overview
Ransomware:Win32/Fakeransom (or 'Scareware') refers to malicious programs that mimic the behavior and appearance of actual ransomware to extort money, but lack the capability to actually encrypt the victim's files (`T1491`). They rely entirely on psychological manipulation and screen-locking techniques rather than cryptographic damage.
Understanding Fakeransom (Scareware)
To an end-user, Fakeransom is terrifying. A full-screen window appears, claiming their files have been encrypted by a notorious cartel (like WannaCry or Ryuk) or locked by the FBI/Interpol for 'illegal activity', demanding immediate payment in Bitcoin or gift cards. For an incident responder, discovering the infection is 'fake' is a massive relief, as data recovery is usually trivial and requires no decryption key.
Execution and Screen-Locking Mechanics
Fakeransom is often distributed via malvertising, drive-by downloads, or bundled with pirated software. Upon execution, it does not encrypt files. Instead, it employs Screen Locking techniques (`T1491.002`). It maximizes a borderless window, sets it to always be 'on top', and disables the Task Manager (`taskmgr.exe`), the Windows key, and Alt+Tab functionality via API hooking (`T1562.001`). This traps the average user on the extortion screen, convincing them that their machine is hopelessly compromised.
Indicators of Compromise & Impact
The impact is psychological distress and potential financial loss if the user pays the ransom. Data availability is only temporarily affected by the screen lock. Host-based IoCs include the presence of the full-screen extortion window, registry modifications disabling the Task Manager (`DisableTaskMgr=1`), and a persistent executable running from `%AppData%` or `%Temp%`. Network IoCs may include connections to the attacker's payment portal, but unlike real ransomware, there is no transmission of encryption keys.
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-RBI | Remote Browser Isolation | Isolate | T1189 | Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints. |
D3-WIM | Web Interface Monitoring | Detect | T1491.002 | Deploy automated file integrity monitoring (FIM) and continuous HTTP checksum verification across public web roots. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_FAKERANSOM_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fakeransom"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fakeransom" 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 - Fakeransom (Ransomware) Execution & Triage
id: a15c9685-75aa-5911-ab02-552db51f0c91
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fakeransom 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/fakeransom
- 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.t1562_001
- attack.t1491_002
- attack.t1189
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: criticalTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_FAKERANSOM_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakeransom 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 = "fakeransom" 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.
- Boot the infected computer into 'Safe Mode with Command Prompt' to bypass the screen-locking application.
- Use the command prompt to launch `regedit.exe` and remove the persistence mechanism (usually a Run key) and re-enable the Task Manager.
- Delete the Fakeransom executable from the file system.
- Run a comprehensive anti-malware scan to ensure no other, silent threats were dropped alongside the scareware.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Under no circumstances should the ransom be paid; the files are not encrypted, and payment only encourages further extortion.
- Avoid reinstalling the entire operating system, as this is usually unnecessary for non-encrypting scareware.
References & External Analysis
- Search "fakeransom" on VirusTotal (External Analysis)
- Search "fakeransom" on Any.Run (Sandbox Sandbox)
- Search "fakeransom" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fakeransom and what threat category does it belong to?
Fakeransom 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 Fakeransom establish persistence and evade defensive controls?
Fakeransom 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 Fakeransom compromise?
Security teams responding to Fakeransom 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 Fakeransom employ during execution?
Fakeransom 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 Fakeransom, and what is the recommended recovery procedure?
Decryption availability for Fakeransom 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 Fakeransom from Windows?
Manual removal of Fakeransom 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 Fakeransom infection?
Symptoms of Fakeransom 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 Fakeransom 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/fakeransom.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.