Fakedos

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Deceptive UI: The program may present a graphical user interface (GUI) allowing the user to enter a target IP address to "attack." When initiated, it simulates an attack, often displaying fake console outputs to maintain the illusion of functionality.
• Covert Payload Execution: While the fake UI is running, the core malware silently executes in the background. It establishes persistence by modifying the Windows Registry (`HKCU\Software\Microsoft\Windows\CurrentVersion\Run`) to ensure it survives system reboots.
• Botnet Assimilation: FakeDoS typically connects to a hardcoded command-and-control (C2) server. Instead of the user controlling the attacks, their machine is assimilated into a botnet. The C2 server can now command the infected host to launch actual DDoS attacks (e.g., UDP floods, SYN floods) or download secondary payloads like info-stealers.

Threat Assessment

Remediation and Eradication

• Network Monitoring: Analyze edge firewall logs for sustained, high-volume outbound traffic to unknown IP addresses or anomalous communication over non-standard ports, which indicates the machine is participating in a botnet attack.
• Endpoint Isolation: Isolate the infected endpoint from the LAN immediately to halt any outbound attacks and sever the C2 connection.
• Security Awareness Training: The presence of FakeDoS indicates a user intentionally attempted to download and execute malicious hacking tools. This requires immediate administrative review and targeted security awareness training regarding acceptable use policies.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.FakeDoS
• HackTool.FakeDoS
• Win32/FakeDoS

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:

• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.

MITRE D3FEND™ Defensive Countermeasures

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

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:

rule MALWARE_WIN_FAKEDOS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Fakedos"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "fakedos" ascii wide nocase
        $s2 = "trojan.fakedos" ascii wide nocase
        $s3 = "hacktool.fakedos" ascii wide nocase
        $s4 = "win32/fakedos" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Fakedos (Trojan) Execution & Triage
id: 563a5055-1ef4-5f8c-ad50-614d6873f341
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Fakedos 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/fakedos
- 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.t1059
- attack.t1547_001
- attack.t1583_003
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

rule MALWARE_WIN_FAKEDOS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fakedos 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 = "fakedos" 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.

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Fakedos from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Fakedos into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Fakedos persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Fakedos execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Fakedos dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Fakedos until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Search "fakedos" on VirusTotal (External Analysis)
• Search "fakedos" on Any.Run (Sandbox Sandbox)
• Search "fakedos" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Smshoax
• Gootkit
• Redirected
• Candyopen
• Zamg
• Shelma
• Informer
• Xrat

Machine-readable

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