Gaming hardware company Razer has suffered a leak that potentially exposed the personal information of more than 100,000 customers who are registered in the Razer system.

The leak looks like it was the result of a faulty Elasticsearch database that exposed customers’ emails, addresses, and phone numbers, but not their passwords, according to Ars Technica.

I must say I really enjoyed my conversations with different reps of @Razer support team via email for the last couple of week, but it did not bring us closer to securing the data breach in their systems. pic.twitter.com/Z6YZ5wvejl

— Bob Diachenko 🇺🇦 (@MayhemDayOne) September 1, 2020

Security researcher Volodymyr Diachenko identified the leaky cluster back in August, but according to his reports, Razer was less than coordinated in its response.

The current Elasticsearch leak was also reportedly accessible via public search engines. According to Ars Technica, Razer has experienced leaky cloud functionalities several times in the past.

Razer has not yet responded to a request for comment. The company asks customers to sign in to the cloud to use Synapse, its program to control all of a user’s hardware.

Related Posts

Your first Windows on ARM gaming laptop may be a Lenovo Legion

The clue comes from how Lenovo's naming appears to tag the platform inside each system. Qualcomm is marked with a Q, while NVIDIA shows up under two labels, N1 and N1X. A dataminer, Huang514613, surfaced a cluster of Lenovo models where those tags appear across multiple families, not just one device.

New study shows AI isn’t ready for office work

A reality check for the "replacement" theory

Google Research suggests AI models like DeepSeek exhibit collective intelligence patterns

The paper, published on arXiv with the evocative title Reasoning Models Generate Societies of Thought, posits that these models don't merely compute; they implicitly simulate a "multi-agent" interaction. Imagine a boardroom full of experts tossing ideas around, challenging each other's assumptions, and looking at a problem from different angles before finally agreeing on the best answer. That is essentially what is happening inside the code. The researchers found that these models exhibit "perspective diversity," meaning they generate conflicting viewpoints and work to resolve them internally, much like a team of colleagues debating a strategy to find the best path forward.