AWP Executor Inject detection [PATCHED]

Resources Community Resources
#1 
-- (This isnt fake btw)
local ContentProvider = game:GetService("ContentProvider")
local connection

connection = ContentProvider:GetAssetFetchStatusChangedSignal("rbxasset://awp"):Connect(function(arg1)
    if arg1 == Enum.AssetFetchStatus.Success then
        connection:Disconnect()
        print("Detected AWP")
    elseif arg1 == Enum.AssetFetchStatus.Failure or arg1 == Enum.AssetFetchStatus.TimedOut then
        connection:Disconnect()
    end
end)

ContentProvider:Preload("rbxasset://awp")

This has already been reported to AWP Developers, so it will probably be patched very soon

16 Likes
#2

Interesting! This same detection works for the Argon exploit, you must change the asset from “rbxasset://awp” to “rbxasset://argon”.

5 Likes
#3

Works for Seliware too, replace //awp with //SELIWARE

2 Likes
#4

This has been a known AWP detection for about 2 months now, AWP likely won’t patch it soon due to how it’s a required folder for their assets so its safe to use in games.

1 Like
#5

It’s not “safe” for them if it’s this easy to detect. :cry: :broken_heart:

1 Like
#6

AWP’s very unsafe in general, I found a vuln for it on accident using debug.profilebegin to put hundreds of 200-500MB files on an AWP users pc but you could probably get fined for doing that to them.

3 Likes
#7

Make that 200-500 GB and then I’ll start to feel bad for them. This is self defense, so a fine wouldn’t make sense in my opinion.

2 Likes
#8
  1. Will never understand how exploits are susceptible to detections like this…
  2. How are detections like this even found?
2 Likes
#9

vouch
exploiter count went from 1 billion to -5 in 2 minutes

1 Like