Today, I’m releasing a detection method for the getcustomasset function used by exploits. Some exploits, like Xeno (lmao), even use this function during injection. Because of that, you can also consider this an injection detection method.
When and how you run this is entirely up to you. Put it in a loop, tie it to some trigger, whatever fits your game’s performance model.
local ContentProvider = game:GetService("ContentProvider")
local CoreGui = game:GetService("CoreGui")
local RobloxDefaults = {"avatar", "configs", "fonts", "models", "sky", "sounds", "textures", "LuaPackages"}
local Analyze = function(AssetId)
local NewId = AssetId:match("^rbxasset://([^/]+)")
if NewId and not table.find(RobloxDefaults, NewId) then
return true
end
return false
end
-- Run this in a loop or based on custom conditions — it's your job to optimize.
ContentProvider:PreloadAsync({CoreGui}, function(Id)
if Analyze(Id) then
print("getcustomasset Detected!") -- CHANGE THIS
end
end)
I know this method is easy to patch but its working currently. Good luck catching skids while it lasts. Note: Don’t forget to secure your PreloadAsync from hooks.
Time to wait for the 3 way argument between the people who say “Don’t you know leaking detections will just get them patched faster??”, the people who say “Client anticheats are useless”, and the people who actually think this is useful - that seems to appear on every topic like this…
Anyway, thanks for the detection, no matter how quickly it gets patched or how easy it is to spoof, it’s still a detection that could help to catch skids. Really inexperienced skids, but still skids. Thanks for posting it!
is it false? no, the OP post makes this even more apparent:
You children are incredibly disappointing. Instead of releasing these kinds of powerful and effective stopgaps for free on this forum primarily full of skids, you could have been selling these to top developers or simply making your own games secure using them.
Wasted potential.
This is the most horrendous detection method if it even works on any current executor (Xeno is literally extinct).
If you actually wanted to detect something, you could’ve done a service check or a reference check as some versions of Dex Explorer and IYFE and even some exploits are still vulnerable to. This includes the extinct Xeno.
