Hi everyone,
I’m Delus, a Roblox developer, 3D artist, and event producer specializing in brand integrations. You can find more about me and my work on Twitter/X.
I’m posting to request assistance with two account compromises, the loss of my items and Robux, and an ongoing issue preventing me from accessing places in Roblox Studio. Roblox is my primary source of income, and these incidents have significantly affected my ability to work and meet project deadlines.
The compromises appear to be connected to the reported PlayStation Network API security issue described in this post by RoUtilityNews. However, I cannot independently confirm the method used, and I would appreciate Roblox investigating whether this vulnerability was involved.
The first compromise occurred while I was away from my computer. I became aware of it approximately two hours later and discovered that I had been logged out and could no longer sign in with my usual password.
After regaining access, I found that all of my Robux were missing. I reset my password, logged out all other sessions, and contacted Roblox Support. Support successfully restored the missing Robux.
This was particularly concerning because I had security measures in place and had been careful about protecting my account. Approximately a week later, someone shared the RoUtilityNews post with me, which appeared to offer a possible explanation for how the compromise had occurred.
The second compromise happened approximately one month later. Someone contacted me on Twitter to ask whether I was selling my Roblox account in a Discord server.
I discovered that the person who had previously compromised my account had linked their Discord account to my Roblox account, allowing them to present themselves as its owner. Alarmed, I reset my passkey and changed the email address associated with my Roblox account.
Through the Discord server, I was also able to identify and contact the individual. They sent me the message, “I saw ur email when u reverted it.” Shortly afterward, I was logged out of my Roblox account again.
During this second incident, my username was changed to a seemingly random name, my limited items were taken, and additional Robux were spent on tradable items in various experiences. I suspect those items were transferred to the attacker, although I cannot verify that.
Friends helped me reach someone at Roblox, and my account was deleted as a protective measure to prevent further unauthorized changes. I was especially concerned about the projects and places accessible through my account.
I subsequently contacted Roblox Support and recovered access to the account. However, my username and avatar had been changed, my limited items were missing, and my Robux had been depleted. When I requested restoration of these losses, Support declined because I had already received a restoration following the first compromise.
The ongoing Studio issue became apparent the following day when I attempted to resume work. Whenever I try to open a place in Roblox Studio, I receive this error:
I have been unable to access any of my places. So far, I have tried:
- Reinstalling Roblox Studio.
- Restarting my computer multiple times.
- Using different devices.
- Completely resetting my Studio settings, following instructions provided by Roblox.
None of these steps have resolved the issue. It began after the second compromise and account recovery, although I do not know whether those events are directly related.
This has caused substantial delays across several active projects. Beyond the loss of my items and Robux, the inability to access Studio is directly affecting my livelihood and my commitments to clients and collaborators.
I would greatly appreciate assistance with:
- Investigating and resolving the Studio access issue so I can resume work.
- Reviewing the second compromise and reconsidering restoration of my limited items, Robux, and original username.
- Investigating how access was regained after I updated my security details, so I can be confident that my account is secure.
A private message is associated with this bug report