← Breach analysis by the Dual Vulnerabilities framework

FNS Tax-System Hack and Data Destruction (HUR/GUR, 2023)

2023 · Russia · O - Public administration and defence · State-backed hack with data destruction and nationwide disruption

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

State-backed hack with data destruction and nationwide disruption

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 4/6 stages, weight 18/60

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

Why this classification

(1) Expectation at the victim: a national tax authority running one centralised system over some 2,300 territorial offices is expected to keep outsourced hosting and backups recoverable independently of production, to contain a central-office compromise away from the regions, and above all to communicate accurately to citizens and businesses about the availability of its own services during an incident. (2) What happened: Ukraine's GUR claimed on 12 December 2023 to have broken into a 'well-protected key central server' of the FNS, moved on to more than 2,300 regional servers, and destroyed the configuration files, database and backups at the company hosting the FNS data bank, Office.ed-it.ru, paralysing central-regional communication and tax collection for days - all attacker claims, independently unverified and denied by Moscow (Kommersant reported the FNS denial that the attack had any impact). What independent reporting does document is the response stage: the FNS publicly stated that all services were normal and citizens' data safe, while its own contact centre acknowledged possible access problems and the agency refused to give a cause. (3) The classification rests on that response stage - the only stage documented by sources beyond the attacker's claims: the expectation sits in the organisation's own public statement (doctrinal) and the chain broke at the decision/communication level, since the official narrative was contradicted by the agency's own disclosure and no truthful incident communication followed. That is a Strategy to Leadership gap within the doctrinal column. The entry vector is not disclosed and not load-bearing; the containment, egress and recovery conditions are only claimed by the attacker and are recorded as such - if true, they would point to Strategy to Execution (isolated backups, governed concentration) as the strong second pattern. (4) RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged from the expectation of accurate public incident communication - the official denial of any impact was contradicted by the agency's own contact centre admitting access problems, and no proper notification followed (causal role: Constraining). RM31 (Strategy to Leadership lens): the claimed destruction of the entire database and its backups together at the hosting provider indicates that leadership continuity objectives were not backed by a realistic, isolated backup arrangement - rests solely on the GUR claim (causal role: Constraining). RM04 (Strategy to Leadership lens): the claimed dependence of the nationwide tax system on one central communication link and one hosting provider made a single compromise produce a country-wide outage, i.e. concentration risk in the service model was not governed - claim-based (causal role: Amplifying). RM30 (Strategy to Leadership lens): the claimed spread from one central server to 2,300 regional offices indicates containment and blast-radius reduction were not architectural priorities - claim-based (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Atypical state-on-state wartime case: the incident is disclosed only by the attacker (GUR), independently unverified, and denied by the victim (FNS statement to RIA Novosti via Meduza; Kommersant denial via Cybernews), so all mechanism details outside the response stage rest on attacker claims (source type speculation) and are flagged as such. The FNS contact centre's partial admission of access problems (Port Telegram channel, reported by Meduza) is the only victim-side disclosure. The dataset's source_url list also contains two articles about different GUR-claimed incidents (the Planeta research-centre wipe and the March 2024 Russian MoD claim); they were not used. No related_rows in the case file. Entry vector never disclosed; detection/dwell time undocumented; the secondary receiver Office.ed-it.ru (the hosting provider) is part of the incident but the victim as coded is the FNS.