Hello everyone,
I’m writing this on behalf of all developers who have been affected by the ongoing exploit targeting Roblox users, particularly developers, community leaders, and bots (lol), I’ll break down what’s happening, who is behind it, and why this demands immediate attention. Let me get into this:
Firstly. Who Am I?
I’m a player in a football/soccer genre community on Roblox called MPS. That hosts different leagues and games, with one of the biggest and longest-standing league recently suffering a coordinated, targeted attack.
Why? Simply because certain individuals who were previously banned, whether for exploiting, community violations, or even serious offenses like pedophilia; decided to retaliate. These bans were not issued without reason.
What Happened?
On [May 12, 2025, 12:38 PM], the lead developer and owner of the largest, oldest MPS league “OssieNomae” was wrongfully terminated from Roblox. Shortly after, the chairman and other developers were banned as well. Two days later, even the automated bots used only for Discord-based group request handling were deleted, despite never chatting or uploading games.
This is when it became clear:
This wasn’t a random wave. This was a targeted takedown.
After digging deeper, we found a post from @Zenuux confirming that many other indie game owners and known community developers have also been hit by this.
Suspiciously, a previously inactive league within the same MPS community became active again just two days before Ossie’s ban. Coincidence? Doubtful.
Accounts Wrongfully Terminated
Here are some of the accounts that were terminated without clear explanation:
OssieNomae – Ossie - Roblox
PRS_AudioBot – PRS_AudioBot - Roblox
PRSRequestBot – PRSRequestBot - Roblox
For full context on the PRS situation, here’s a detailed post:
Termination Exploit (5 Accounts Deleted)
Another related case:
The Bigger Problem: Roblox’s Communication
This post isn’t just about PRS. It’s about something bigger:
The absolute lack of real communication from Roblox during serious incidents like these.
When someone’s account is falsely deleted, especially developers and bot accounts, we’re met with:
Generic AI replies
“Resolved” messages that are blatant lies
Zero transparency
No updates
No human communication
It’s now been 5 days since Ossie’s ban, and we haven’t received any proper response from Roblox support. Nothing. Not even a public status update.
More Cases of False Terminations
These aren’t isolated incidents. Here are more cases involving the same exploit:
What We Found
Through Discord, I was contacted by someone who risked a lot by providing screenshots and internal evidence showing pricing, services, and the users behind these false terminations.
Evidence:
This Also Hit Twitter
A related post calling attention to this issue made it onto Twitter:
Final Thoughts
I’m writing this out of frustration, anger, and deep concern. We are tired of being ignored. Roblox’s developer ecosystem is growing, but your response system is failing. When bad actors can abuse exploits to delete innocent accounts, and we have zero human interaction or recourse, that’s a massive problem.
We’re not just usernames and IDs. We’re people. We build your games. We run your communities. We are the reason many players stay engaged on your platform.
All we ask is:
- Transparency
- Direct human support
- Real investigations
- Immediate responses when dev accounts are wrongly terminated
Please, if you are a Roblox staff, a DevForum moderator, or someone with connections inside Roblox or medias that could give us visibility, help us bring this to light. We need to be heard.
Thank you.
More cases regarding moderation:
Expected behavior
The accounts, especially those associated with development and automated group management bots, should not be vulnerable to false termination exploits. If everything were functioning properly, developers and innocent users would not be targeted and banned without cause, especially without a clear explanation or transparent appeal process. I also expect that once an account is wrongfully terminated, it should be promptly investigated by a real staff member, and the issue should be resolved quickly with the affected account reinstated.
A private message is associated with this bug report