[OLD, BUT WORKS] How to detect DEX Explorer

The mainstream mobile executors tend to be in general very lacking in terms of functionality, which naturally also means they also tend to be rendered unusable / detected pretty easily by an experienced developer. Your baseless claims do not prove how mobile executors do prevent the detection from working successfully.

1 Like

because most of the time the exploit scripts are the one that bypass the detection by doing hooking

1 Like

Those functions you cited are sadly extremely detectable, and can be mostly rendered useless if not preventable at all. For hookfunction, simple stack frame or cl info checks will reveal a function being detoured pretty easily, as theres no way to fully prevent the bypasses to these checks from being detected, and will rather result in additional detection vectors. As for connections, things tend to be trickier, but you should know as an informed developer that client-sided connections aren’t ideal to detect exploiters, as they can be trivially disabled, and should only be used as another layer of security against skids. Finally, decompiling can easily be stopped by obfuscating scripts, or using flaws in a decompiler where certain parts of the code / closures won’t be decompiled, although the former will usually be better.

1 Like

Demonstrate a video showing that this works

2 Likes

of course it will, but I’m developing a more reliable detection system so it will have to wait a bit

1 Like

Good point but to stay ahead is more important we need more than just clientside detection. A combo of client and serverside detection would make it harder for exploits to slip through. Maybe tracking GUI changes or comparing expected vs actual states could help. Also any ideas for catching mobile exploiters?They seem tougher to detect than the pc exploiters i think it has to do with how the device is presived.

3 Likes

Oh no…

The idea of “i can bypass!!” & “but ur detected by client ha !!88!!” is pointless and an endless back-and-forth discussion. As fond as you are about (client sided) anti cheats, at the end of the day it’s only a matter of time for it to be bypassed

Just like you said, these checks aren’t “national treasure” and well-known. Any check will be prone to being bypassed, even if you implement an additional most divine internal check lol
Even with obfuscation, which isn’t the most performant solution, you cannot stop decompilation.

The point of this reply was to emphasize that client sided anti cheats do stop cheaters, however it is only a temporary solution. Thus rendering “functions” as mostly useless is a wild & hypocritical take.

3 Likes

obfuscation gets bypassed easily by dynamic analysis

3 Likes

Client sided anti cheats are still good for detecting skids which is like 99.999% of roblox exploiters

2 Likes

dude why are you making anti cheats dude?? theyll just get patched dude like just a huge waste of time dude no point in creating anti cheats just let exploiters do anything dude it doesnt matter exploiters are gonna bypass it anyways dude

2 Likes

making optimal anti cheats isn’t really a time waste, what ur saying is without a doubt true and it would ultimately get bypassed anyways. but referencing the quote to what Sango said, all jokes aside it’s really true. for every game there are different factors, but it definitely prevents a decent percentage from cheating.

1 Like

It still would get bypassed its just matter of time all it takes is person who knows how to script instead of putting time and resources working on an anti-cheat that will probably be bypassed eventually it’s better to work on actual content and adding server checks especially since exploiting community died

2 Likes

i’m sorry, but protect_gui() is not working anymore. mostly, exploits are faking it by mkaing a folder in coregui, and putting every gui there. back then, it would make it HTML-based, because no proper anti-tamper existed.

2 Likes

also, saveinstance() can easily be detected by cool property Archivable

2 Likes

That is to prevent static analysis, not dynamic. Its up to you to prevent dynamic analysis by adding checks for detouring, op code tampering and such.

You can apply the same logic, backwards, even though you seem to discard it entirely. Any patches will be prone to being detected.

You even proved it here!

You can’t qualify something as “wild” and “hypocritical” simply because you’re unable to do so (at least that is what I’m assuming). In general, this isn’t the right mindset to further progress, and the opposite is what usually brings you success.

Where did you get that information from? It’s actually bigger than ever since Hyperion’s arrival.

EDIT: Didn’t mean to reply

1 Like

All it takes is somebody to release one script and the entire anti-cheat would be useless (unless you started spending time trying to fix the script) and even if you were to do that you can’t have a guarantee that somebody else won’t just make a new script this is why most of the experiences on roblox focus on actual content updates instead of targetting exploiters because they know its endless battle also everything done on the client can be tempered yes it can be time-consuming sometimes but it’s still possible.

Take bedwars or jailbreak or lumber tycoon 2 as example people constantly exploit their experience but they are still front-page experiences because server checks are good enough to nerf exploiters

also most of stable executors cost monthly what killed marketplace and scripts :slight_smile:

2 Likes

You’re just replying to reply, that’s LITERALLY what I started my post with… Maybe if you stopped reading posts backwards, you might’ve gotten the point of my reply. Maybe though, it’s still a hypothetical :sweat_smile:

Notice how you only see it after, I might just take back what I said as a joke. I really do think you read text backwards.

We can apply every rule of phraseology and attempt to extract any relevant information in regards to what I said, and end up with nothing. You’re non argumentative.

thanks to everyone who appeared here, but I created a new page on this topic: Anti dex [v1] [still works]

Tbf exploiting community fell off after hyperion, there arent any executor devs on roblox rn with more than 3 braincells and quality of exploits suck. Hyperion detects everything injected due to exploiter incompetency. There are a lot less exploiters rn compared to pre hyprion which is clear to anyone who played during both time periods

1 Like

I addressed your initial point directly by demonstrating how the logic applies in reverse – if bypasses are inevitable, so is detecting them. You’re dismissing this without engaging with the idea. Simply saying “you started with this” doesn’t invalidate the argument. If you feel I misunderstood something, you’re free to clarify, but sarcasm doesn’t contribute to the discussion.

Acknowledging that the conversation is cyclical reinforces my point. Whether you take it as a joke or not, the reality is that both bypasses and detections are part of an ongoing process, not a one-sided inevitability as you implied earlier.

It seems ironic to accuse me of being non-argumentative while sidestepping the actual points I made. If there’s something specific you disagree with, address it directly instead of dismissing the entire reply. That would make for a much more productive discussion.

At the end of the day, my argument is simple: both bypassing and detection evolve constantly. Client-side anticheats aren’t perfect, but they aren’t pointless either. If you disagree, I’d like to hear why, beyond just calling the discussion “pointless.”.

That said, I will no longer be replying here, as the OP has created a new topic. Feel free to continue the discussion there if you’d like.

1 Like