← Breach analysis by the Dual Vulnerabilities framework

Roll20 credential database theft (Gnosticplayers, 2018)

2018 · United States · J - Information and communication · Mass data theft (account database sold on dark web)

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Mass data theft (account database sold on dark web)

Dual vulnerability type

Expertise to Execution

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

Decisive stage: egress (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) Strategic expectation: an online platform holding identity and payment-adjacent data for millions of users is expected to protect and monitor its crown-jewel account store, and Roll20's own disclosures state that expectation explicitly - it said it had always known it was an attractive hacking target and had deliberately minimised and protected what it stored. (2) In practice: on approximately 26 December 2018 the entire accounts table (about 4 million users: name, email, last four of credit card, most recent IP, salted bcrypt hashes, ~700MB) was taken, and Roll20 did not notice - it learned of the loss only on 13-14 February 2019 when the seller 'Gnosticplayers' listed it on a dark web marketplace and TechCrunch/ZDNet named Roll20 among eight hacked sites; the later forensic work identified only 'several possible vectors of attack that have since been remedied', so the entry vector is not documented and is not load-bearing here. (3) The classification rests on the egress stage (detection as the second, same-direction gap): the knowledge that was not realised is material, not doctrinal - noticing or interrupting a bulk export of the accounts table is standard technical practice for a service of this profile, and the victim itself documented that it was aware of the threat - while nothing in the sources shows leadership deferring, under-resourcing or accepting a known monitoring need: the chain broke between existing technical expertise and operational/architectural reality, where the control was simply not implemented (Expertise to Execution). The response stage does not carry the case: once aware, disclosure within a day, GDPR notification, law-enforcement notification and an independent Kroll investigation show alignment there. (4) RM35 (Expertise to Execution lens): no egress monitoring existed to detect or interrupt the bulk departure of the ~700MB accounts table, so the crown-jewel data left unnoticed and surfaced only as a marketplace listing (causal role: Amplifying). RM34 (Expertise to Execution lens): detection capability did not identify the incident for roughly seven weeks - the victim dated its own breach indirectly from account numbers in the stolen data because no internal detection had fired (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

informationisbeautiful row: the one-line description (theft of 127M records from 8 sites, sold after a 617M/16-site tranche) matches Roll20's role in the February 2019 'Gnosticplayers' compilation; ZDNet dates the Roll20 tranche listing to 14 February 2019, three days after the 620M batch went up on 11 February, so the dataset's 'one week after' is imprecise. The case file's source_url (techcrunch.com/2019-02-14/hacker-strikes-again/) is dead: the article has been removed from TechCrunch (site returns a lost-page notice) and the indexed Wayback captures return 404 on retrieval, so it is not cited; the ZDNet article opened during research covers the same event. Year is 2018: Roll20 dated the theft to approximately 26 December 2018 and titled its own report 'Conclusion of 2018 Data Breach Investigation'; the row describes the February 2019 resale. Actor caveat: 'Gnosticplayers' is the marketplace seller; ZDNet notes it is unclear whether the seller performed the hacks. The origin/break answers at detection and egress are the coder's reading (no source documents Roll20's internal monitoring decisions), which caps the score. Country (United States) inferred from the victim's own disclosures: it referred users to the Federal Trade Commission for identity-theft resources and operates from the US. Roll20's initial forum statement said no financial data was included while the account object it later described holds the last four credit-card digits - a framing nuance disclosed by the victim itself, not a concealment.