← Breach analysis by the Dual Vulnerabilities framework

Las Vegas Sands destructive hack (Iranian-linked hackers, 2014)

2014 · United States · R - Arts, entertainment and recreation · Destructive cyberattack with data theft and website defacement

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Destructive cyberattack with data theft and website defacement

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 5/6 stages, weight 29/60

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

Why this classification

(1) Las Vegas Sands Corp., the world's largest gaming company, ran SEC-reportable operations and customer data under Pennsylvania's breach rule that notice must be made 'without unreasonable delay'; after the February 10, 2014 attack its strategic-level narrative was containment, insisting the company's 'core operating systems have not been impacted'. (2) In practice a campaign running since December 2013 (VPN brute-forcing, then a January compromise of the Bethlehem VPN gateway) reached the Microsoft IIS development/staging server behind the casino website; mimikatz-harvested credentials, including a senior systems engineer's, unlocked the corporate network, and on February 10 wiper malware cascaded across thousands of PCs and servers, took email, phones and the Venetian, Palazzo and Asia-facing sites down for about a week, while almost a terabyte of data left unseen. Sands said in February that mid-five-figure customers' Social Security and driver's license numbers had been stolen (SEC filing, Feb 28, 2014) yet continued to minimise the damage; the scale of the wipe emerged only through Bloomberg Businessweek in December 2014, which the company declined to confirm, and affected patrons received letters in late December 2014 - roughly 10 months after the breach - with the company pointing to its ongoing investigation. (3) The classification rests on the response/disclosure stage: the expectation was doctrinal (the company's public containment account and the prompt-notification standard) and the chain broke at leadership, which communicated inaccurately and timed notification badly - the espoused strategic account diverged from what the company's own filings and the impact record showed. The entry gap (exposed non-production server, credential harvesting), the containment gap (company-wide wiper cascade), the detection gap (weeks of unnoticed intrusion) and the egress gap (about a terabyte leaving undetected) read as Expertise to Execution, but their origin and break rest on inference and cannot win the decisive stage; recovery was not the constraint. (4) RM39 (Strategy to Leadership lens): leadership's disclosure behaviour diverged from the legal and strategic expectation of prompt notice - letters to affected Sands Bethlehem patrons arrived about 10 months after the February 2014 breach, while the public account downplayed the impact (causal role: Constraining). RM30 (Strategy to Leadership lens): containment and blast-radius reduction were not made architectural priorities, so a single intrusion wiped thousands of PCs and servers in a cascading catastrophe across properties on three continents (causal role: Amplifying). RM34 (Strategy to Leadership lens): detection objectives were not ensured or acted upon at oversight level - VPN probing from December 2013, the January gateway compromise and the February staging-server intrusion went unnoticed until the destruction itself started killing systems on February 10 (causal role: Obscuring). RM29 (Strategy to Leadership lens): the delivery strategy did not hold the non-production environment to production standards - the staging server behind the corporate website was internet-reachable and its stolen credentials opened the corporate network (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

Dataset name 'Sands-Casino-Hack'; victim established as Las Vegas Sands Corp. (Sands Casino Resort Bethlehem most affected). Year 2014 from eurepoc_extra.start_date (01.02.2014) and the Feb 10, 2014 attack; Bloomberg's timeline shows attacker probing starting December 2013, not recorded as the incident year. Attribution is contested: company-hired investigators assessed politically motivated hacktivists (as reported by Bloomberg/Reuters press), while DNI Clapper attributed the attack to Iran before the Senate Armed Services Committee on Feb 26, 2015; the DV is assessed victim-side, so attribution does not enter the claims. EuRepoC coded the theft as non-sensitive commercial data, while press and the company's own statement list Social Security and driver's license numbers. The Bloomberg article is subscriber-only - only the opening section was readable; its mechanism details were corroborated via Softpedia, The Hacker News and Security Affairs quoting the same story. The case file's CNN source_url returned HTTP 502 when opened and is not cited. The case file carries no related_rows. Destruction was detected within an hour on Feb 10, so RM34 is coded for the undetected intrusion campaign of Dec 2013 - Feb 2014, not the wipe itself. No regulator or court finding on the victim's controls was found; a Reuters republication of the Bloomberg story rendered no article body and was not cited. Link check: news.softpedia.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: mcall.com blocks automated access (HTTP 403); the page was opened and read during research.