Simple detection of Xeno Injection [PATCHED]

i am sorry to inform you that your crash can be bypassed trivially via game:GetService("ScriptContext"):SetTimeout(0.1)

(although to give you credit im pretty sure the other one will be bypassed by this too lol)

1 Like

His script also only crashes because of while true do, nothing else. So no. And that’s exactly my point.

Uh, no? setTimeout(0) just defers execution; it doesn’t stop anything. A while true do loop like the one above will still run, So no, it won’t be “stopped”.

Yes, and? Why does it matter if it’s just being deferred? It’s just filling a table and letting it get garbage collected immediately. That’s not going to cause a crash. What’s really causing the crash is the while loop, and nothing but the while loop.

And anyway, the bypass goes like this:

Try making a plugin and see if it crashes studio when you use this bypass.
Spoiler: It doesn’t. That’s because only the infinite while loop is causing the crash.

Xeno have seriously fixed the vulnerabilities for detection, it could probably be a re-debug of their code, or some modifications to the dll interface. But Xeno interacts strongly with ThirdPartyUserService, adding its own stack indicators to it, the service is initially created in ROBLOX and without injection, does anyone have any options to detect it? I tried to do detection via strong references for weak tables, but all to no avail. Any options to detect via getfenv() with calling multiple stack levels and make a trap?