← Breach analysis by the Dual Vulnerabilities framework

Epik data theft & leak (Anonymous, 2021)

2021 · United States · J - Information and communication · Data theft and doxing via website compromise

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Data theft and doxing via website compromise

Dual vulnerability type

Strategy to Leadership

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

Decisive stage: response (tie-break: post-breach stage) · Alternative: Expertise to Execution

Why this classification

(1) Epik was a domain registrar and web host holding a decade of customer identity data, credentials, payment histories, domain-ownership records and scraped WHOIS data on roughly 15 million people; the expectation at this victim was doctrinal on two counts: its business sold exactly the protection and anonymity of that data, and state breach-notification law (RCW 19.255.010(7)) obliged it to communicate incidents to affected individuals and regulators accurately and promptly, as its own filings show it understood. (2) In practice, Anonymous breached Epik on 28 February 2021 (timestamps in the leaked data), the intrusion went unnoticed for about six and a half months, and the cache published from 13 September contained plaintext login credentials, API keys for Coinbase, PayPal and Twitter, SSH and private keys, and eventually bootable disk images of the entire server estate. When confronted, Epik publicly denied the breach, acknowledged only an 'alleged security incident' on 15 September, and its 20 September regulator notification dated the intrusion 'on or before September 13, 2021' while never acknowledging the February attack; the September defacement of its support portal followed the company's denial. (3) The classification rests on the response/disclosure stage: the expectation (accurate, timely disclosure) originated at the doctrinal level - a legal obligation the leadership itself executed through counsel - and the chain broke at leadership, which denied a verified breach and communicated an official timeline contradicted by the leaked data and by the intrusion its own notification confirmed; this is a within-doctrinal-column gap (Strategy to Leadership), not mere weak security. The entry vector is not officially confirmed and is not load-bearing; the ignored researcher warning is a secondary Expertise to Leadership pattern, and the egress and detection gaps (plaintext credentials, six-month dwell) are Expertise to Execution readings that made the impact disproportionate. The response stage was load-bearing and, by the post-breach tie-break, prevails over the egress stage. (4) RM39 (Strategy to Leadership lens): leadership's disclosure behaviour diverged from the legal expectation and its own regulator correspondence - public denial, disclosure forced by the attacker's leak, and a notification that misstated the intrusion period (causal role: Constraining). RM34 (Strategy to Leadership lens): detection readiness received no leadership attention, leaving a roughly six-and-a-half-month dwell time ended only by the attacker's publication (causal role: Obscuring). RM26 (Strategy to Leadership lens): leadership held crown-jewel credential and payment data without protection commensurate with its sensitivity - plaintext credentials, API keys and unguarded SSH/private keys in the published cache (causal role: Amplifying). RM19 (Strategy to Leadership lens): leadership processes gave the external warning no ownership - the CEO read the researcher's January report of an unauthenticated RCE flaw, treated it as spam and did not act before the intrusion (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; receiver_category 'Social groups / Political opposition / dissidents / expats' describes the doxxed customer base, not the organisation whose lifecycle is assessed here - the intruded victim is Epik itself (Epik Holdings, Inc.), matching the row description. Entry vector was never officially confirmed: the WHOIS-library RCE flaw reported by Corben Leo is his and TechCrunch's hypothesis for how the February intrusion happened, not a confirmed mechanism; the classification does not rest on entry. The Massachusetts AG copy of Epik's customer notice (mass.gov) is a scanned PDF with no text layer and could not be read; the Maine AG notification pages cited by press now return 404, so the Washington AG notification letter (same customer notice, text layer) is cited as the primary disclosure document. The archived epik.com knowledge-base page is the September 2021 support-portal defacement itself - the text there was written by Anonymous posing as Epik - and documents the defacement mentioned in the row description. The February 2021 intrusion and the September 2021 leaks/defacement are one campaign (Operation EpikFail); Year = start year 2021. The live Daily Dot article now returns 404; the analysis was done on its text and the citation is the opened web.archive.org snapshot of 01-10-2021.