Holding Account for Group With 40k Members Terminated From Targeted Exploit

Bug Reports Roblox Application and Website Bugs
,
1

Recently, our holding account for our Roblox Community / Group has been terminated off the platform after being targeted maliciously.

We looked into the situation and discovered that a malicious group had targeted the holding account and had it terminated off the platform by abusing Roblox’s moderation systems.

The profile is rarely accessed compared to a normal account, and the only things it contained were a very basic and simple avatar, along with the Roblox starter place.

Our group, which contains 40k members, is now left in a state of purgatory, and we are unable to access funds, and other essential options to configure our group along with its experiences.

We hope with this bug report we can help Roblox be aware, and be able to help improve their systems thus making a positive impact on the platform as a whole, as well as resolving our situation, Roblox in the past has made some positive progress in avoiding issues like this in the past and we hope they continue to do so.

Expected behavior

Account should be accessible & have its account status re-determined by auto-moderation, along with an auto-moderation improvement.

A private message is associated with this bug report

4 Likes
2

What was the reason given for the account getting terminated? Even malicious false reports/false bans need to be about something

3

If I recall correctly, it was for inappropriate content/behavior.
The accounts only ever logged into on the website and had a basic avatar and the default Roblox place.

4

A quick update,

We’ve now identified exactly what part of Roblox’s system was abused in order to take down our holder account.

We won’t be making this information public, to avoid anybody else from attempting to use the information maliciously. We however, will be free to disclose it to Roblox Staff and have this issue situated, if you wish to contact.

1 Like
5

Our personal issue as of today has now been resolved.

However, I’m unsure of the status of future incidents.
Hopefully issues like this can be avoided in the future.