Case Library / Phishing / 2015 Ukraine Power Grid Attack (Sandworm/BlackEnergy)
Phishing Documented incident

2015 Ukraine Power Grid Attack (Sandworm/BlackEnergy)

An attack attributed to Russia's Sandworm Team used compromised credentials to remotely open substation breakers at three Ukrainian utilities and cut power to about 225,000 customers. Government investigators reported BlackEnergy infections but did not confirm the malware's role in acquiring the credentials.

Share:

Social Engineering Examples·5 sources

What happened

On December 23, 2015, attackers attributed to Russia's Sandworm Team remotely and manually operated circuit breakers at more than 50 substations across three Ukrainian regional electricity distributors. The operation cut power to approximately 225,000 customers for one to six hours across the affected areas, according to WIRED. Investigators reported a spear-phishing campaign and BlackEnergy infections, but government reporting did not confirm that the campaign or malware acquired the credentials used in the outage. The attackers also deployed reported anti-recovery measures including KillDisk, firmware corruption, UPS disconnects, and a telephone denial-of-service attack. CISA later updated its attribution to Russian state actors, and the 2020 US DOJ indictment named GRU Unit 74455 officers in allegations concerning the Ukraine grid attacks.

How it worked

SANS/E-ISAC describes a macro-enabled Office-document infection path. The related NCCIC/ICS-CERT alert reports a broader spear-phishing campaign delivering BlackEnergy variants, but explicitly says the connection between that campaign and the outage was unclear. Investigators determined that the attackers used compromised legitimate credentials to access local systems through VPN and other legitimate remote-access pathways, but the exact nature of credential harvesting remained unknown. Using those credentials, the attackers reached the ICS network and directly operated breakers. The outage was caused by this reported human interaction with SCADA/HMI systems, while the role of BlackEnergy in acquiring credentials remained unconfirmed. Reported anti-recovery actions included firmware changes, UPS disconnects, KillDisk, and a telephone denial-of-service flood.

The lure and the tell

The reported lures were weaponized Microsoft Excel and Word documents emailed to utility personnel and disguised as business correspondence. The related NCCIC/ICS-CERT alert described the broader spear-phishing campaign as using Office attachments with "generally popular topics," but expressly left its connection to the outage unclear. The technical tell was the Office macro-security prompt urging the recipient to click "Enable Content" or "Enable Editing."

Outcome

On December 23, 2015, coordinated attackers remotely and manually operated breakers at more than 50 substations across the three utilities within about 30 minutes of each other, cutting power to roughly 225,000 customers for one to six hours across the affected areas, according to WIRED. Reported KillDisk, firmware, UPS, and telephone denial-of-service actions complicated recovery. Utility staff restored power substantially through manual, on-site switching after remote control was lost. The supplied reporting does not quantify a financial loss.

Why it matters

This incident demonstrated that attackers could use compromised credentials and legitimate remote-access paths to reach control systems and manually operate breakers, while reported phishing and malware details remained partly uncertain in government reporting. It illustrates the importance of IT/OT segmentation, macro security for the reported campaign, VPN and remote-access hardening, monitoring, and manual fallback procedures.

Defenses

The cited CISA/ICS-CERT alert and SANS/E-ISAC report recommend or describe defenses including phishing awareness, disabling Office macros or blocking macros from internet-sourced documents, application controls, network segmentation and strict IT to ICS access controls, multi-factor authentication on VPN and remote-access paths, monitoring remote-administration tools, manual or offline fallback procedures, firmware integrity checks, and backup communications for call centers. These measures address reported attack paths and impacts but are not presented here as proven to have stopped this incident.

Sources
Cite this case

Social Engineering Examples. “2015 Ukraine Power Grid Attack (Sandworm/BlackEnergy)”. Accessed 3 November 2026. https://socialengineeringexamples.com/ukraine-power-grid-attack-2015

Attack Chain & Defense
1Reconnaissance
What happened

SANS/E-ISAC's Defense Use Case reported no observed reconnaissance before the companies were targeted, but inferred from the highly coordinated targeting and final attack plan that reconnaissance occurred at some point before the attack.

The control that would have stopped it

Publicly available ICS vendor/version listings and routine employee-level OSINT are very hard to eliminate at enterprise scale; the realistic control assumes an adversary already has this information and instead hardens what that access can reach, particularly the IT/ICS boundary addressed in Stage 6.

2Reported weaponization
What happened

