Fakehack
Table of Contents
Overview
Program:Win32/Fakehack (or similar Rogue Security Software) is a type of Scareware or Potentially Unwanted Program (PUP) that uses social engineering to extort money from users. It intentionally displays highly alarming, fabricated warnings indicating the system is critically infected with viruses or is under active attack, and then coerces the user into purchasing a 'premium' license to resolve these non-existent threats (`T1566.002`).
Understanding Fakehack (Scareware)
To an end-user, the computer suddenly displays official-looking, flashing warnings (often mimicking the Windows Security Center interface) claiming the system is critically compromised. For a SOC analyst, Fakehack is a nuisance that generates support tickets and indicates a lapse in web filtering or user awareness, as it is almost always downloaded manually by a tricked user.
Execution and Deception Mechanics
Fakehack typically gains access via drive-by downloads (`T1189`), bundled software installers, or deceptive ads ('Your PC is infected, click here to scan'). Once installed, it establishes persistence (usually via Registry Run keys) so that it launches automatically. It then runs 'scans' that are designed to always find critical errors. It aggressively hooks into the browser to display pop-ups and may attempt to block legitimate security software or prevent the user from opening the Task Manager until they pay (`T1489`).
Indicators of Compromise & Impact
The impact is primarily financial fraud against the user and a severe degradation of the user experience. Host-based IoCs include the presence of the Fakehack application in `C:\Program Files` (often with a deceptive name like 'Antivirus Pro 2024'), an overwhelming number of pop-up windows, and modifications to the browser's default search engine. Network IoCs include connections to payment gateways associated with known rogue software vendors.
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 |
|---|---|---|---|
T1566.002 | Phishing: Spearphishing Link (Using fake alerts to drive installations) | Initial Access | ATT&CK ↗ |
T1489 | Service Stop (Sometimes attempting to disable legitimate AV to maintain the deception) | Impact | ATT&CK ↗ |
T1189 | Drive-by Compromise (The primary delivery vector) | Initial Access | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1566.002: Inspect email links for known malicious domains and use link-rewriting services for time-of-click analysis.
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-SPP | Service Protection Policies | Harden | T1489 | Configure strict DACLs on Windows Service Control Manager to prevent unauthorized termination of antivirus and backup services. |
D3-URLR | URL Rewriting & Time-of-Click Inspection | Filter | T1566.002 | Rewrite all external email links to force real-time URL reputation and DNS resolution at click time. |
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_FAKEHACK_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fakehack"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fakehack" 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 - Fakehack (Advanced Threat) Execution & Triage
id: ba4142c5-234e-5ed8-bea2-beccf51d41dd
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fakehack malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/fakehack
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_002
- attack.t1489
- attack.t1189
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_FAKEHACK_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakehack 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 = "fakehack" 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 machine into Safe Mode (this usually prevents the Fakehack software from loading its persistence mechanisms) and uninstall the rogue application.
- Reset the user's browser settings (home page, search engine, extensions) to their defaults.
- Run a full scan with a legitimate, enterprise-grade AV solution to ensure no actual malware was downloaded alongside the scareware.
- Educate the user on how to identify fake security alerts and avoid downloading unapproved software.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not instruct the user to 'just ignore' the pop-ups; the software must be forcefully removed to restore usability.
- Avoid assuming the machine is actually infected with the severe malware the scareware claims it found.
References & External Analysis
- Search "fakehack" on VirusTotal (External Analysis)
- Search "fakehack" on Any.Run (Sandbox Sandbox)
- Search "fakehack" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fakehack and what threat category does it belong to?
Fakehack is classified as a Advanced Threat. 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 Fakehack establish persistence and evade defensive controls?
Fakehack 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 Fakehack compromise?
Security teams responding to Fakehack 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 lateral movement and credential access tactics does Fakehack leverage in enterprise intrusions?
Fakehack frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Fakehack maintain covert communications and evade perimeter network monitoring?
Fakehack often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove Fakehack from Windows?
Manual removal of Fakehack 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 Fakehack infection?
Symptoms of Fakehack 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 Advanced_Threats
Want to prevent Fakehack and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 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/fakehack.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.