2018 · Mexico · S - Other service activities · DDoS attack on a campaign website
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS attack on a campaign website
Expertise to Execution
Evidence coverage: 1/6 stages, weight 8/60
Decisive stage: recovery (clearest evidence) · Alternative: Expertise to Leadership
(1) The doctrinal and operational expectation at the victim: a party coalition that launches a site on a placard in front of a nationally televised presidential audience must be able to keep it available under a foreseeable surge of both genuine visitors and adversaries; the standard remedies (elastic hosting, an intermediary filtering/mitigation service) were commercially available and a Cloudflare layer with country-based access rules was already in use. (2) In practice the site crashed during the debate on 12 June 2018 and remained inaccessible (Reuters reported hours; the fact-checkers measured about ten minutes of full unavailability), PAN attributed it to a DDoS with traffic mainly from Russia and China, while Mexican security specialists (Verificado 2018 / Animal Politico, SocialTIC, Bianciotto) found the evidence did not prove a Russian attack - the coalition's own report showed only about 10,000 requests from Russia - and identified the primary cause as the administrators' failure to contract elastic capacity or an extra filtering intermediary for a surge that the launch itself made predictable; the site could not serve even legitimate traffic. (3) This is a knowing-doing gap inside the material column: technical experts could name the available remedies and the scenario was foreseeable, yet they were not realised in the site's architecture and operations; the break is in execution, not leadership, because no source shows PAN leadership was told of the need and deferred or defunded it, and no formal availability policy of the party is documented (which would make it a doctrinal gap). The entry vector (an unattributed volumetric flood, plausibly mixed with organic traffic) is not load-bearing for the classification; it rests on the resilience/recovery stage. (4) RM05 (Expertise to Execution lens): the site's operators never assessed the scenario that materialised - that Mexican traffic alone, at the volume a televised launch would generate, could overwhelm the server - as specialists put the cause down to a capacity miscalculation and a lack of prevention, so the threat was not identified in the run-up (causal role: Predisposing). RM32 (Expertise to Execution lens): capacity and denial-of-service protection were insufficient to keep the service available under the attack and surge, because the web team did not scale the architecture with elastic services or an additional filtering intermediary even though those were available to them (causal role: Enabling).
RM05 — Risk-identification / threat-assessment blind spotRM32 — Capacity / availability-protection gapActor unattributed: PAN's public claims (rival's bots; traffic from Russia and China) were contested by Verificado 2018 specialists and unconfirmed by Reuters; Morena denied involvement; no official investigation is documented. Outage duration differs across sources: Reuters reported hours, Verificado 2018 specialists about ten minutes of full unavailability. The crashed site was debate2018.mx, created and run by the PAN-led Por Mexico al Frente coalition to publish documents criticising Lopez Obrador; the row describes it as the party's website, which matches in substance. Sector: a political party's primary activity falls under SBI section S (membership-organisation activities), not O, as the party is not a government body. SecurityWeek notes attribution in DDoS cases is inherently difficult (Netscout Arbor: 300+ DDoS attacks/day in Mexico that week, largest over 200 Gbps, none confirmed as this one). Link check: reuters.com blocks automated access (HTTP 401); the page was opened and read during research.