2022 · Lithuania · O - Public administration and defence · DDoS campaign against government, transport and media websites
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS campaign against government, transport and media websites
Strategy to Execution
Evidence coverage: 1/6 stages, weight 8/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution
(1) The strategic expectation at the victim side was availability under hybrid pressure: Lithuanian state institutions ran their services on the Secure National Data Transfer Network, officially presented as a critical component of the national cyber-security strategy and as built to stay operational during crises or war to guarantee the continuity of critical institutions. (2) In practice, the June 2022 DDoS campaign by Killnet and NoName057(16), triggered by the Kaliningrad transit ban, left part of that network's users unable to reach services, forced the State Tax Inspectorate to halt all activities, and over roughly ten days hindered or took offline more than 130 state, transport, financial and media websites, with functional impact lasting days (the government opened a criminal investigation). (3) The classification rests on the response stage (availability under attack): the expectation is doctrinal - a stated strategic continuity commitment, not merely a technical remedy - and the break is in execution: the realised architecture and DDoS protection did not deliver the stated commitment, and additional protections had to be applied mid-incident by the Core Center of State Telecommunications with international providers. No source shows leadership deferring, under-resourcing or accepting the availability gap, so the break is execution rather than leadership; the entry vector is not load-bearing (a flood, not an exploited weakness), and detection, egress and recovery show no documented victim-side gap. RM32 (Strategy to Execution lens): availability and DDoS-protection requirements were not implemented in the running architecture, so the flood took state services, the crisis-resilient network and well over 130 websites down for hours to days (causal role: Enabling). RM04 (Strategy to Execution lens): many critical state services depended on the single shared Secure National Data Transfer Network, an architectural concentration that let one attack produce a wide outage across institutions (causal role: Amplifying).
RM32 — Capacity / availability-protection gapRM04 — Control dependency concentrationMulti-organisation national campaign: no single victim organisation, victim named descriptively per the method spec (state institutions, critical infrastructure and corporate targets per the receiver categories); Country taken from eurepoc_extra.receiver_country. Killnet's claim of 1,652 demolished web resources and 70% network isolation is an unverified attacker claim and is not used for the classification. Whether Killnet and NoName057(16) acted jointly is unknown per the case description; Avast's Bobik report covers NoName057(16) malware targeting transport companies from 18 June. The live lrv.lt government statement no longer loads, so the opened Wayback snapshot of 27 June 2022 is cited; the identical ministry statement remains live on kam.lt. A CNN article on the attack would not open and is not cited. Link check: kam.lt blocks automated access (HTTP 403); the page was opened and read during research. Link check: reuters.com blocks automated access (HTTP 401); the page was opened and read during research. The RM44-adjacent point - the resilience claim for the secure network versus its behaviour under attack - describes a failure during the incident rather than a pre-breach misrepresentation, so it is described in the rationale and not coded.