Termination Exploit (Targeted)

[xvywop (JJCavalli)]

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:

Exploit Allowing False Account Terminations

Exploit Allowing False Account Terminations – Needs Urgent Attention Recently, a major issue has surfaced in the Roblox community where malicious users have found a way to falsely terminate innocent accounts. What’s even worse is that they’ve turned this into a service, allowing people to pay for the wrongful termination of other users. This is an extremely dangerous exploit that needs to be addressed immediately. How This Exploit Works False Reports & System Abuse – The exploiters use a me…

---

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:

Termination Exploit (5 Accounts Deleted)

A quick Follow-Up, there was another person by the name of kstarvibez who was terminated for his Starter Place, he has never edited any of his experiences yet still received a termination for the same reason as everyone else. This alone should signify the invalidity of those moderations. [image]

Termination Exploit (5 Accounts Deleted)

Hello, I had previously posted a thread on X about this issue and while the initially affected victims were unterminated, the method itself was not patched - it seems “TTTT” and “user091441” are still misusing some moderation vulnerability to falsely terminate people for money. I am unsure whether I am allowed to add a link to an X post so I will attach this image of it instead. [image] Other affected people are: bmwg80owner paranoid829 IIlIlIlIlIlIlllIllI bunny3839344 onlyrealbunny monerom…

---

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:

Roblox's Moderation Needs To Be Fixed

[image] Roblox bizarrely moderated my group, “Empire of the British Isles”, and and gave me a one-day ban. The appeals people took longer than a day to reply, and when they told me my ban was false and that it would not affect my account in the future, they forgot to fix my group. It’s now been over four days and we have lost nearly 1,000 members over this, which is about one to two months worth of growth. It’s incredibly frustrating to lose months of work due to a Roblox error. I have been em…

Roblox Support needs to be reworked

We’ve all heard of it before: Roblox Support. Roblox Support has been bad for as long as I can remember. I have been on the platform since 2012, and the reactions from everyone I know and everywhere I go about support have stayed the same. A terrible service, more than often incapable of solving the problems presented to them. For the sake of this post, I will not ramble about the awful specific user situations that have occured with Roblox Support over the years. Instead, I will include a lis…

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

[xvywop (JJCavalli)]

@Hooksmith apparently its not critical, is there any updates about this? someone abusing an exploit to terminate whoever he wants is not critical to you?

[xvywop (JJCavalli)]

Update:

Exploit Allowing False Account Terminations

According to this reply, it might be exactly what I was guessing. This isn’t a bug that can be fixed — Roblox’s moderators just need to be smarter and realize from the tab that the one spamming the text in-game is someone else, and that it’s not part of the game content. If necessary, they should even take that person’s username and have them moderated.

the exploit in question

[xvywop (JJCavalli)]

UPDATES:

https://devforum.roblox.com/t/crosswoods-mass-ban-problem/3654144/2?u=xvywop

[CraX_573]

Crosswoods is unrelated, that’s just Roblox refusing to fix a multiple year old vulnerability.

[Davey_Bones]

If I had to guess, this is probably abusing something related to the issue that’s causing people with new or empty places to be banned. People noticed they would get banned if their game was reported for “Sexual Content”. It was also banning people randomly for just publishing empty games supposedly. I assume that issue hasn’t been fixed and is now being exploited somehow since it seems pretty coincidental that this is coming up shortly after that issue. That issue at first was (and likely still is) incorrectly attributed to Adonis, but it seems to happen with or without Adonis so it seems more like a general issue with Roblox’s moderation stuff.

Note that my assumption is just an assumption with no concrete proof of anything, but this and that issue being related seems very likely to me.

I wouldn’t be surprised if this termination service is something simple like having bots report places owned by the target for “Sexual Content” with screenshots of something totally random (supposedly this was a condition for the self ban thing) and it’s triggering some sort of auto takedown likely in an effort to crack down on NSFW experiences since it would be faster than humans would be able to manually review them. Basically, erring on side of caution and being overly harsh even if a place has nothing ToS breaking in it.

I any event, this sounds pretty serious and given recent seemingly related events, I don’t doubt the validity of this. The radio silence from Roblox in both cases tells me they either aren’t paying enough attention and are incorrectly dismissing both issues, or more likely, they know it’s an issue and are avoiding saying anything publicly about it while behind the scenes they’re scrambling to figure out the cause and how to fix it. In a thread about the mentioned related issue, they made a statement saying Adonis and other such tools were not a violation of ToS but that people abusing them to violate rules would be banned. The message to me sounds like it was a very PR way to say admin systems wouldn’t get you banned unless you abuse them, but didn’t altogether say there isn’t an issue causing false bans… I’m guessing they couldn’t totally ignore that thread but also didn’t want to say more until they finish investigating and correcting the real issue.

[AnEngma]

Hey @xvywop! Thanks for reaching out.

We hear your frustration regarding the silence on these issues. This has actually undergone intense discussion internally over the last few days, but we were reluctant to communicate too early before a fix for the exploit was in place to avoid encouraging further abuse. But we acknowledge that our delayed communication was unfair to the community, and we’re actively reviewing our processes to ensure better and more timely responses going forward.

As of now, the exploit has been fixed and the accounts that were impacted have been restored. Please reach out if you continue to see this or other issues come up!