← Breach analysis by the Dual Vulnerabilities framework

Government of Sri Lanka Minister of Sports website hack (Davy Jones, 2013)

2013 · Sri Lanka · O - Public administration and defence · Website hack with data and credential leak

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Website hack with data and credential leak

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 4/6 stages, weight 19/60

Decisive stage: response (clearest evidence) · Alternative: Expertise to Leadership

Why this classification

(1) The victim is a Sri Lankan government ministry whose public web presence sat inside a national incident-response doctrine: SLCERT, the national CERT, was monitoring the January 2013 wave of hacks on government sites and said on record it was ready to inspect and restore them once officially asked. (2) In practice, on 26-01-2013 the individual hacker 'Davy Jones' breached the Minister of Sports website as part of a weeks-long campaign against Sri Lankan government sites and published the site database with admin credentials (attacker claim via Pastebin, never confirmed by the victim), while the affected ministry and its peers detected nothing, filed no complaint and never asked SLCERT to inspect their sites, so the CERT said its ability to look into the attacks was limited without an official government request; disclosure came entirely from the attacker's leak. (3) The expectation - hand incidents to the national response capability and keep government sites maintained - sits at the doctrinal/strategic level and was publicly offered, yet the chain broke at the decision level: no institutional owner took ownership or activated the framework. That is a gap within the doctrinal column (leadership behaviour not grounded in the existing strategy), not merely weak security. The entry vector is undisclosed and not load-bearing; government-wide reporting on unmaintained sites (one-year developer contracts, no updates afterwards, low budgets) indicates a secondary Expertise to Leadership pattern at entry, but rests on sector-level statements rather than incident-specific confirmation. RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged from the expectations of the national response framework - the breach of the minister's site was made public solely by the attacker's own data publication, while the ministry neither acknowledged the incident nor referred it (causal role: Constraining). RM36 (Strategy to Leadership lens): decision rights for crisis response were effectively unestablished - SLCERT could not act without an official request and none of the hacked government institutions, including the victim, ever made one, leaving a documented response-readiness gap across the whole campaign (causal role: Constraining). RM34 (Strategy to Leadership lens): leadership oversight provided no detection objective for these government sites - owners had to ask the national team to check whether they had been hacked at all, and the intrusion surfaced only via the attacker's leak (causal role: Obscuring). RM14 (Strategy to Leadership lens): leadership did not preserve accountability when responsibility crossed the supplier boundary - after the one-year website development contract ends, government sites are left with no security updates and no accepted maintenance owner, as described on record by SLCERT's information security engineer (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; victim named descriptively (the dataset has no receiver_name; the row's name field reads DavyJones vs. Government of SriLanka). The data/credential leak for the minister's site rests on the attacker's Pastebin publication as reported by press; SLCERT checked another site in the same campaign (Board of Investment) and found no evidence of a leak, so leak claims in this campaign are unverified. Attribution is self-attribution only; the actor's identity (one report suggested a Pakistani national) is unconfirmed; the motive (belief the government is corrupt) is an attacker claim. The entry-side maintenance evidence is government-sector-wide (pattern), not incident-confirmed for this site; the entry vector itself is undisclosed. No regulator or formal investigation of the incident was found; no related_rows in the case file.