2023 · Israel · J - Information and communication · Distributed denial-of-service (DDoS) attack knocking a news website offline
Analysed 2026-11-07 by Hermes
Open this case in the tool →Distributed denial-of-service (DDoS) attack knocking a news website 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 the victim was that its flagship public news site stays available under hostile traffic: the Jerusalem Post is Israel's most-read English-language newspaper, and after the same group's DDoS took the site down for more than an hour on 5 April 2023, the threat was concretely known to the organisation before the October war weekend. (2) In practice, from 7 October 2023 (the Hamas attack) until at least 9 October, the Anonymous Sudan DDoS service repeatedly knocked the homepage and specific war-reporting pages offline; the paper's editor-in-chief said they had been trying to deal with a succession of devastating attacks but were taken down several times, and Check Point Research recorded roughly two days of disruption - one of the very few successful attacks in a campaign of hundreds of floods. (3) This is a knowing-doing gap inside the material column: the remedy (DDoS mitigation and capacity scaled to a known threat actor) is standard technical practice, and the Post demonstrably held incident-specific knowledge of this actor's method since April 2023; the chain broke in execution, because the same technique by the same actor succeeded again in October at far greater scale. No source documents a doctrinal availability policy or a leadership deferral, so the classification rests on the recovery/availability stage as the only documented victim-side gap; the entry vector (a volumetric flood against a deliberately public website) is not itself a victim-side gap and is not load-bearing. (4) RM32 (Expertise to Execution lens): experts could not keep the desktop news service up under flood traffic because the protection was not realised at the capacity the threat demanded, so the site stayed offline for roughly two days over 7-9 October while alert apps, banks and government sites shrugged off comparable floods (causal role: Enabling). RM21 (Expertise to Execution lens): the known technical remedy was not implemented or validated to a sufficient standard after the earlier event of 5 April 2023, when the identical actor took the same site down with the same technique, so the comparable weakness recurred in October with an outage roughly forty times longer (causal role: Perpetuating / learning-blocking).
RM32 — Capacity / availability-protection gapRM21 — Recurring weakness / learning failureDisruption-duration discrepancy: the case file scores the disruption as short-term (< 24h, functional impact Day < 24h, intensity 1), but the US indictment (overt acts 107-110, Central District of California, CR No. 2:24-cr-00614) documents attacks on jpost.com from 7 October until at least 9 October 2023 with the attacker's own +24h and +50h still-down posts, Check Point Research records approximately two days of disruption, and The Record reported the site still down on Tuesday 10 October; the classification uses the incident as documented in sources. Overt act 111 (defendant Telegram post of 9 October claiming all Post articles had been deleted) is an unverified attacker claim reproduced in the indictment, corroborated by no other source - not treated as data destruction. Attribution: self-attribution via the group's Telegram channel on 8 October 2023 (dataset attribution_basis: attacker confirms); the t.me attribution URL from the case file was not opened per research policy (attacker channel; cited as reported by press). Two case-file source URLs returned 404 when opened (channelnewsasia.com/world/hackers-disrupt-israel-gaza-conflict-hamas-palestinians-cybersecurity-ddos-3836641 and c4isrnet.com/cyber/2023-10-31/hacktivists-join-the-front-lines-in-israel-hamas-war/), and the techcrunch.com 9 October article failed to fetch; the same facts are carried by the opened Daily Beast, Record, Dark Reading, heise and Security Affairs articles. The 5 April 2023 takedown of the same site by the same group is a separate earlier incident at this victim, recorded here as the RM21 basis, not as the row's incident. The Dark Reading source_url in the case file redirects to the /threat-intelligence/ path, which is the URL cited.