← Breach analysis by the Dual Vulnerabilities framework

Iranian government websites DDoS disruption (Anonymous, 2011)

2011 · Iran · O - Public administration and defence · Distributed denial-of-service (DDoS) attacks on government websites

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Distributed denial-of-service (DDoS) attacks on government websites

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) Strategic expectation at the victim: the affected entities are Iranian state institutions - the Office of the Supreme Leader, the Parliament, the police, the Ministry of ICT, the Basij militia sites and the Fars news agency among more than a dozen government sites (receiver subcategories: government/ministries, legislative, police, political parties) - for which one would expect basic availability protection of official public websites; no source documents any Iranian policy, programme, resourcing decision or control relevant to these websites, so no doctrinal expectation can be evidenced. (2) What happened in practice: on 1 May 2011, timed to International Workers' Day, the hacktivist collective Anonymous launched #OpIran, a coordinated DDoS campaign using the LOIC tool announced on 23 April; Fars News was inaccessible within four minutes, then the police, Basij and Parliament sites fell, the Supreme Leader's homepage was offline about an hour before reinstatement, and attacks continued through the following days with sites back online but sporadically attacked; some sites had been unreachable for more than a day already in an earlier February 2011 wave of the same campaign; there was no data theft and the case file scores the disruption as short-term (<24h, intensity 1). (3) Why this is Unknown rather than a DV-Type: the incident-specific reporting confirms impact only - sites taken offline and restored - and the operational detail comes from the attacker's own statements and hit lists; no statement from the Iranian authorities about these DDoS attacks, no regulator or CERT finding, and nothing about the victims' detection, mitigation posture, recovery or response appears in the sources reviewed. Placing the case on the origin x break axes would require inferring a missing DDoS-mitigation capability from the outages themselves - an 'attacker used technique X, therefore DV-Type Y' reading the method explicitly rejects - and the outages cannot distinguish whether protection was decided and not realised (an execution break) or never authorised or funded (a leadership break). The entry vector (volunteer LOIC flood) is known but is not load-bearing for any classification. A condition resembling RM32 Capacity / availability-protection gap is visible - repeated hours-long to day-long outages of state websites under a commodity DDoS tool - but it rests on outage reporting alone, so the DV-Type stays Unknown; the case is flagged as atypical: a hacktivist disruption campaign against multiple state web properties, disclosed by the attacker, with no victim organisation speaking on the record.

Risk markers

Sources

Notes

Data quality: the case file carries no receiver_name; the victim is recorded as the EuRepoC incident name 'Anonymous vs. Iran' as written in the case file. The actually affected entities are a diffuse set of Iranian state institutions (Office of the Supreme Leader, Parliament, police, Ministry of ICT, Basij, Fars news agency); the row's description matches the incident. Sources are attacker-claim heavy: target list, timings and takeover claims come from Anonymous statements (hit list, Twitter, interviews with self-described members) as reported by The Hacker News, OWNI and the Center for Human Rights in Iran; no Iranian official statement on the DDoS attacks was found in the sources reviewed. The February 2011 attacks on the same victim category (Foreign Ministry site offline for more than a day, cited article) are an earlier wave of the same campaign and a separate incident, not this row; no earlier row for this victim exists in the run's case set, so no recurrence marker is coded. Searches for 2011 Iranian government or CERT reaction to the May attacks returned later OpIran campaigns (2022), not this incident.