← Breach analysis by the Dual Vulnerabilities framework

AKADO Telekom DDoS disruption (IT Army of Ukraine, 2023)

2023 · Russia · J - Information and communication · DDoS attack causing multi-day internet service outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS attack causing multi-day internet service outage

Dual vulnerability type

Expertise to Execution

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

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

Why this classification

(1) AKADO Telekom is a major Moscow-region operator whose customers include the Kremlin administration, the FSB, the FSO, Moscow city bodies and Sberbank, and its own news page advertised a fully automated cloud DDoS-protection service preventing practically all modern DDoS attack types: the expectation that its own availability would hold under volunteer-scale floods was carried by the company's own technical expertise, and that remedy sat with its specialists (material origin). (2) In practice the provider was reported down three times in under a month (30 December 2023, 4 January and 21-24 January 2024, the last outage about three days long), customers mass-complained and could not reach its support line, and GURMO reported the work of dependent state institutions significantly complicated or impossible; the victim itself said nothing publicly and disclosure came entirely from an adversarial state's intelligence service and the claiming group. (3) That is a knowing-doing gap inside the material column: the remedy (DDoS mitigation capacity) was not exotic or unknown to the victim - it sells it - yet it was not executed on the victim's own infrastructure, and the recurrence after two earlier takedowns shows the known remedy was not implemented or validated after earlier events. The classification rests on the recovery/availability stage; the entry vector (volumetric DDoS) is the attacker's claim and is not load-bearing, and every other lifecycle stage is undocumented or not in play. The gap's break (operations did not realise the known protection) is inferred from impact plus the company's own product disclosures - no source describes AKADO's internal state - which is why confidence is capped. (4) RM32 (Expertise to Execution lens): AKADO's own experts could not scale or protect the service under attack - a provider that builds DDoS mitigation as a product suffered repeated multi-day availability failures from volunteer-scale floods, showing its own architecture and capacity did not realise the protection it sells (causal role: Enabling). RM21 (Expertise to Execution lens): after the 30 December and 4 January takedowns, the same availability weakness recurred on 22 January without any documented remediation, so known technical remedies were not implemented or validated after earlier events (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

All incident reporting is external: GURMO (Ukrainian military intelligence) and the claiming IT Army of Ukraine; AKADO itself made no public statement and no Russian official source was found, so the mechanism is inferred from documented impact plus the victim's own archived product disclosures. The three-takedown recurrence (30 Dec, 4 Jan, 22 Jan) rests on the attacker's Telegram claim as reported by Cybernews - unverified attacker claim, capped confidence. Case file source_url infobae.com articles return 404 (not citable); t.me/DIUkraine/3341 renders no post text; the RealClearDefense analysis (Smoke, Mirrors, and Self-Attribution, 2 March 2024) discussing the Akado DDoS could not be opened (403/404) and is not cited. GURMO credited unknown cyber volunteers in Russia while the IT Army self-attributed; the attribution tension is noted but does not change the victim-side assessment. Year taken from eurepoc_extra.start_date (30.12.2023). Description matches the stated victim (no data-quality mismatch).