After a possible breach, hackers start publishing personal data of Roobet streamers
A new leak campaign is unfolding around Roobet, and this time the target is not the platform’s servers but the people who stream on it. Documents allegedly belonging to several Roobet-affiliated streamers are being posted on a dedicated site, with the collection growing as the campaign continues. The operator itself has stayed quiet.
What’s known
The material posted so far includes identity documents, home addresses, and transaction correspondence tied to the names of several creators. For one of them, identity is not in question: DOUGGAMBLES, a channel with 11,300 followers on Kick. Whoever claimed responsibility for the release describes their motive as selective, targeting specific streamers they suspect of colluding with Roobet and showing inflated balances to viewers for effect. None of the documents have been independently verified.
The tactic of publicly exposing streamers under the banner of fighting fake balances has surfaced before in gambling content, and it tends to blur two very different things together: a legitimate complaint about deceptive content, and a decision to publish someone’s passport and home address regardless of whether the underlying accusation holds up. Even if some of the inflated-balance claims turn out to be true, publishing identity documents is a far more serious act than simply calling out questionable content.
Context
This is not Roobet’s first incident like this. In October 2025, the company acknowledged a security failure on the side of Fast Track, the third-party service the platform uses for audience engagement. That leak was limited to email addresses, names, and basic account details — attackers did not gain access to passwords, wallets, or customer funds, according to the operator. Customers were advised to add two-factor authentication and watch for suspicious links.
Two incidents in under a year, even through different attack vectors, tend to change how a platform’s security statements get read. A single breach tied to a third-party vendor can be written off as a one-time accident. A second episode in a row hit people connected to the brand rather than the platform’s own infrastructure, and that is a different kind of story — Roobet’s data may simply be less secure across the board than its official statements suggest.
October’s breach was a story about servers and vendors. This one is about real people who go live under the brand’s name every day, and for them the fallout is far more direct than any leaked email address.
Share
SUBSCRIBE TO OUR PRIVATE CASES AND USEFUL TIPS
Subscribe to our newsletter, get only exclusive content and weekly digests, no any spam!
By providing my email, I accept the Privacy Policy.