← Breach analysis by the Dual Vulnerabilities framework

Weebly credential theft (Unattributed, 2016)

2016 · United States · J - Information and communication · Data theft: bulk exfiltration of the user credential database

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft: bulk exfiltration of the user credential database

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 10/60

Decisive stage: detection (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) Weebly, a US web-hosting and website-builder platform, held its entire customer base - some 43.4 million accounts - in one central database, so the baseline technical expectation was that the copy of that database out of the estate would be detected or interrupted and that password protection would be applied consistently across the estate. (2) In practice an unauthorized party copied a file containing all 43,430,316 records between October 2015 and February 2016; Weebly noticed nothing and learned of it only on 8 October 2016 when LeakedSource, which had received the data from an anonymous source, informed it - roughly eight months later, with the Alberta OIPC noting the information may have been exposed on the dark web for almost 1 year; the root cause of the intrusion was never disclosed. Accounts created before June 2011 also remained on MD5 hashes until they were automatically reset after the breach. (3) This is a knowing-doing gap inside the material column, not a doctrinal one: the remedies were the technical specialists' own known craft, and the company demonstrably possessed the expertise - its engineers had implemented salted bcrypt for all accounts created after June 2011 - yet operations did not realise it estate-wide (the legacy MD5 cohort stayed weakly protected) and monitoring did not register a full-database theft for months. No source documents any Weebly policy, standard or leadership decision on detection or egress monitoring, so origin cannot be placed at the strategic level and the break cannot be placed at leadership: the chain broke in execution. The entry vector is unknown and is not load-bearing; the classification rests on the detection stage, corroborated by the egress stage (both point to Expertise to Execution, so no tie-break was needed). The response stage cuts the other way: once notified Weebly disclosed and remediated promptly, which is why the case is not a Strategy to Leadership pattern. (4) RM34 (Expertise to Execution lens): the detection tooling and alert handling were not configured, staffed or tuned to catch the activity - an 8-month dwell time ended only by an outsider's notification, and the regulator cited the near-year exposure as raising harm (causal role: Obscuring). RM35 (Expertise to Execution lens): egress visibility and prevention were not realised in the architecture - the single copy of the entire user database left the estate unnoticed and surfaced on the dark web, so the theft of the crown-jewel dataset went uninterruptible by design gap rather than by attacker sophistication (causal role: Amplifying). RM26 (Expertise to Execution lens): the known hashing remedy could not be applied to the pre-June-2011 cohort, which stayed on MD5 until a forced post-breach reset, a legacy-driven cryptographic weakness inside otherwise adequate password protection (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Case-file source_url (techcrunch.com/2016-10-20/weebly-hacked-43-million-credentials-stolen/) returns 404 and the path variant without trailing slash also failed to open (http_error); the analysis rests instead on the Alberta OIPC breach-notification decision (primary, records Weebly's own report to the regulator) plus three security-press articles opened in full. Weebly's own security-update page (hc.weebly.com/hc/en-us/articles/230297688) is gone (404), so its statements are taken as quoted by CSO/SecurityWeek/OIPC. Year: press dates the theft to February 2016 (file dating); the OIPC gives a wider believed window of October 2015 to February 2016 - 2016 recorded, following the dated file and the dataset. The Alberta OIPC found a real risk of significant harm, disagreeing with Weebly's own assessment that the data was non-sensitive, but recorded no notification failure (all individuals were emailed 20 October 2016); no regulator examined or found the root cause - it remains undisclosed. Actor unattributed; no related rows in the case file and no prior result for this victim in the output directory. The case-file description matches the incident (IP addresses, usernames and hashed passwords stolen). Link check: helpnetsecurity.com blocks automated access (HTTP 405); the page was opened and read during research.