2023 · Ethiopia · O - Public administration and defence · DDoS attack (website taken offline)
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS attack (website taken offline)
Expertise to Execution
Evidence coverage: 1/6 stages, weight 6/60
Decisive stage: recovery (clearest evidence) · Alternative: Strategy to Execution
(1) The expectation at an Ethiopian government ministry publishing public health information, inside a national cyber-defence programme in which the authority INSA had publicly urged institutions to modernise their systems (ENA, October 2022), was that its public web service could stay available against commodity threats: DDoS protection, redundancy and scalable delivery are standard, available technical remedies. (2) In practice a low-sophistication DDoS claimed by the self-styled Mysterious Team Bangladesh took the website offline for several hours on 11 May 2023 (Cyber Express verified the site inaccessible during its own investigation, live again at publication), while the same group's unsophisticated flooding repeatedly took the online services of at least 10 Ethiopian governmental, energy and banking institutions offline for hours and up to days or weeks (Kaspersky GReAT via Capital). (3) The remedy sat in the material column as known technical practice against unsophisticated volumetric floods, yet it was not realised in operations - the site fell and stayed down for hours; no source documents any leadership decision, deferral or resourcing on the victim side, so the chain breaks at execution: a known technical remedy not executed (Expertise to Execution). The entry vector (volumetric flood) is not load-bearing; the classification rests on the recovery/availability stage, the only lifecycle stage with a documented victim-side condition, and the origin/break reading is the coder's inference from the documented facts, which caps confidence at 3. (4) RM32 (Expertise to Execution lens): the ministry's public web service could not scale or hold up under an unsophisticated botnet flood, staying offline for several hours with no evidence of DDoS protection or spare capacity keeping it serving (causal role: Enabling). RM08 (Expertise to Execution lens): operationalising the known remedy was constrained by sector capability - INSA had publicly flagged before the incident that Ethiopian institutions' technologies and working systems needed modernisation to withstand rising attacks; this marker rests on the sector-level pattern, not incident-specific confirmation (causal role: Enabling).
RM32 — Capacity / availability-protection gapRM08 — Security resourcing / capability constraintAttribution and disclosure rest entirely on the attacker's self-claim via Twitter (EuRepoC: disclosed by attacker, attribution basis 'Attacker confirms'); the ministry never confirmed the incident and did not reply to Cyber Express's queries. No incident-specific victim-side mechanism was published, so the origin/break answers at the recovery stage are coder inference and confidence is capped at 3; RM08 rests on the sector pattern (INSA statements), not incident-specific evidence. The four Twitter links in the case file source_url could not be opened in this environment and are not cited; the cited articles were opened and read here. The case description matches the stated victim (no data-quality mismatch); no related_rows in the case file and no earlier incident at this victim was found (Kaspersky's April-May 2023 campaign observation is campaign-level, not a documented earlier attack on this ministry, so RM21 was not coded). No security-policy-restricted steps were needed for this case.