Profile Picture

stan2012

Reputation: 37 [rate]

Joined: Mar, 2018

Last online:

‏‏‏‏‏

Bio

</>

Badges

badge badge badge

Etc

Send Message

Threads List
Possible Alts

Activity Feed

Replied to thread : these bot threads are so annoying


on it

 

10chars

Replied to thread : WeAreDevs on an Apple Watch.


stan2012 easy dubs!!

Created a new thread : huge unicode is allowed in thread titles


https://cdn.discordapp.com/attachments/1064332722065117204/1094424530639933470/image.png

 

unicode is U+FDFD (https://www.compart.com/en/unicode/U+FDFD)

Commented to thread : [BUG] Extremely large comment text


test12 123233223﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽﷽

Replied to thread : test_bot3 (real, it's coming back)


🎉new bot 🎉

Replied to thread : [warning to you idiots] erlc logs your ip lmfao


this has been known for a while.

 

the reason this isn't patched in mainstream exploits is, you need to set the environment to something. for example: secure_call has arguments that allow you to run the function under a script's environment, but require would need a whole different arg for this to work. 

 

another reason is that it will lead to many (un-neccessary) detections. if i'm correct scriptware tried patching this in require, but their script still leaks on debug.traceback. to spoof the traceback, you have to deal with line-info spoofing (making sure it's actually a valid line or that could be used as a detection vector), and finding a script that actually calls that module, ALL IN ONE require call. you would also be having a ####-show with function blocking in general, and fixing debug.info detections.

 

other games use this strategy too (phantom forces uses it, i think?)

 

in short, just use secure_call for calling functions (this isn't the best solution as synapse's secure call sucks, but its the only thing we got), and use raw??? functions for setting, or getting.

 

Replied to thread : State which phrase is blacklisted


the banned words should be here (if it hasn't changed over the years)

Replied to thread : A way to buy WRD premium with crypto


site has shutdown

Replied to thread : [WARNING] Hyperion is coming in


there goes every linux user, hope that the jan source code breach for roblox has hyperion so it gets unironically bypassed in 5 minutes

Replied to thread : A badge is broken


i come back from the dead to update my badge

https://i.imgur.com/ZresqKT.png

Replied to thread : sirhurt detection n Dat


@atari no other exploit has that issue, ur probably using sirhurt's launcher

Replied to thread : The History Of WRD (2016-2021)


now send pics of global chat :troll:

Replied to thread : SENTI OBFUSCATOR


@69697you can still deobfuscate it with 

local oldstring = loadstring
loadstring = function(v) print(v) return oldstring(v) end

if on repl.it, you can deobfuscate it with this (extra lines added so the "platform lock" doesn't make the script error

table.clear = function() return end
warn = print
game = {}
game.GetService = function() return {} end
local oldstring = loadstring
loadstring = function(v) print(v) return oldstring(v) end

https://i.imgur.com/uTguyKA.png

Replied to thread : SENTI OBFUSCATOR


"good"

loadstring = print on the top of the script will literally deobfuscate it

(game = "a" added so i could actually run it in repl.it)

https://i.imgur.com/pIlbPHC.png