Skip to content

Attack encyclopedia

BlackEnergy - the malware that switched off the lights in Ukraine

BlackEnergy (S0089) and the 23 December 2015 attack on Ukraine power grid - the first confirmed cyber-induced blackout. Sandworm, KillDisk, campaign C0028 and lessons for OT security.

Józef SulwińskiJózef Sulwiński

Published 7 min read

BlackEnergyKillDiskS0089SandwormICSSCADAOT securityMITRE ATT&CKenergy sector
Contents
  1. Context - from DDoS botnet to a weapon against the power grid
  2. Attack timeline
  3. Anatomy of the attack - BlackEnergy opened the door, a human was at the keyboard
  4. MITRE ATT&CK - technique mapping (campaign C0028)
  5. Attribution and significance
  6. Lessons for OT security
  7. Summary
  8. Sources

Ivano-Frankivsk, 23 December 2015, early afternoon. A duty operator at the Prykarpattyaoblenergo distribution utility is sitting at the dispatch console when the cursor on his screen starts to move on its own. Without his input it glides across the network diagram, opens the control dialog for one of the circuit breakers and issues a disconnect command. He grabs the mouse and tries to take back control - in vain. Moments later he is logged out of the system, and his password no longer works. Over the next few minutes substations go dark, one after another. That afternoon roughly 230,000 people across three Ukrainian regions lose power.

It was the first confirmed blackout in history caused by a cyberattack. And the tool that opened the door to the network was BlackEnergy.

Context - from DDoS botnet to a weapon against the power grid

BlackEnergy was not built to attack power plants. Its first version appeared around 2007 as a simple toolkit for building botnets and running DDoS attacks, sold on Russian-language criminal forums. The second generation, developed from around 2010, was something far more serious - a modular platform with a plugin architecture and a kernel-level rootkit. An operator could bolt on additional modules: for data theft, network traffic capture, disk destruction.

The third generation, BlackEnergy 3, emerged around 2014 and became the signature of the Sandworm group. The rootkit was dropped in favour of a lighter, stealthier design. In 2014 the attackers exploited the CVE-2014-4114 vulnerability (dubbed “Sandworm” by researchers) in the OLE mechanism of Microsoft Office to deliver BlackEnergy to government institutions and energy companies in Ukraine and across NATO states. Ukraine became the proving ground where successive stages of the operation were tested.

Attack timeline

Date Event
May 2014 First spear-phishing campaigns against Ukrainian energy utilities - Microsoft Office documents with macros
Spring 2015 A Prykarpattyaoblenergo employee opens an Excel attachment; BlackEnergy 3 is triggered
Summer-autumn 2015 Months of reconnaissance: lateral movement, mapping the environment, theft of VPN credentials
23 December 2015, approx. 15:30 Attackers hijack operator workstations and manually open breakers at around 30 substations
In parallel KillDisk launched, converter firmware overwritten, TDoS attack on call centres, UPS systems manipulated
Evening of 23 December Power restored manually - operators switch to local control

Anatomy of the attack - BlackEnergy opened the door, a human was at the keyboard

The crucial point is understanding what BlackEnergy was, and what it was not. The malware did not open the breakers. BlackEnergy 3 served as an access and reconnaissance tool: it gave the attackers a foothold in the utilities’ IT networks, let them move between hosts and steal credentials. The actual power cut was a hands-on-keyboard operation, carried out live by Sandworm operators.

Using stolen credentials, the attackers connected to the OT networks over remote-access channels and hijacked SCADA operator sessions. From the system’s perspective it looked like the work of an authorised dispatcher: someone was clicking through the HMI and issuing breaker-open commands. Except that someone was not an employee of the utility.

The attack did not stop at cutting power. Sandworm made sure that restoring it would be as hard as possible:

  • KillDisk (catalogued in MITRE as S0607) overwrote selected files and destroyed the Master Boot Record (MBR), rendering workstations and servers inoperable, including SCADA machines.
  • Firmware overwrites on the serial-to-Ethernet converters at substations stripped dispatchers of the ability to remotely control field devices. Some hardware had to be replaced afterwards.
  • A TDoS attack (the telephone equivalent of DoS) flooded the utilities’ call centres with thousands of automated calls, so customers could not report the outage and the operators’ situational picture was degraded.
  • UPS manipulation cut backup power to parts of the server rooms and control centres exactly when it was needed most.

