Hacdef

Overview

Rootkit:Win32/Hacdef (Hacker Defender) is a legendary, historically significant user-mode rootkit. Wide-spread in the mid-2000s, Hacdef was one of the first sophisticated, widely available tools designed specifically to hide the presence of an attacker, their files, and their backdoor connections from the system administrator and early antivirus software (`T1014`).

Understanding Hacdef (User-Mode Rootkits)
To an end-user or system administrator relying on standard Windows tools (like Task Manager or `netstat`), the system appears entirely normal. Hacdef intercepts the API calls made by these tools and actively filters the results. For example, if an attacker drops a file named `evil.exe`, Hacdef ensures that when Explorer asks for a list of files, `evil.exe` is removed from the list before it reaches the screen.

Execution and Hooking Mechanics
Hacdef is deployed *after* an attacker has achieved administrative access. It is a user-mode rootkit, meaning it does not typically load a kernel driver (`.sys`). Instead, it uses API Hooking (`T1056.004`), specifically injecting itself into all running processes and intercepting calls to fundamental Windows APIs (like `FindNextFile`, `EnumProcesses`, `RegEnumKey`). It uses an `.ini` configuration file that tells it exactly which file names, process names, registry keys, and network ports to hide from the OS.

Indicators of Compromise & Impact
The impact is total loss of system integrity and a deeply hidden attacker presence. Because Hacdef hooks user-mode APIs, host-based IoCs are difficult to find with standard tools. Advanced EDR tools detect Hacdef by identifying the inline hooks placed on the API functions in memory. Another classic detection method is cross-view validation (comparing the output of a clean, low-level disk read against the output of the hooked Windows API). Network IoCs involve looking for the hidden backdoors Hacdef is protecting.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1056.004: Monitor for unauthorized keylogging, screen capturing, or web browser API hooking. Deploy EDR to detect API hooking.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_HACDEF {
    meta:
        description = "Detects Hacdef (backdoor)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "hacdef" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Hacdef Activity
id: 103f1be6c3b656812d23b922e064409b
status: experimental
description: Detects generic indicators of the hacdef malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*hacdef*"
    condition: selection
level: medium

Containment & Response Steps

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

1. Do not attempt to clean a system infected with a rootkit using standard tools; the rootkit controls what those tools see.
2. Boot the system from a clean, read-only environment (like an offline AV rescue disk or a Linux Live CD) to inspect the hard drive without the rootkit's interference.
3. Analyze the `hxdef.ini` (or similarly named configuration file) to determine exactly what the attacker was hiding (e.g., hidden backdoor ports or dropped executables).
4. The safest remediation for a confirmed rootkit infection is a complete wipe and reimage of the system from known-good media.

What to Avoid

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

1. Avoid relying on `netstat` or Task Manager to investigate a suspected Hacdef infection; they are actively lying to you.
2. Do not connect the infected machine back to the network until it has been completely wiped, as the attacker has persistent, hidden access.

References & External Analysis

• Search "hacdef" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: backdoor)

Explore other malware families in the same category:

• Mydoom
• Meterpreter
• Chopper
• Darkhotel
• Hawkeyekeylogger

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/hacdef.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.