← Breach analysis by the Dual Vulnerabilities framework

SPIEF DDoS attack (IT Army of Ukraine, 2022)

2022 · Russia · O - Public administration and defence · DDoS attack disrupting accreditation and admission systems

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS attack disrupting accreditation and admission systems

Dual vulnerability type

Expertise to Execution

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

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

Why this classification

(1) The St. Petersburg Economic Forum (SPIEF, run by the state-linked Roscongress Foundation under the Russian government) is Russia's showcase state economic event, operating in mid-2022 amid the openly acknowledged cyber conflict with Ukraine; the expectation on its accreditation system, participant database and badge admission infrastructure - on which access to the presidential plenary depended - was to stay available under attack. (2) In the victim's own account (Peskov via Interfax), massed DDoS attacks from 16 June were held off through the night, but on 17 June intensified attacks knocked the participant database and badge admission system out of action, blocking badge pickup and plenary access; the session moved an hour and the president's speech started about 100 minutes after its scheduled time (Dark Reading citing Reuters), in fact at 15:40 against an announced 15:00 (Gordonua). (3) The classification rests on the entry/availability stage: the victim's account shows the technical defence existed and was operating - expertise was present - yet it did not translate into capacity and architecture that kept the services up, so the break is in execution, not leadership: no source shows leadership deferring, under-resourcing or accepting the protection gap, and no strategic artefact failure is documented; the origin and break are inferred from the official timeline, which caps confidence. There is no separate entry vector question - this was volumetric flooding of public services, not an intrusion - and containment, egress, recovery and response show no victim-side gap. (4) RM32 (Expertise to Execution lens): the specialist defenders could not scale or protect the forum's public services - after holding the first wave overnight, the accreditation and badge admission systems fell to the intensified attack because the availability protection was not matched to the required capacity (causal role: Enabling). RM04 (Expertise to Execution lens): badge admission, participant-database verification and plenary access all hung on the single accreditation system, so when it went down physical access to the flagship session stalled and the head of state's speech was delayed; the dependency could not be reduced under time pressure (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Description matches the stated victim (no data-quality issue); no related_rows. The case file's Reuters and tvpworld links could not be opened (HTTP 403 / redirect error) and the Telegram channel links (t.me/itarmyofukraine2022/437 and /442) render no readable text through the public preview, so the attacker's call and claim are recorded only as reported by legitimate press (The Record interview; the Ukrainian Ministry of Digital Transformation statement via Gordonua). Peskov confirmed the attack but attributed it to no actor (case file; Dark Reading). The victim-side lifecycle rests on a single official account (Peskov via Interfax); there is no independent technical reporting on the SPIEF infrastructure or its DDoS-protection arrangements. Pure disruption incident: no data breach or exfiltration, recovery within 24h. No research requiring consent was needed or performed in this unattended run.