Fakesupport
Table of Contents
Overview
Adware/Trojan:Win32/Fakesupport is a classification encompassing malware and aggressive adware specifically designed to facilitate Technical Support Scams. Unlike pure ransomware, Fakesupport does not encrypt files; instead, it uses browser hijacking, full-screen overlays, and simulated 'Blue Screen of Death' (BSOD) images to convince the victim their computer is critically infected or locked by law enforcement (`T1491.001`). The goal is to coerce the victim into calling a fraudulent toll-free number provided on the screen.
Understanding Fakesupport (Tech Support Scams)
To a non-technical user, the infection is terrifying. The screen locks, loud alarms may play through the speakers, and legitimate-looking Microsoft or Apple logos warn of impending data loss. For security teams, this represents a highly effective social engineering attack (`T1566.002`). If the user calls the number, the scammers will use remote access tools (like TeamViewer or AnyDesk) to take control of the machine, 'prove' the infection using normal Windows logs, and extort hundreds of dollars for a fake 'lifetime support contract'.
Execution and Deception Mechanics
Fakesupport is often delivered via malvertising (malicious ads that redirect the browser) or bundled with deceptive software. Some variants are purely web-based (JavaScript loops that prevent closing the browser tab), while others are installed locally. Locally installed variants establish persistence (Registry Run keys) and utilize APIs to disable Task Manager and keyboard shortcuts (like Alt+F4) to prevent the user from closing the deceptive full-screen overlay (`T1562.001`).
Indicators of Compromise & Impact
The primary impact is financial loss via fraud and the potential installation of actual backdoors if the user grants the scammers remote access. Host-based IoCs include the presence of anomalous executables generating full-screen overlays and registry modifications explicitly disabling Task Manager (`DisableTaskMgr`). Network IoCs include connections to known malvertising redirectors or domains hosting the fake BSOD templates.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
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-WIM | Web Interface Monitoring | Detect | T1491.001 | 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. |
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_FAKESUPPORT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fakesupport"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fakesupport" 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 - Fakesupport (Ransomware) Execution & Triage
id: 41f5c7e7-dbca-5088-b43b-a12a3c193c36
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fakesupport 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/fakesupport
- 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_001
- attack.t1566_002
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_FAKESUPPORT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakesupport 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 = "fakesupport" 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.
- If the lock screen is active, reboot the machine into 'Safe Mode with Networking' to prevent the Fakesupport malware from launching.
- Run a full scan with a reputable Adware/Malware removal tool to strip out the persistent executables and restore Task Manager functionality.
- If the user called the number and granted remote access, assume the machine is fully compromised; a complete forensic wipe and OS reinstall is mandatory.
- Reset all passwords for accounts that may have been accessed while the scammers had remote control of the machine.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not call the phone number displayed on the screen under any circumstances.
- Do not assume the machine is clean just because the overlay was closed; if the scammers had remote access, they likely installed persistent backdoors.
References & External Analysis
- Search "fakesupport" on VirusTotal (External Analysis)
- Search "fakesupport" on Any.Run (Sandbox Sandbox)
- Search "fakesupport" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fakesupport and what threat category does it belong to?
Fakesupport 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 Fakesupport establish persistence and evade defensive controls?
Fakesupport 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 Fakesupport compromise?
Security teams responding to Fakesupport 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 Fakesupport employ during execution?
Fakesupport 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 Fakesupport, and what is the recommended recovery procedure?
Decryption availability for Fakesupport 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 Fakesupport from Windows?
Manual removal of Fakesupport 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 Fakesupport infection?
Symptoms of Fakesupport 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 Fakesupport 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/fakesupport.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.