← Breach analysis by the Dual Vulnerabilities framework

Cambodian government websites DDoS & data leak (Anonymous Cambodia, 2013)

2013 · Cambodia · O - Public administration and defence · DDoS disruption and data theft / doxing of government websites

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS disruption and data theft / doxing of government websites

Dual vulnerability type

Expertise to Execution

Evidence coverage: 3/6 stages, weight 12/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The strategic expectation at the victim: the Cambodian government maintained Camcert, whose stated role is to improve the government's online security, and its own officials had warned that the government lacked the information security capabilities necessary to protect state data. (2) In practice, the 2013 hacktivist campaign showed routine protections absent at execution level: simple DDoS attacks took ministry and state-media sites offline for days (the Press and Quick Reaction Unit, the Council of Legal and Judicial Reform and TVK were down from 07-09-2013, with only one restored by 12-09-2013, and the attacks continued on 27-09-2013 against the Press and Quick Reaction Unit, the Ministry of Foreign Affairs, the Ministry of Economy and Finance and the National Bank), the Anti-Corruption Unit's web system was breached with its staff credentials published, and the compromised agency neither noticed the intrusion nor informed Camcert, whose head said Camcert could not investigate until informed. (3) This is a knowing-doing gap inside the material column: the remedies - basic web hardening, DDoS resilience, credential protection - are standard specialist practice that needed no leadership decision, yet they were not realised in government web operations; comparable compromises recurred (the 2012 leak of over 5,000 Ministry of Foreign Affairs documents, the July 2013 NEC breaches) without evident remediation. The classification rests on the entry stage (the only load-bearing gap; the detection gap is documented but contributing, and it points to Strategy to Execution). The specific intrusion technique for the ACU site was never publicly disclosed and the DDoS method is trivial; the load-bearing victim-side condition is the absence of routine protections, not the attacker's technique, and no source shows leadership having decided and resourced such protections (which would make the break a leadership one) - that reading rests on the coder's inference from the documented pattern. (4) RM22 (Expertise to Execution lens): credential management was never operationalised on the government side - the ACU's staff and administrator accounts shared one trivially weak password kept in clear text, letting the attackers use the site's own administration panel (causal role: Enabling). RM26 (Expertise to Execution lens): stored data was unprotected - the published credentials were kept in clear text, so one site compromise exposed the identity material of almost 200 staff (causal role: Amplifying). RM34 (Expertise to Execution lens): the detection capability that nominally existed was not configured or operationalised - the victim agency noticed nothing and the national CERT could not investigate until told, so the attacker disclosed the breach (causal role: Obscuring). RM21 (Expertise to Execution lens): earlier comparable incidents and Camcert's own ministry security workshops (its head suggested the ACU had not taken part) were not turned into implemented, validated controls, so comparable compromises recurred across 2013 (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; victim is a multi-institution government campaign (sector coded for the government ministries). Disclosure was attacker-side (EuRepoC source_disclosure: incident disclosed by attacker). The credential-weakness details (clear-text storage, the common weak password) rest on the attackers' own published leak as reported by Softpedia and The Cambodia Daily; the victims never confirmed or contested them, so that claim is scored as speculation. The specific ACU intrusion vector was not publicly disclosed. Cambodia had no cybercrime law in 2013 (a 2012 draft was never released); this affected prosecution rather than a control, and is described here rather than coded. The case is a hacktivist operation against state targets but the victim institutions are real organisations in the framework's sense, so no atypical attacker-side exclusion applies. No related_rows in the case file. Link check: news.softpedia.com blocks automated access (HTTP 403); the page was opened and read during research.