← Breach analysis by the Dual Vulnerabilities framework

Westinghouse credential theft espionage (Fancy Bear, 2014)

2014 · United States · D - Electricity, gas, steam and air conditioning supply · State-sponsored espionage via phishing-based credential theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

State-sponsored espionage via phishing-based credential theft

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 9/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) Westinghouse Electric Company, the US nuclear power developer whose plant designs underpin about half of the world's operating reactors and which had been supplying nuclear fuel to Ukraine since 2008 (the motive US prosecutors gave for the targeting), was expected to hold the baseline for an organisation of its criticality: authenticate and protect the accounts of its advanced-reactor-development staff so a captured password alone was not usable, filter and flag lookalike internal email, and notice a sustained phishing campaign against its staff. (2) In practice the GRU officers researched the company and its employees from 20 November 2014, registered the lookalike webmail domain webmail.westinqhousenuclear.com on 10 December 2014, and captured the login credentials of at least five employees through spearphishing email made to look like routine messages from the company's own Microsoft Exchange Server; the attackers verified the credentials against the real network and re-routed the victims so the theft went unnoticed, then returned in four further waves to employees' personal accounts, the last on 18 November 2015, with the indictment's counts resting on the obtained usernames and passwords for multiple employee accounts. Containment, egress and recovery show no documented gap, and Westinghouse denies its systems were ultimately infiltrated (its October 2018 statement: it found "no evidence that the phishing campaigns against employees to breach Westinghouse's systems were successful"), so the entry vector here is documented and load-bearing while the internal blast radius is not established. (3) The knowing-doing gap sits in the material column: the missing controls - lookalike-domain and spoofed-internal-email defence, MFA so stolen passwords alone were not authenticatable, stolen-credential and phishing-campaign monitoring over a twelve-month span - are standard remedies at the reach of security specialists, and no source documents a strategic artefact that existed but was not operationalised (Strategy to Execution) or a leadership decision that deferred, under-funded or accepted the gap (Strategy to Leadership / Expertise to Leadership); the chain therefore broke between expertise and execution. The classification rests on the entry stage (clearest evidence: its mechanism is documented in a court indictment); the detection gap (campaign undetected from December 2014 to November 2015) points to the same type and is contributing, not separately decisive. (4) RM22 (Expertise to Execution lens): the intrusion path ran entirely on captured password-only credentials for accounts whose authenticity the attackers could simply test against the live network, and the remedies that identity specialists hold for exactly this - MFA, credential monitoring, lookalike-domain blocking - show no evidence of having been blocked by a leadership decision or capability constraint, so the known remedy simply was not executed in operations (causal role: Enabling). RM34 (Expertise to Execution lens): a foreign intelligence service's credential-harvesting waves against company and personal accounts persisted roughly twelve months, four waves continuing after the first credential capture, without detection or interruption - monitoring and alert handling that should have surfaced repeated spoofed-domain targeting did not identify the activity in time, consistent with tooling and staffing not realised against a known threat rather than with a deferred strategic programme (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Source caveats: the row's source_url (justice.gov/opa/page/file/1098481/download, the October 2018 indictment in US v. Morenets et al.) is a scanned PDF without a text layer and could not be read directly; the same public indictment was read in full in the National Security Archive's text copy, which is cited instead, plus the DOJ's own press release for the same allegations. Provenance/scope: the EuRepoC description says Fancy Bear accessed the internal networks and stole sensitive data; the October 2018 indictment documents reconnaissance, spoofed-domain spearphishing and theft of login credentials for multiple WEC employee accounts (aggravated identity theft counts) and lists WEC among GRU targets of benefit to Russian interests, but does not detail internal network penetration or corporate-document theft at WEC, and Westinghouse publicly stated its systems were not ultimately infiltrated; the classification is built on the documented credential theft and year-long undetected campaign rather than on an unverified internal-network claim. The dataset's dates (10-12-2014 to 18-11-2015) match the indictment (fake domain registered 10 December 2014; last wave 18 November 2015). Westinghouse's 2018 statement that it maintains robust processes was not coded as RM44: it postdates the incident and the breach denial may be accurate as to system infiltration. Detection gaps (dwell/detection method) are undisclosed; the detection-stage reading is marked inference. The company disclosed nothing itself; disclosure came from US authorities via the indictment (source_disclosure: incident disclosed by authorities of victim state). Sector: Westinghouse designs reactors and supplies fuel, services and plant design rather than operating as a utility; mapped to section D following the dataset's own receiver_subcategory Energy (row 1436, BHI Energy, a Westinghouse subsidiary hit by Akira ransomware in 2023, is a different incident and is not a related row of this case file).