Fakecoder
Table of Contents
Overview
Trojan:Win32/Fakecoder is a classic but enduring social engineering lure designed to trick users into executing malware under the guise of a required media player update. Attackers set up malicious streaming sites or seed torrents with video files that prompt the user to download a 'special codec' or 'video player update' to view the content. The downloaded file is, in fact, a trojan dropper (`T1204.002`).
Understanding Fakecoder (Social Engineering Delivery)
To an end-user, they are simply trying to watch a pirated movie, a sports stream, or adult content, and believe the prompt to update their software is legitimate. For a security team, a Fakecoder detection highlights a failure in user awareness training and a reliance on risky browsing behavior, providing a direct path for attackers to bypass email filters and network perimeters.
Execution and Delivery Mechanics
The attack relies heavily on user interaction. The victim navigates to a compromised site. The site uses JavaScript to detect the browser and serve a fake, highly realistic prompt (e.g., 'Flash Player is out of date' or 'Missing DivX Codec'). The user downloads the executable (often named `setup.exe` or `codec_pack.exe`) and runs it (`T1204.002`). The executable may actually install a basic media player to avoid suspicion, but silently drops a RAT, Adware, or Ransomware payload in the background (`T1027.002`).
Indicators of Compromise & Impact
The impact depends on the secondary payload delivered by the fake codec. Host-based IoCs include the execution of unsigned executables from the `%Downloads%` folder immediately following web browsing activity to high-risk sites (streaming, torrents). EDR will flag the 'codec' installer spawning unexpected child processes (like `cmd.exe` or `powershell.exe`) to establish persistence or reach out to a C2 server.
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-EDA | Executable Deobfuscation Analysis | Detect | T1027.002 | Deploy static entropy scanners and dynamic memory-unpacking heuristics to identify obfuscated and packed PE structures. |
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-FEA | File Execution Analysis | Harden | T1204.002 | Enforce AppLocker and Windows Defender Application Control (WDAC) to block executable launches from temporary and user-writable directories. |
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_FAKECODER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fakecoder"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fakecoder" 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 - Fakecoder (Ransomware) Execution & Triage
id: 0c88a273-ee32-5385-a029-bbc287907d13
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fakecoder 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/fakecoder
- 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.t1027_002
- attack.t1204_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: critical
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_FAKECODER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakecoder 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 = "fakecoder" 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 machine; the fake codec was likely a dropper for a more severe payload (like an InfoStealer).
- Review web proxy logs for the infected host to identify the malicious streaming or download site, and block it enterprise-wide.
- Determine what the secondary payload was by analyzing the EDR process tree spawned by the downloaded executable.
- Conduct targeted security awareness training focusing on the dangers of pirated media and fake update prompts.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not close the incident just because the AV blocked the initial download; the user's risky browsing behavior needs to be addressed.
- Avoid allowing standard users to execute unapproved binaries from their `%Downloads%` folder (enforce AppLocker).
References & External Analysis
- Search "fakecoder" on VirusTotal (External Analysis)
- Search "fakecoder" on Any.Run (Sandbox Sandbox)
- Search "fakecoder" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fakecoder and what threat category does it belong to?
Fakecoder 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 Fakecoder establish persistence and evade defensive controls?
Fakecoder 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 Fakecoder compromise?
Security teams responding to Fakecoder 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 Fakecoder employ during execution?
Fakecoder 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 Fakecoder, and what is the recommended recovery procedure?
Decryption availability for Fakecoder 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 Fakecoder from Windows?
Manual removal of Fakecoder 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 Fakecoder infection?
Symptoms of Fakecoder 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 Fakecoder 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/fakecoder.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.