Fakecoder

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 the MITRE ATT&CK framework:

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_FAKECODER {
    meta:
        description = "Detects Fakecoder (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "fakecoder" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Fakecoder Activity
id: b7b85ec2b1b68ca91261f24265b224a0
status: experimental
description: Detects generic indicators of the fakecoder malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*fakecoder*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Isolate the machine; the fake codec was likely a dropper for a more severe payload (like an InfoStealer).
2. Review web proxy logs for the infected host to identify the malicious streaming or download site, and block it enterprise-wide.
3. Determine what the secondary payload was by analyzing the EDR process tree spawned by the downloaded executable.
4. 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.

1. Do not close the incident just because the AV blocked the initial download; the user's risky browsing behavior needs to be addressed.
2. Avoid allowing standard users to execute unapproved binaries from their `%Downloads%` folder (enforce AppLocker).

References & External Analysis

• Search "fakecoder" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Archsms
• Trialkiller
• Mutant
• Gendal
• Plasma

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/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.