Hacker Claims to Have Obtained Kick Payment Info, Passwords, and More for Thousands of Users

gamerant.com:

In a recent development, a hacker claimed to have obtained sensitive information belonging to thousands of users on Kick.com, a streaming platform owned by Stake.com and positioned as a rival to Twitch. The alleged breach includes payment details, passwords, and additional personal data, raising concerns about the security of Kick's growing user base.

For those unfamiliar, Kick burst onto the scene in December 2022, introduced by popular streamer Trainwreck, with relaxed ban policies and higher payout rates immediately setting it apart from leading streaming platform Twitch. Initially met with skepticism, Kick has defied expectations, experiencing rapid growth and attracting numerous prominent streamers to its platform. One of its most notable signings was xQc, a renowned streamer who made headlines in June last year by joining Kick in a groundbreaking $100 million deal, igniting widespread surprise and discussion within the industry. Other notable streamers who have since joined Kick include Adin Ross, Amouranth, Nickmercs, and many others.

However, on February 13, a Twitter/X user going by @KickViewBot claimed to have uncovered a significant security vulnerability in Kick's system, compromising sensitive data of 50,000 users, including emails, passwords, payment information, password resets, and addresses. Remarkably, the hacker made it clear that their intentions were altruistic; they sought to raise awareness and prompt action from Kick rather than exploit the compromised data. What made this breach particularly alarming were the prominent names associated with the compromised accounts. According to KickViewBot's claims, the affected users included high-profile streamers such as xQc, Trainwreck, Adin Ross, Fousey, and Kick staff members.

In response, Kick's Head of Product vehemently denied the allegations, stating that they do not store unencrypted passwords and dismissing the hacker's claims as fabricated. Despite Kick's reassurances, @KickViewBot persisted,