Fakesmoke
Table of Contents
Overview
Trojan:Win32/Fakesmoke is a form of **Rogue Security Software** (often called Fake AV or Scareware). It masquerades as a legitimate, high-end antivirus program, deliberately generating terrifying, fake security alerts to trick the user into paying for a 'premium' license to remove non-existent threats.
Understanding Fakesmoke
To an end-user, Fakesmoke is highly distressing. The desktop is bombarded with urgent, red-flashing pop-ups claiming the system is severely infected with zero-day trojans or that data is actively being stolen. For a security team, Fakesmoke relies entirely on social engineering and intimidation (`T1498.002` - modified context for deception) to monetize the infection directly from the victim.
Execution and Scareware Mechanics
Fakesmoke is often distributed via malvertising, drive-by downloads, or bundled with pirated software (`T1189`). Upon execution (`T1204.002`), it establishes persistence via the Registry (`T1547.001`) so it runs every time the computer boots. It immediately displays a highly professional-looking (but fake) scanning interface. It simulates a fast scan and inevitably reports dozens of severe infections. To enforce compliance, Fakesmoke actively attempts to disable legitimate Windows utilities (like Task Manager, Registry Editor, and Command Prompt) (`T1562.001`) and may block access to real security vendor websites to prevent the user from downloading actual removal tools.
Indicators of Compromise & Impact
The impact is primarily financial fraud and severe disruption of productivity. Host-based IoCs include EDR alerts for the unauthorized modification of registry keys disabling Task Manager (`HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableTaskMgr`), the presence of the rogue executable in the `%AppData%` folder (often with a randomly generated, innocent-sounding name), and persistent, aggressive pop-up windows demanding credit card payment.
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 |
|---|---|---|---|
T1562.001 | Impair Defenses: Disable or Modify Tools (Disabling Task Manager/AV) | Defense Evasion | ATT&CK ↗ |
T1498 | Network Denial of Service (Blocking access to security sites) | Impact | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution | Persistence | ATT&CK ↗ |
T1189 | Drive-by Compromise | Initial Access | ATT&CK ↗ |
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-TR | Traffic Rate Limiting | Isolate | T1498 | Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks. |
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-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_FAKESMOKE_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fakesmoke"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fakesmoke" 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 - Fakesmoke (Trojan) Execution & Triage
id: 4b4c1d45-e3db-5404-b3de-ecb27b18750b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fakesmoke 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/fakesmoke
- 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.t1562_001
- attack.t1498
- attack.t1547_001
- attack.t1189
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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_FAKESMOKE_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakesmoke 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 = "fakesmoke" 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 machine into 'Safe Mode with Networking' to prevent the Fakesmoke persistence mechanisms from launching and blocking remediation tools.
- Use the Registry Editor to manually re-enable Task Manager and Command Prompt if they were disabled by the malware.
- Run a full system scan using a known, trusted, enterprise-grade anti-malware solution to detect and remove the rogue executable.
- Educate the user on the deceptive tactics of rogue security software and instruct them to contact their credit card company if they made a payment.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not input any personal or financial information into the payment portals presented by the software.
- Avoid attempting to manually delete the Fakesmoke files in normal Windows mode, as the malware will actively defend itself and block deletion.
References & External Analysis
- Search "fakesmoke" on VirusTotal (External Analysis)
- Search "fakesmoke" on Any.Run (Sandbox Sandbox)
- Search "fakesmoke" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fakesmoke and what threat category does it belong to?
Fakesmoke is classified as a Trojan. 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 Fakesmoke establish persistence and evade defensive controls?
Fakesmoke 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 Fakesmoke compromise?
Security teams responding to Fakesmoke 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 secondary payloads and staging behaviors are commonly associated with Fakesmoke?
Fakesmoke frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Fakesmoke across enterprise endpoints?
Defenders should hunt for Fakesmoke by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove Fakesmoke from Windows?
Manual removal of Fakesmoke 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 Fakesmoke infection?
Symptoms of Fakesmoke 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 Fakesmoke 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/fakesmoke.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.