(post derived from this with the permission of the original post creator.)
((to clarify, I did NOT make this post, merely uploaded it into bug reports since the original OP couldn’t.))
"Unfortunately, there’s a brand new way to terminate any Roblox account with an open place. The last post that came from one of the individuals whose development team was affected was unlisted & closed, which is unfortunate, but I hope to bring light to this issue with actual “evidence”, if you can call heavily a blocked out (as precaution not to spread the exploit) screenshot evidence.
Today, two developers in a development team I actively communicate with were terminated for the same vague reason, with no further explanation as to why or how, the asset linked is simple a place name & place ID:
I discovered a piece of evidence that something like this DOES exist, so we don’t seem to be the only people targeted with this type of attack. The next image will be EXTREMELY censored to prevent showing what is done & how it gets the game deleted, as well as extremely crude language put by the exploiter. This relies on an external tool, but the method at its core is far too simple! I am baffled on how hard the client is trusted, for its information to be used without human checks to terminate an account. Remember the “Crosswoods” incident? Guess it’s the reverse of it.
I will not elaborate how to replicate this in public because this is EXTREMELY easy to perform and, therefore, very dangerous, but as a safety precaution - close your public places if you feel like you may be subject to this attack.
This needs to fixed REALLY QUICK as the word is slowly spreading around and the isolated incident could turn into publicly available information. Please, if you are a staff member, ask for all the information you need, I will provide everything known to mitigate the impact, as well as a list of the known accounts who had been affected by this."
Expected behavior
given a false report, moderation should check the actual game and not the screenshot itself, however because of this exploit/flaw within the reporting system, situations like this can arise.
A private message is associated with this bug report