SANS/E-ISAC described VBA macro droppers embedded in ordinary Microsoft Word and Excel files. The related government alert reported a broader spear-phishing campaign but did not establish its connection to the outage.

The control that would have stopped it

For the reported macro-based campaign, email filtering and disabling macro execution can reduce exposure, while the government's alert leaves the campaign's connection to the outage unclear.

3Reported delivery
What happened

The government alert described Office attachments emailed to utility employees, but did not establish that this campaign caused the outage.

The control that would have stopped it

Email and attachment filtering or sandboxing for internet-sourced Office documents, combined with employee phishing-awareness training, reduces exposure to the reported weaponized-document campaign.

4Reported infection path
What happened

A spear-phishing campaign used macro-enabled Office documents to deliver BlackEnergy variants. The companion NCCIC/ICS-CERT alert says the campaign's connection to the outage was unclear.

The control that would have stopped it

Disabling Office macros by default, restricting execution to trusted signed macros, and blocking macros in internet-sourced files addresses the reported macro-delivery path; the government alert did not confirm that path as the cause of the outage.

5Credential use and lateral movement
What happened

The attackers used compromised legitimate credentials, whose harvesting method remains unknown, to access local systems through legitimate remote-access pathways such as VPN; BlackEnergy's role in obtaining those credentials was suspected but unconfirmed.

The control that would have stopped it

Multi-factor authentication on VPN and remote-access paths, plus monitoring for anomalous credential use and lateral movement, addresses the use of compromised credentials. The method of credential harvesting remains unknown.

6Staging inside the ICS network
What happened

Using the stolen credentials over VPN, the attackers reached SCADA/HMI systems at each utility, learned each company's distinct control software, and, per SANS/E-ISAC's kill-chain analysis, developed and likely tested malicious firmware for serial-to-Ethernet field devices ahead of the operation.

The control that would have stopped it

Strict network segmentation between corporate IT and ICS/SCADA networks, with no shared credentials or unmonitored remote-access bridges between them, would have prevented stolen IT credentials from ever reaching SCADA/HMI systems in the first place.

7Coordinated attack execution
What happened

On December 23, 2015, multiple operators simultaneously used existing remote-administration tools (RDP, TeamViewer, rlogin) or ICS client software to manually open breakers at more than 50 substations across the three companies within about 30 minutes of each other, cutting power to roughly 225,000 customers; this direct manual manipulation of the control systems was the objective-completion step of the attack.

The control that would have stopped it

Monitoring and alerting on remote-administration-tool use (RDP/TeamViewer/rlogin) into ICS environments, combined with operator procedures to detect and immediately revoke unauthorized HMI sessions, plus rehearsed manual/offline fallback procedures for breaker operation, are the last practical defenses against direct manual manipulation of control systems.

8Anti-recovery and evidence destruction
What happened

In parallel, the attackers corrupted serial-to-Ethernet firmware, scheduled unauthorized UPS disconnects, deployed a modified KillDisk wiper to corrupt master boot records and delete logs, and ran a telephone denial-of-service flood against a utility call center, all intended to delay restoration and blind both operators and customers to the scope of the outage.

The control that would have stopped it

Firmware integrity checks and monitoring on serial-to-Ethernet field devices, offline and immutable backups of logs and system images, and out-of-band or backup communications for call centers would have preserved recovery capability and customer communication despite the wiper, firmware corruption, and telephony flood.

Quick Facts
Victim
Three Ukrainian regional electricity distribution companies
(oblenergos): Prykarpattyaoblenergo, Kyivoblenergo, and Chernivtsioblenergo
Location
Ivano-Frankivsk, Kyiv, and Chernivtsi regions, Ukraine
Date
Spear-phishing/intrusion campaign observed from as early as March 2015 through January 2016
; the coordinated blackout occurred December 23, 2015
Impact
No official dollar loss figure was disclosed by the Ukrainian utilities or US government.
BasisunquantifiedNo official dollar figure; impact is measured operationally in customers and hours
Impact is measured operationally: approximately 225,000 customers lost power for one to six hours across the affected areas, according to WIRED; affected oblenergos continued operating under constrained/manual conditions for months afterward because corrupted firmware on serial-to-Ethernet converters and wiped systems had to be replaced/rebuilt, and one utility's call center was also disabled by a telephone denial-of-service flood during the response.
Status
Documented incident
Case Type
Real-World Incident
Sector
Critical Infrastructure, Energy & Utilities
Threat Actor
nation-state
Explore more

Related Cases

Browse by what this case has in common with others in the library.