← Breach analysis by the Dual Vulnerabilities framework

Beloyarsk NPP hack-and-leak (GURMO claim, 2022)

2022 · Russia · D - Electricity, gas, steam and air conditioning supply · Hack-and-leak: data theft and publication of stolen documents

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Hack-and-leak: data theft and publication of stolen documents

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) The expectation one would normally assess at the victim - what security strategy, policies, network segregation or data-protection controls Rosenergoatom maintained for the Beloyarsk business network - is entirely undocumented: the plant, Rosenergoatom and Rosatom made no public statement about a cyber intrusion, and no Russian CERT (GosSOPKA), regulator or court document on this incident was found, including in Russian-language searches. (2) What the record contains is attacker-side impact only: cybersecurity writer Jeffrey Carr, who states he was working with two GURMO offensive cyber operators, wrote on 7 March 2022 that GURMO cyber operators had breached the plant's business network and exfiltrated a large amount of data including contracts, architectural diagrams, alarm system configurations and set-up instructions for control system parts, publishing samples to subscribers of his newsletter (his own account; the paid tier carried the downloadable documents). SC Media's analysis of 11 March 2022 - the dataset's attribution source - reports only that GURMO leaked documents it 'claimed it stole' and quotes Carr's characterisations, with no independent verification; Cybernews (16 March 2022) likewise relays Carr, noting the operators accessed only the business network, not the control systems. (3) The DV framework measures where the victim's own strategy or expertise failed to translate into execution; none of the six lifecycle stages yields a defensible victim-side mechanism: entry vector, dwell time, detection, containment, recovery and victim response are never described from the victim's side, and the exfiltration - the only gap-like signal - is an unverified attacker claim in an information operation whose stated purpose was to signal Russian vulnerability. The EuRepoC record itself concedes the basis: disclosure by a third-party actor, attribution via an anonymous media statement with basis 'Attacker confirms', and the row description notes the incident was exclusively reported by Carr. Independent analysis of this claim environment (Soesanto, RealClearDefense, March 2024) states that between February 2022 and November 2023 'no credible reports existed on GURMO's activities in cyberspace' and finds news outlets repackaging GURMO claims without due diligence. Per the decision rule (reporting confirms impact only; no defensible victim-side mechanism), the case is set to Unknown with no confidence score; the atypical, openly claimed state hack-and-leak nature is flagged in Notes.

Sources

Notes

One-sided source: the entire incident rests on Jeffrey Carr's Substack newsletter, written in close cooperation with GURMO (the case file itself notes Carr was working with two GURMO offensive cyber operators and publishes their stolen data to paid subscribers); EuRepoC attribution is 'Attacker confirms' via an anonymous statement in a media report. Searches in English and Russian (Белоярская АЭС хакеры утечка ГУР) found no Rosenergoatom/Rosatom statement, no Russian CERT advisory, no regulator or court document on this intrusion; every press item opened (SC Media, Cybernews, O'Reilly) traces back to Carr. Context on the reliability of GURMO cyber claims of this period: Soesanto (ETH Zurich CSS, RealClearDefense, 02-03-2024) finds no credible reporting on GURMO cyber activity existed between Feb 2022 and Nov 2023 and documents examples of false or exaggerated later self-attributions; this caps the evidentiary value of the breach claims but does not disprove them either way. Consistency: result-200 (JINR, Dubna), the same Carr/GURMO hack-and-leak series - Beloyarsk was its first piece per Carr's O'Reilly article, JINR the fifth, and Carr's Beloyarsk post announces the JINR breach as an upcoming article - was classified Unknown on the same evidentiary grounds (row-200 case file opened and checked). Security policy: no leaked documents from the newsletter were downloaded or opened and no leak sites were visited; the newsletter was read for its narrative only. Data quality: eurepoc_extra rates functional impact 'No system interference/disruption' and intelligence impact 'Minor data breach/exfiltration (no critical/sensitive information)', which sits awkwardly with the described architectural diagrams and alarm-system configurations; weighted_intensity 3; the case file's end_date 07.03.2022 is the disclosure date, not a confirmed end of intrusion. Sector: the plant generates electricity for the grid (SBI section D); victim named from the case file description. Country from eurepoc_extra.receiver_country (Russia); Year 2022 from start_date 01.01.2022 (disclosure 07.03.2022). Unattended run: no consent-gated actions were needed.