Prevent "LocalScripts" from being decompiled

The very cool, awesome, syn-“based” decompiler “UniversalSynSaveInstance” is out and many unique!! executors are using it but an easy trick can easily stop your “localscripts” from being decompiled.

Create a script and change it’s RunContext to Client. That’s it.
You can still access client-only properities like LocalPlayer



image

13 Likes

Has this been tested? It’s weird how simple it is.

2 Likes

Yes, the two last screenshots are from decompiled file that had Scripts with Client RunContext.

2 Likes

I haven’t looked over the source code of that decompiler but from the “error” message it seems to just skip over Scripts. Meaning it can still get the Source, but just chooses to go over it since it doesn’t check for RunContext?

3 Likes

Unsure but the read me had Xeno 1.1.0 in it.

3 Likes

it’s still a client script so maybe with an updated version of dex viewing these will be possible when they check for runcontext too. Or maybe it just won’t work. hopefully no

2 Likes

Pretty sure “dex” currently checks if the script it’s decompiling is a literally a script, it ignores the runcontext (pretty sure u can bypass this by making a custom mod of dex or something)

2 Likes

This is not dex, i don’t know where you got that from

2 Likes

My bad homie. But still. Just make ur own fork or whatever and just change this check

7 Likes

Then Doing This Tutorial Does not work then?

2 Likes

The bytecode is still loaded into memory so its only so long before this gets fixed.

9 Likes

This got leaked a while ago but AWP.GG is the only executor I know that has fixed it.

2 Likes

Time for this to be updated and changed within 30 minutes (if it hasn’t already) because anyone can go on their github page and make a pull request.

Thank you. You truly assisted Roblox developers around the world by making this public.

2 Likes

this is not gonna work from decompile function because you still can read the bytecode

2 Likes

Interesting find however I wouldn’t be surprised if developers make a fork or the repo devs themselves patch this.

Good thing it is open source however.


Note: Saying “Prevent” is a super miss leading term here. You should instead say help prevent or reduce. There is no way to truly prevent this from happening as it is client side.

1 Like

Just want to add my own little find. I am not going to go into depth with this however but I will give slight information as I know for a fact exploit developers read these posts.


I found a potential way to prevent a script from displaying or decompiling some scripts correctly. What I mean is something like this:

Script:


print("123 hello world!")

Decompiled:

--- Blah blah blah comments from decompiler output and junk

That’s it. It wouldn’t show any kind of result or anything. You’d expect the output to be the print statement however it is not :wink:

The only executor I have tested and am messing with is currently Delta IOS. Have fun and these kids are skidding again :confused:


EDIT 1

I figured out a way to not only kick the client as soon as they join but also have it even work around anti kick scripts too.

Here is a proof of concept video. I will NOT be sharing the script or making the place public.

1 Like