Roll20 Blog

Roll20 Security Breach

Written by The Roll20 Team | Feb 14, 2019 8:00:00 AM

Earlier today, Roll20 was named in a report as one of several victims of an attack by malicious cybercriminals. We are currently working diligently to investigate the veracity of those claims.

Our security teams work tirelessly to monitor, identify and fix potential weaknesses in our systems to prevent any attacks, and we take seriously our responsibility to safeguard our users’ personal information. Accordingly, Roll20 only maintains users’ name, email address, hashed password, last login IP and time of login, and the last 4 digits of users’ credit card. We use Stripe and PayPal to process transactions; all billing information is handled by them and never touched our servers. For password hashing we utilize bcrypt, which means that it cannot be reverse-engineered for utilization with other sites or to access Roll20.

We work hard to ensure data breaches don’t happen, and we always plan ahead for worst-case scenarios. That’s why we maintain strict limits on the amount of personal information available for exposure in such a breach.

We will be continuously updating our members with information as we receive it.

__UPDATE 3:38PM PT: __To remove any possible session cookies, we’ve logged everyone out of the site as a security precaution as we continue to investigate.

We have confirmed a possible time-frame from this data based on the number of accounts the cybercriminal states they accessed and we are still researching methodologies of access.

__UPDATE 2/15 2:45 PM PT: __ Based off the account numbers from breached data, we’ve determined this took place on approximately December 26th. The data size (~700MB) is consistent with being our “account object,” which, as earlier stated, contains name, email address, last four of credit card, most recent IP address, and hashed & salted password. While the hash & salt should keep passwords safe, it never hurts to reset.

We are continuing to work internally and with outside investigators to determine the methodology of breach, while also fulfilling GDPR requirements and notifying appropriate law enforcement. Expect more details early next week.

__UPDATE 2/22 1:00 PM PT: __We wanted to give an update, even though there is a limited amount that can be offered at this time.

We’re working with legal and an outside security firm to confirm elements of the breach and attempt to determine its vector. We’re working to advance these steps as quickly as possible, but know this will be an ongoing process.

In terms of immediate aftermath, we feel fortunate that the scope appears limited. We know, given our market, that your data is an attractive target– which is why we’ve intentionally stored and processed minimal information, and been diligent in protecting what is necessary for us to have.

We appreciate how understanding the community has been in the process, and will continue to give updates as we’re able.

__Update 8/12 1:00 PM PT: __The complete investigation has been officially concluded, with details given in the blog post here: Nonehttps://blog.roll20.net/post/186963124325/conclusion-of-2018-data-breach-investigation