2013 · Lebanon · O - Public administration and defence · Website defacement and short-term outage
Analysed 2026-11-07 by Hermes
Open this case in the tool →Website defacement and short-term outage
No DV evidenced
Alternative: none defensible
(1) The doctrinal expectation at a national legislature would be that its public web presence is protected and that a compromise is investigated and the cause identified, but the reporting documents none of this. (2) What the sources establish is the impact and the reaction only: on 23 February 2013 the Parliament's website (lp.gov.lb) was defaced by the self-named Team Kuwaiti Hackers, who posted a photo of Sheikh Ahmad al-Assir and an anti-Hezbollah, pro-Assad message in the context of the Syrian conflict; the site was taken down and stayed down roughly a day before being restored, and the Parliament's General Secretariat stated that the concerned department was working on restoration and warned of legal prosecution. (3) No source documents a victim-side failure point at any lifecycle stage: the entry vector is undisclosed, no policy, known technical remedy, expert warning, or leadership decision is reported, detection is implicit in the visible defacement, there was no data theft, recovery took under a day with no reported obstacle, and the disclosure was immediate via the attacker's own claim with a prompt victim statement. With reporting confirming impact only, the decision rule puts this case at Unknown rather than a forced type; reasoning that a defacement proves a hardening gap is the coder's inference, not evidenced origin/break. The one condition the sources do document is recurrence: Lebanese government websites were defaced repeatedly (Raise Your Voice in 2012, the Parliament website hacked again on 21 June 2013), while perpetrators were seldom identified and Lebanese security officials remained poorly equipped to deal with the attacks - the country lacked a cybersecurity strategy - but these are country-level conditions, not an incident-specific victim-side mechanism at the Parliament, so they are described here rather than used to force a DV-Type.
RM21 — Recurring weakness / learning failureEuRepoC row; victim named from receiver_category (State institutions / political system, Legislative) and receiver_country Lebanon; the row itself carries no receiver_name. Attribution rests solely on the group's self-attribution in the defacement; the Kuwaiti identity of the actors is unverified, and Sheikh al-Assir, whose photo was posted, denied any connection. Entry vector undisclosed; no incident-specific victim-side mechanism documented in any source found, so DV-Type is Unknown per the decision rule (reporting confirms impact only) - confidence null with no assessable mechanism. RM21 is recorded despite Unknown (allowed 0-4): the recurrence it names is documented - the same Parliament website was hacked again by Raise Your Voice on 21-06-2013 and government sites repeatedly in 2012 (Freedom House Freedom on the Net 2014; Naharnet) - but no source documents remediation lessons being taken after the February 2013 defacement. The dataset's first source_url (dailystar.com.lb, 23-02-2013) returned HTTP 403 when opened and is therefore not cited; the article's substance was corroborated through the Naharnet, Asia Media Centre, HackRead and Softpedia articles opened during this task. Case file carries no related_rows and no legal/political response fields; none were found. Link check: news.softpedia.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no step required consent and none was skipped.