Killdisk

Category: wiper · Aliases: KillDisk, Wiper.KillDisk, Trojan.KillDisk, Sandworm Wiper, Win32/KillDisk · Sample count (EMBER 2018): 1 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: WiperStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Execution, Defense-Evasion, ImpactFirst seen: 2015Actor: Russian GRU Unit 74455 (Sandworm)Industry: energy, utilities, critical_infrastructure, government, transportationMotivation: Geopolitical Sabotage & Critical Infrastructure Destruction🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Trojan:Win32/KillDisk is a catastrophic industrial wiper malware family developed and deployed by Russian military intelligence hackers belonging to the Russian GRU Unit 74455 (known globally as Sandworm, TeleBots, and BlackEnergy Group).

Table of Contents

Overview

Trojan:Win32/KillDisk is a catastrophic industrial wiper malware family developed and deployed by Russian military intelligence hackers belonging to the Russian GRU Unit 74455 (known globally as Sandworm, TeleBots, and BlackEnergy Group). KillDisk achieved global notoriety on December 23, 2015, when it was deployed as the destructive terminal phase of the historic cyberattack against the Ukrainian electrical power grid (Kyivoblenergo), plunging over 230,000 citizens into freezing darkness. After operators remotely opened circuit breakers at substations, KillDisk was executed across master SCADA workstations, uninterruptible power supplies (UPS), and operator human-machine interfaces (HMIs). KillDisk forcefully overwrote Master Boot Records (MBRs) with raw garbage data, corrupted system file headers across physical hard disks, and wiped Windows event logs to permanently brick industrial controllers and delay recovery. In October 2020, the United States Department of Justice indicted six Russian GRU officers for the deployment of KillDisk, BlackEnergy, NotPetya, and Olympic Destroyer in federal court in the Western District of Pennsylvania.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Blackenergy

Known Derivatives & Downstream Variants: Killdisk Industrial Wiper (2015) · Killdisk Financial Ransomware-Wiper (2016) · Hermeticwiper (Lineage)

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

Tactical Mitigations

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

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-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-MFAMulti-factor AuthenticationHardenT1078.002Enforce mandatory phishing-resistant FIDO2 multi-factor authentication across all external access portals.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsTCP, HTTP
Observed ports443, 80
Identifiable from traffic aloneLow

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_KILLDISK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Killdisk"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "killdisk" ascii wide nocase
        $s2 = "killdisk" ascii wide nocase
        $s3 = "wiper.killdisk" ascii wide nocase
        $s4 = "trojan.killdisk" ascii wide nocase
        $s5 = "sandworm wiper" ascii wide nocase
        $s6 = "win32/killdisk" 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 - Killdisk (Wiper) Execution & Triage
id: 43c03822-da40-5d87-a408-79a8c5b47db9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Killdisk 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/killdisk
- https://malware-families-catalog.systemhelpdesk.com/defensive/wiper-destructive-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.wiper
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1561_002
- attack.t1561_001
- attack.t1070_001
- attack.t1490
- attack.t1059_003
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: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_KILLDISK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Killdisk 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 = "killdisk" 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. Physically disconnect industrial SCADA and OT network segments from corporate IT infrastructure.
  2. Enforce strict read-only access to physical disk handles and block raw disk I/O from unauthorized binaries.
  3. Maintain verified offline, air-gapped system disk images for industrial HMI and controller workstations.
  4. Apply security patches for Microsoft Office OLE vulnerability CVE-2014-4114.

What to Avoid

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

  1. Never interconnect industrial control systems (ICS/SCADA) directly with public-facing corporate IT networks.
  2. Avoid relying solely on software-level backups connected to the same active directory domain.
  3. Do not allow unsegmented lateral administrative access between corporate workstations and industrial HMIs.

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-054a ↗

Frequently Asked Questions

What is KillDisk malware?

KillDisk is a devastating cyber-weapon and disk wiper used by Russian GRU military hackers to permanently destroy operating systems and sabotage critical infrastructure.

How was KillDisk used in the Ukrainian electrical grid blackout?

In December 2015, Sandworm deployed KillDisk to overwrite SCADA server boot records and corrupt industrial workstations, blinding operators during the Kyivoblenergo blackout.

Who is responsible for the KillDisk cyberattacks?

The US Department of Justice unsealed criminal indictments attributing KillDisk, BlackEnergy, and NotPetya to six military intelligence officers of Russian GRU Unit 74455.

How does KillDisk destroy disk data?

KillDisk opens raw physical disk handles, overwriting the Master Boot Record (MBR), partition tables, and system system files with zeros or static garbage strings before forcing a crash.

What vulnerabilities were used in conjunction with KillDisk?

Sandworm deployed KillDisk following initial access via spear-phishing emails exploiting CVE-2014-4114 (OLE package exploit) and SMB lateral movement (CVE-2017-0144).

How do I remove the Killdisk Wiper from Windows?

Manual removal of Killdisk 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.

Is Killdisk a virus or a Wiper?

Killdisk is classified as a Wiper. Unlike traditional viruses that infect files, modern malware like Killdisk typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Killdisk infection?

Symptoms of Killdisk 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 Wipers

Want to prevent Killdisk and similar threats from compromising your organization? Read our comprehensive defensive guide: Wiper & Destructive Malware Protection.

📣 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 team.

Machine-readable

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