This was an attack designed as a whole: one phase removed control, the other made regaining it harder.

MITRE ATT&CK - technique mapping (campaign C0028)

The 2015 attack is catalogued in the ICS matrix as campaign C0028 - 2015 Ukraine Electric Power Attack, and the malware itself as BlackEnergy S0089. The key techniques:

Technique ID BlackEnergy / 2015 context
Spearphishing Attachment T0865 Office documents with macros delivered to energy-sector staff
Remote Services T0886 Hijacking remote sessions to SCADA operator workstations
Valid Accounts T0859 Stolen VPN and domain credentials
Graphical User Interface T0823 Manually clicking through the HMI to open breakers
Manipulation of Control T0831 Opening breakers and disconnecting substations
Denial of Service T0814 TDoS attack on call centres, UPS power manipulation
System Firmware T0857 Overwriting the firmware of serial-to-Ethernet converters
Data Destruction T0809 KillDisk - wiping files and destroying the MBR
Loss of View T0829 Loss of visibility into grid state after SCADA was disabled

More about the framework and its use in OT threat analysis - in our MITRE ATT&CK guide.

Attribution and significance

The attack is attributed to the Sandworm group (G0034), a unit of Russia’s military intelligence service GRU (Unit 74455). In October 2020 the U.S. Department of Justice indicted six officers of that unit, naming the BlackEnergy campaign explicitly alongside NotPetya and Olympic Destroyer.

The significance of December 2015 is hard to overstate. For the first time, a cyberattack produced a physical outcome in the form of a power outage affecting hundreds of thousands of customers. It also demonstrated a model that Industroyer would extend a year later: in 2015 the attackers opened breakers by hand; in 2016 fully automated malware did it for them. BlackEnergy was the proof of concept. Industroyer was the production run.

Lessons for OT security

1. The IT/OT boundary is the most common route into control systems

The attack began with ordinary phishing in an office network. From there, step by step, the attackers reached the control environment. The OT network was not attacked directly - it was reached through IT.

TIP

Define zones and conduits in line with IEC 62443 and monitor traffic at the IT/OT boundary. Apply OT network segmentation so that compromising an office workstation does not automatically grant access to the dispatch room.

2. Remote access to the HMI demands strong controls

The attackers did not break an industrial protocol. They logged in like operators, using stolen credentials and remote-access channels.

TIP

Enforce multi-factor authentication and jump hosts for every connection into the OT environment. Restrict and log VNC/RDP sessions to SCADA workstations, and keep service accounts under separate control.

3. Field-device integrity matters

Overwriting the converter firmware is what most prolonged the return to normal. What was destroyed was not data but the ability to control remotely.

TIP

Maintain an ICS asset inventory that includes firmware versions and a recovery plan. Keep configuration backups and images of edge devices so that replacing or reprogramming them takes hours, not weeks.

4. Manual fallback procedures save the day

The fact that the Ukrainians restored power the same day came down to one thing: operators were able to switch substations to local control and run them by hand. For months afterwards, many utilities operated in manual mode.

TIP

Regularly test procedures for working without the SCADA system. Make sure staff can operate a substation locally, and that such drills are part of the incident response plan.

Summary

BlackEnergy was not the most sophisticated malware of its time. Its strength lay elsewhere: in pairing a simple access tool with a patient, hands-on operation aimed at a specific target. The attack of 23 December 2015 proved that a cyberattack can switch off the lights across an entire region - and that a state actor is willing to do it.

For critical-infrastructure operators the lesson is simple: OT security does not begin in the dispatch room. It begins with the first email opened on an office network, and it ends with the procedure that lets you run a substation without a single working computer.

Sources

  1. MITRE ATT&CK - BlackEnergy S0089
  2. MITRE ATT&CK - 2015 Ukraine Electric Power Attack C0028
  3. MITRE ATT&CK - KillDisk S0607
  4. ESET WeLiveSecurity - BlackEnergy trojan strikes again: Attacks Ukrainian electric power industry
  5. SANS / E-ISAC - Analysis of the Cyber Attack on the Ukrainian Power Grid
  6. CISA - Cyber-Attack Against Ukrainian Critical Infrastructure (IR-ALERT-H-16-056-01)
  7. Wikipedia - 2015 Ukraine power grid hack

Need help in this area?

Our experts will help you assess the risk and plan next steps.

Talk to an expert

We'll discuss scope, methodology, and timeline.

Book a call