People search Roll20 data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 3 Roll20-linked incidents, with headline counts up to 12M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Roll20 breach history matters
Roll20 operates in Technology. Across indexed rows, recurring themes include credential theft and social engineering, zero-day exploitation and malware. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2024 — 12M users, compromised admin account
Cataloged incident. Roll20, the online tabletop RPG platform, suffered a breach in July 2024 when a compromised administrative account was used to access user data. Approximately 12 million records were exposed including full names, email addresses, IP addresses, and the last four digits of credit cards. Exposed categories include Full names, email addresses, IP addresses, last 4 of credit cards. BreachHistory cites approximately 12M+ affected records in this row. See the roll202024 and canonical BreachHistory entry.
2019 — — Roll20: Roll20 was part of the theft of 127 million records…
Cataloged incident. Feb 2019. Roll20 was part of the theft of 127 million records from eight websites, by the same hacker who previously stole 617 million online account details from 16 other sites. All were put up for sale on the dark web. BreachHistory cites approximately 4M+ affected records in this row. See the roll202019 and canonical BreachHistory entry.
2018 — 4M accounts (virtual tabletop)
Cataloged incident. Roll20 database compromised in December 2018. Breach announced February 2019 after stolen data appeared on dark web marketplaces. Exposed categories include Email addresses, IP addresses, names, last four digits of credit cards, bcrypt password hashes. BreachHistory cites approximately 4M+ affected records in this row. See the roll202018 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Roll20 catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple Roll20 catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Roll20 company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/roll20 · Latest: roll202024.
Sources: BreachHistory catalog (3 rows for Roll20), company and regulator disclosures cited in individual breach records.