Faketool

Category: trojan · Aliases: Trojan:Win32/FakeTool, Rogue:Win32/FakeTool, PUA:Win32/FakeTool, Win32/FakeTool, Program:Win32/FakeTool · Sample count (EMBER 2018): 20 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Persistence, Defense EvasionActor: Scareware Syndicates & Rogue Antivirus AffiliatesIndustry: Consumer Endpoints, Small Business WorkstationsMotivation: Financial Fraud & Scareware Licensing Fees🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
FakeTool (cataloged under antimalware detections including Trojan:Win32/FakeTool, Rogue:Win32/FakeTool, and PUA:Win32/FakeTool) represents a pervasive family of rogue security software, fake antivirus tools, and scareware trojans.

Table of Contents

Overview

FakeTool (cataloged under antimalware detections including Trojan:Win32/FakeTool, Rogue:Win32/FakeTool, and PUA:Win32/FakeTool) represents a pervasive family of rogue security software, fake antivirus tools, and scareware trojans. Masquerading as legitimate system defense utilities, PC repair suites, or disk defragmentation software, FakeTool is distributed through drive-by downloads, compromised websites displaying fake infection alerts, and malicious software bundlers. Upon execution, FakeTool hijacks Windows display elements and executes fabricated system scans that report non-existent virus infections, registry errors, and severe hardware failure warnings. It aggressively blocks the execution of legitimate antimalware tools and Task Manager, while coercively prompting the victim to pay for an expensive commercial activation license.

Known aliases

Threat reports may refer to this family under multiple names:

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-RBIRemote Browser IsolationIsolateT1189Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints.
D3-WIMWeb Interface MonitoringDetectT1491.001Deploy automated file integrity monitoring (FIM) and continuous HTTP checksum verification across public web roots.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block 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_FAKETOOL_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Faketool"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "faketool" ascii wide nocase
        $s2 = "trojan:win32/faketool" ascii wide nocase
        $s3 = "rogue:win32/faketool" ascii wide nocase
        $s4 = "pua:win32/faketool" ascii wide nocase
        $s5 = "win32/faketool" ascii wide nocase
        $s6 = "program:win32/faketool" 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 - Faketool (Trojan) Execution & Triage
id: 9fa79d13-7bd7-5b5c-8f1e-7ded29b39c25
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Faketool 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/faketool
- 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.t1189
- attack.t1491_001
- attack.t1547_001
- attack.t1562_001
- attack.t1112
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: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_FAKETOOL_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Faketool 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 = "faketool" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Instruct the user not to input credit card numbers into the fake registration prompt.
  2. Reboot the infected machine into Safe Mode with Networking to bypass process-killing hooks.
  3. Terminate active FakeTool processes and remove startup keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Clean malicious DisallowRun registry values under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options.
  5. Run a reputable antimalware scanner to remove all leftover rogue files.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not purchase license keys from the fake software interface.
  2. Do not allow pop-up scan warnings on websites to prompt software installations.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/FakeTool?

FakeTool is a rogue security scareware trojan that displays fake virus warnings to coerce victims into buying fake licenses.

How does FakeTool impede system remediation?

It terminates or blocks legitimate antimalware programs and Task Manager, claiming they are infected.

How is FakeTool delivered to computers?

It is delivered through malicious drive-by downloads, fake online scanner alerts, and software bundlers.

Are the infections reported by FakeTool real?

No, all reported viruses and system errors are completely fabricated to induce panic and force payment.

How can FakeTool be eradicated from an infected system?

Boot into Windows Safe Mode, kill the rogue process, remove startup registry keys, and run a reputable antimalware scanner.

What are the main symptoms of a Faketool infection?

Symptoms of Faketool 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 Faketool 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.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/faketool.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.