A vulnerability is currently being abused on the DevForum where a particular type of content posted in a reply can cause certain threads to become extremely difficult or impossible to view. When a browser attempts to load and render a thread containing one of these replies, the page will freeze and flash repeatedly. I’ve identified multiple users engaging in this malicious behavior across multiple threads, and each one is listed in the PM attached to this report.
When opening an affected thread, the tab becomes unresponsive and the page flashes rapidly. In some cases, the browser shows an Out-of-Memory error, and system RAM usage increases dramatically. The issue persists across different browsers and refresh attempts and only occurs on threads containing the specific reply content.
This issue is triggered by specially crafted content embedded in a reply that breaks the page renderer. When the page processes this reply during load, the entire thread becomes unstable and fails to render properly, effectively making the thread unreadable and breaking your entire browser.
This is actively disruptive because it prevents users from accessing legitimate discussion content and creates the impression that the forum itself is broken. The same method appears to be reusable across different threads, meaning a single reply will make any thread it is posted under freeze or fail to load for all users.
This behavior can be observed by opening a thread that contains one of these replies, such as:
https://devforum.roblox.com/t/i-have-found-a-working-bypass-to-robloxs-age-verification/4395840/
I am intentionally not naming the users involved publicly to avoid encouraging copycat behavior or escalation, but they are listed in the PM. Multiple users have confirmed experiencing the same symptoms. Images and videos are attached showing the flashing, incomplete page rendering, and failure to load behavior when opening affected threads. Could this please be investigated as a priority, as it is currently being abused and making parts of the DevForum inaccessible.
A private message is associated with this bug report


