Roll20, the online tabletop where millions play Dungeons & Dragons and other role-playing games, has confirmed a data breach that exposed salted bcrypt hashes of account passwords. An attacker exploited the flaw on Monday 16 November; Roll20 learned of the access that evening, and Roll20 told the affected players by email on Friday 20 November. Fewer than 1 percent of Roll20’s users were potentially impacted, the company says, and each of them got an email directly. The exposed data includes names, email addresses and a salted bcrypt hash of the account password. For a smaller group with a saved payment card, the last four digits of that card were exposed too.
How the attacker got in: an animated image upload
The warning email names the way in. A recipient posted its “What happened” section on Bluesky, and PrivacyAffairs reported it: on 16 November, an unauthorized third party “exploited a vulnerability in one of our systems that processed animated image uploads.” That gave the attacker access to records from a database of account information. Roll20 says it blocked the access as soon as it found it and started investigating. The company’s forum post, written by chief technology officer Mike Todd, says the “pathway” involved has been fixed.
What Roll20 has not said is which software had the flaw. Roll20 lets players upload animated maps and tokens as GIF, MP4 or WebM files, and neither the email nor the forum post names the product behind the upload system. Todd’s post also says Roll20 believes the attack “was part of a larger global trend of automated, AI-assisted attacks on organizations large and small.” No evidence for the AI element was given, and PrivacyAffairs notes Roll20 has not explained what makes it think AI was involved. Treat that as the company’s belief, not a confirmed fact about this attack.
What was taken, and what was not
For the affected accounts, the information involved included “details such as” first and last names, email addresses and a one-way salted bcrypt hash of the account password, according to Todd’s post. For a much smaller group of users with a saved payment card, the last four digits of that card were also involved. Full card numbers, security codes, expiration dates and billing addresses were not involved. Roll20 says it does not hold that information at all; it sits with its payment processors.
Two things in that account need care. First, the data list is introduced as “details such as,” which means it may not be complete. IP addresses, for example, are not mentioned this time, although the June 2024 breach did include users’ last known IP addresses. PrivacyAffairs says it has asked Roll20 whether IP addresses or other data were included, and says it will update its article when Roll20 replies. Second, Roll20’s investigation “found no evidence that the data was copied or misused.” That is the company’s own finding, and it is not the same as evidence that the data was not copied: the email itself says the attacker could access the records.
Roll20 has not said how many accounts were hit. Its homepage claims more than 15 million players, so 1 percent of exactly 15 million would be about 150,000 accounts, but that is PrivacyAffairs’ arithmetic, not a Roll20 figure. The real number could be far smaller. About 150,000 is what 1 percent of exactly 15 million would be; the homepage gives no exact total, so this is an estimate, not a cap, and never a confirmed count. Roll20 says if you did not get an email, your account was not involved.
Roll20’s third breach since 2018
Roll20 has been here before, twice. The comparison is the part that matters most, because the reassurance Roll20 gave after the last breach no longer holds.
| Breach | When | How many | Password hashes exposed? | Other data |
|---|---|---|---|---|
| December 2018 | Discovered February 2019 | Almost 4 million accounts (Have I Been Pwned) | Yes, salted bcrypt hashes | Names, emails, IP addresses, last 4 card digits |
| June 2024 | 29 June 2024, realized about 6:30pm, blocked by 7:30pm | Every account viewable (count undisclosed) | No, Roll20 stressed passwords were safe | Names, emails, last known IP addresses, last 4 card digits (only where a payment card was saved) |
| November 2026 | Evening 16 November 2026 | Fewer than 1% of users (about 150,000 estimated, not a count) | Yes, salted bcrypt hashes | Names, emails, last 4 card digits (smaller group); IP addresses not mentioned |
In June 2024, an attacker took over an account on Roll20’s administrative website and could view every user account. Roll20 realized its network had been compromised at about 6:30 p.m. Pacific time on 29 June and had blocked all unauthorized access by 7:30 p.m. The reassurance then was that passwords were safe because Roll20 only keeps bcrypt hashes. This time, the hashes are part of what was exposed. That is the difference between this breach and the last one.
The 2018 breach was far larger by count: almost 4 million accounts against about 150,000 this time, if the total were exactly 15 million. On that estimate, almost 4 million is about 27 times as many, but this is only an approximate comparison, since 150,000 is an estimate, not a count. But size is not the whole story. A bcrypt hash is a scrambled version of a password that cannot be turned back into the password directly; an attacker has to guess, hash each guess and compare, and bcrypt is built to make every guess slow and expensive. That protects long, unique passwords well. It protects short or common ones much less, because those are the first an attacker tries. And a password reused on other sites is only as safe as the weakest of them.
One thing did change between the breaches. After years of requests from players, Roll20 added two-factor authentication in October 2024, using one-time codes from an authenticator app. With it on, a cracked password alone cannot log anyone into your account, which is why two-factor authentication is included in the advice below.
What should I do if I got the Roll20 email?
If you got the Roll20 email, change your Roll20 password to a long, unique one, change it anywhere else you reused it, and turn on two-factor authentication. A salted bcrypt hash is hard to crack, but a short or reused password is not, and 2FA blocks a cracked password on its own.
- Change your Roll20 password to a long one you use nowhere else, and store it in a password manager.
- Change that password everywhere else you reused it, since a reused password is only as safe as the weakest site.
- Turn on two-factor authentication in your Roll20 account settings, using an authenticator app for one-time codes.
- Ignore messages about refunds or account verification that ask you to log in through a link, and type roll20.net.
- Open a support ticket at help.roll20.net with the subject Incident Data Request to ask what was involved.
Roll20 says it will never contact you to ask for your password. Any message claiming to be Roll20 and asking for it is a fake. The last four card digits cannot pay for anything, but they are still useful to a scammer: an email that knows your name and your card’s last four digits looks a lot more like a real Roll20 message. If you live in the EU or the UK, the GDPR also gives you a right to a copy of the data Roll20 holds on you.
What Roll20 has not said
Four days passed between the break-in on 16 November and the disclosure on 20 November, and several basic questions are still open. Roll20 has not said how many accounts were affected, whether IP addresses or other data were included, which software had the flaw, or what makes it believe the attack was AI-assisted. It has not said whether it reset the affected users’ passwords, whether its other platforms such as DriveThruRPG were touched, or which data-protection authorities it has notified. PrivacyAffairs says it has asked Roll20 all of these questions and will update its article when Roll20 replies.
What to watch next
The first thing to watch is Roll20’s reply to those questions, above all the victim count and whether IP addresses were in the set. The second is whether the breach appears in Have I Been Pwned’s catalogue, which listed the 2018 breach. The third is whether Roll20 confirms it reset the affected passwords, which would make a cracked old password useless for logging in to Roll20; it would not stop the hashes being cracked offline, and a reused password would still be at risk elsewhere. The fourth is whether any misuse or phishing wave follows, which would be new evidence of misuse after Roll20’s investigation, and would undermine the reassurance in its finding.
Roll20’s disclosure names the flaw’s shape, the data, and the limits of what it knows. The open questions are the ones that decide how bad this is. Until they are answered, the safe move is the boring one: a new, unique password and two-factor authentication.


