The attack led down the setting Saturday, September 30. In a comment released on Sunday, the firm said an automatic bot accessed their server, cleared the database, and left a ransom note behind. The database seems to be a PostgreSQL instance.
Company left server exposed online
The attacker’s bot was capable to access the database because the corporation engineers left remote connections allowed for the database server from the development phase.
“Due to the hectic and unplanned September migration, we didn’t have everything bolted down yet, which led to this situation,” an R6DB spokesperson said. “They left a nice ransom message, but we have no understanding to believe that they kept any data. On top of that our reserves are useless since they didn’t work on the Postgres codebase yet.”
R6DB said the intruder only entered the database, but they chose to wipe and reinstall the entire machine, just to be safe.
Company technicians are working to restore as greatly of the data as possible, but R6DB expects some data to be lost for good.
Staff says they nevermore stored any personal data on Rainbow Six Siege players, so setting users don’t have anything to worry about.
All that was lost is player statistics. Gamers used R6DB specifically for this purpose, to keep track of their growth across time, and get the different perspective on their stats, besides to what the game gives.
“We basically lost all our traditional data,” said R6DB. “Some profiles are gone. We can re-index them while searched for, but that’s a step we can’t-do ourselves.”
“Progressions are They’ll fill up again over time, but the past is gone,” R6DB said. “aliases are half-REDACTED. We still have some older data, but about a weeks worth of aliases is lost.”
At the time of reporting, the R6DB is up and running, but the company is still operating on restoring player data. Staff expects to close the restoration process by Monday.
Take your time to comment on this article.