← Breach analysis by the Dual Vulnerabilities framework

Ukrainian government institutions WhisperGate wiper attack (Cadet Blizzard, 2022)

2022 · Ukraine · O - Public administration and defence · Wiper malware (WhisperGate) with concurrent government website defacements

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Wiper malware (WhisperGate) with concurrent government website defacements

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 15/60

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

Why this classification

(1) The strategic expectation at the Ukrainian state institutions in this row is that privileged third-party access to the government web estate is governed: the commercial provider's administrator privileges over numerous state websites were an institutional, strategic-level arrangement, and supplier assurance is the doctrinal control that should keep such a trusted path from becoming an attack path. (2) In practice the path was never operationalised into controlled third-party operation: CERT-UA assessed the most probable vector as a supply-chain compromise (compromise of the provider) that used the existing trusted connections to disable the connected state systems, an assessment consistent with Microsoft's finding that Cadet Blizzard repeatedly attacked IT providers serving government bodies with a compromise-one-compromise-many technique and that the January 2022 compromise of government entities was at least partly due to access gained in a breach of such a provider; the destruction (MBR wipe plus file corruption) landed on dozens of systems at government, non-profit and IT organisations on 13-14 January 2022, and the incident came to light through the visible website defacement rather than the victims' own monitoring - Microsoft found the wiper and disclosed it on 15 January. The entry vector was never officially confirmed (CERT-UA also kept OctoberCMS and Log4j exploitation as alternatives), so no classification rests on a specific technical vector. (3) That is a Strategy to Execution gap rather than merely weak security or a leadership failure: the expectation about supplier access sat at the strategic/institutional level, nothing in the sources shows leaders were warned and deferred or under-funded a control, and what failed was the translation of the supplier-trust arrangement into a controlled, constrained operational architecture - formal trust without operational assurance. The classification rests on the entry stage; the detection stage (material origin, execution break) and the response stage (initial official statements minimising the incident while Microsoft's disclosure reported a larger scope, corrected as forensics progressed - a within-days correction that no marker covers, so it is not coded) are recorded as contributing. RM13 (Strategy to Execution lens): supplier-security requirements, contracts, due diligence and monitoring did not translate into controlled third-party operation - a single commercial provider with administrator privileges over numerous state websites was compromised and its trusted connections were used to reach the victim organisations (causal role: Enabling). RM04 (Strategy to Execution lens): architecture and operating-model choices created a single point of failure across the state web estate - one compromised supplier account was enough to deface dozens of government websites and deliver destructive malware to dozens of systems at multiple agencies at once, materially amplifying the impact (causal role: Amplifying). RM34 (Strategy to Execution lens): monitoring and alert-handling requirements were not implemented or operated as intended across the affected agencies - a multi-stage, pre-planned attack was noticed only when the defacement became publicly visible and the destructive malware was identified by an external vendor, leaving the pre-staging undetected (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row without receiver_name; victim named descriptively from the description and the US indictment's named entities (diffuse multi-organisation campaign, sector coded for the primary victim group, state institutions). The entry vector was never officially confirmed: CERT-UA (26-01-2022) named supply-chain compromise as most probable and kept OctoberCMS (CVE-2021-32648) and Log4j exploitation as alternatives; the classification therefore rests on the documented trust-boundary condition, not on a specific CVE. Data-quality caveat: the row codes data_theft none / intelligence_impact no exfiltration, but the 05-09-2024 US superseding indictment (D. Maryland) alleges the conspirators exfiltrated personal data (criminal records, patient health data, data attributed to 13.5 million Diia users) and listed it for sale within hours of the attack; had that been coded, the egress stage would carry a gap - the row is classified as described, with the discrepancy flagged for the researchers. The dataset's start_date 10.01.2022 reflects the malware's compile/test dates; the destructive phase ran 13-14 January 2022. Attribution: Microsoft (DEV-0586, 15-01-2022; Cadet Blizzard, 14-06-2023), US DOJ indictments of 26-06-2024 and 05-09-2024 (GRU Unit 29155, US court, per case file legal_response/attribution fields). Unattended run: no consent-gated actions were needed or taken (no forms, logins or uploads; no leak sites or attacker infrastructure consulted).