← Breach analysis by the Dual Vulnerabilities framework

Russian Embassy in London DDoS (Unattributed, 2011)

2011 · Russia · O - Public administration and defence · DDoS attack causing website disruption

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

DDoS attack causing website disruption

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) The expectation at the victim was the availability of the embassy's public information website, heightened around a high-profile state visit: the embassy itself foresaw a considerable increase in traffic and placed information on a secondary location, and the mirror site www.rusemborguk.ru was used to keep the service running. (2) In practice, between 9 and 12 September 2011 the main website www.rusemb.org.uk was repeatedly brought unreachable by a DDoS attack (down Friday evening, partly available Saturday, down again Sunday); the embassy's IT switched traffic to the mirror, the site was fully restored, no data theft occurred, and the embassy disclosed the incident itself (Twitter 10-11 September, press release of 12 September) and requested the British authorities to investigate. (3) Under the decision rule this is Unknown, not a DV-Type: the record - including the victim's own press release - confirms the impact and a competent victim-side handling, but no source documents why the main site's denial-of-service protection was insufficient; no stage's origin (doctrinal or material) and break (leadership or execution) can be answered from evidence rather than coder inference, so no victim-side mechanism can be placed on either axis. The entry vector is attacker-side and not load-bearing for a victim-side classification. RM32 Capacity / availability-protection gap is recorded as the one victim-side condition the evidence shows (the main site could not stay available under the flood and redundancy via the mirror was needed), but it is not attributed to a knowing-doing or doctrinal-material gap.

Risk markers

Sources

Notes

Atypical case: politically motivated hacktivist-style DDoS against a diplomatic mission's public website; weighted intensity 1, short-term disruption, no data theft. Per the decision rule the DV-Type is Unknown because the reporting (victim statement, Reuters/NBC, ZDNet, Infosecurity, Softpedia) confirms impact and the victim's response only - nothing about the embassy's hosting, capacity or DDoS-protection posture, so no victim-side mechanism can be evidenced. Actor unattributed: media-based suggestions only (Tech Eye via Softpedia: UK hacktivists; ZDNet: outsourcing to a DDoS-for-hire vendor, phrased as it appears the attack was outsourced; no official attribution; the dataset records Attribution given, type unclear / Media-based attribution). Date caveat: the case file carries start_date and end_date 12.09.2011, while the embassy's own press release covers the full 9-12 September 2011 window; Year 2011 is unaffected. The description matches the victim derived from the dataset (the row name is the protest framing, not a data-quality mismatch). No related_rows in the case file. The live page rusemb.org.uk/press/219 returned HTTP 502 at research time, so the embassy press release is cited as the 2011 Wayback snapshot that was opened and read during this task. Link check: news.softpedia.com blocks automated access (HTTP 403); the page was opened and read during research.