Hackav

Overview

Trojan:Win32/Hackav is a specific classification for utility malware designed with a singular, critical purpose: to impair, terminate, or completely uninstall legitimate endpoint security software (Antivirus, EDR, and Windows Defender). Hackav tools are almost never used in isolation; they are deployed by attackers as a precursor step immediately before executing a highly destructive payload, most commonly ransomware, to ensure the encryption process goes uninterrupted (`T1562.001`).

Understanding Hackav (AV Killers)
To an end-user, Hackav is invisible, though they might briefly notice a Windows notification stating that their antivirus has been turned off. For a security operations center, the execution of Hackav is a 'Code Red' alarm. It means an attacker has achieved high-level administrative privileges and is actively clearing the way for a catastrophic attack.

Execution and Impairment Mechanics
Hackav requires administrative or SYSTEM privileges to function. Once deployed by an affiliate or initial access broker, it employs extremely aggressive techniques. It may use legitimate, signed drivers (Bring Your Own Vulnerable Driver - BYOVD) (`T1068`) to gain kernel-level access to forcefully terminate protected EDR processes. It modifies the Windows Registry (`HKLM\SOFTWARE\Policies\Microsoft\Windows Defender`) to permanently disable real-time protection. It may also attempt to uninstall security software using silent WMI commands or by stopping critical security services (`T1562.001`).

Indicators of Compromise & Impact
The primary impact is the complete loss of endpoint visibility and protection, invariably followed by a major secondary attack. Host-based IoCs include EDR alerts (often the final alert before the agent goes offline) indicating tampering, unexpected stopping of security services (e.g., `WinDefend`), and unauthorized registry modifications targeting AV policies. The presence of known vulnerable drivers (like `procexp.sys` or outdated hardware drivers) dropped in the `%Temp%` directory is a major warning sign.

MITRE ATT&CK Techniques

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

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_HACKAV {
    meta:
        description = "Detects Hackav (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "hackav" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

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

Containment & Response Steps

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

1. Isolate the endpoint IMMEDIATELY at the network switch level. If Hackav has run successfully, ransomware execution is likely imminent.
2. Investigate how the attacker gained the administrative privileges necessary to run the AV killer (e.g., compromised credentials, local privilege escalation).
3. Hunt across the environment for the specific Hackav executable or the vulnerable drivers it dropped, as the attacker may be preparing multiple machines.
4. Do not rely on the local AV for cleanup, as it has been compromised; use a standalone, bootable forensic tool or reinstall the OS.

What to Avoid

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

1. Do not assume it's a false positive if an endpoint suddenly stops reporting to the EDR console; treat it as a critical incident.
2. Avoid turning the machine off entirely if possible, as capturing a memory image is vital for analyzing the follow-on payload.

References & External Analysis

• Search "hackav" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Gendelfan
• Rubat
• Esendi
• Dyamar
• Kaseya

Machine-readable

Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/hackav.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.