← Breach analysis by the Dual Vulnerabilities framework

Russian Arbitration Courts Website Defacement (Unattributed, 2022)

2022 · Russia · O - Public administration and defence · Website defacement with temporary nationwide outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Website defacement with temporary nationwide outage

Dual vulnerability type

Strategy to Execution

Evidence coverage: 1/6 stages, weight 6/60

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

Why this classification

(1) The arbitration court system of the Russian Federation runs the public web presence of courts in every region; the strategic expectation for a judicial body is that these public services remain available and that trouble at one court does not spread to the others, and in March 2022 it was operating amid an openly declared hacktivist campaign against Russian state websites. (2) On the morning of 16 March 2022 intruders replaced the courts' front pages with anti-war messages and the sites then stopped loading. Because every arbitration court website ran on a single shared platform hosted in Moscow - the explanation the Primorsky Territory Arbitration Court press secretary gave the press - one intrusion cascaded to all sites nationwide, while courts of general jurisdiction, on a different platform, stayed reachable. The entry vector was never disclosed, nothing was reported as data loss, the online filing cabinet kept working, and access was restored within the day. (3) The classification rests on the containment stage: the architectural and operating-model decision to consolidate the web presence of all regional courts on one platform left no isolation between their sites, so a low-intensity homepage defacement produced a nationwide outage of the judiciary's public services. That is a doctrinal-intent-versus-material-architecture gap - the centralisation was built, but the separation continuity would demand was never realised in it - rather than merely weak security; a missing-control reading is avoided because the concentration itself, documented by the victim's own spokespeople, is the gap. The entry vector is unknown and not load-bearing, and detection, egress, recovery and response show no documented gap. (4) RM04 (Strategy to Execution lens): the architecture and operating model created a single point of failure across the courts' public services - all regional arbitration court websites depended on one Moscow-hosted platform, so one compromise forced a countrywide outage, materially amplifying the impact of a defacement (causal role: Amplifying). RM30 (Strategy to Execution lens): isolation requirements were not implemented in the shared platform's architecture, so containment capability was materially insufficient - the blast radius of a front-page defacement extended to every arbitration court site in the country while the separate general-jurisdiction platform proved the alternative design was feasible (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Attribution is media-based and anonymous: Izvestia says only that the attack was carried out from Ukraine according to some reports, and RFE/RL states no group claimed responsibility; the actor is not a claim the DV rests on. Incident disclosed by media - the courts issued no official statement beyond press-spokesperson comments quoted by RIA Novosti, Interfax and RBC. Only one lifecycle stage (containment) carries a documented gap and its origin/break answers are the coder's reading of secondary reporting, so the stage is recorded as inference; entry vector undisclosed. The October 2024 BO Team attack on the same arbitr.ru/sudrf.ru court infrastructure is a separate incident and was not used as evidence for this row. Case-file description matches the stated victim (judiciary, arbitration courts); no data-quality mismatch found. Unattended run: no step required consent, nothing skipped.