[QUESTION] Should you obufscate a exploit when releasing it?

well i casually dont obfuscate my exploits, i dont really care if ppl are skidding since u can expose them easily + most obfuscators (not all, example .net reactor) use alot of cpu and gpu at the highest obfuscation 

@Lxnnyy delta is obfuscated?

@SirWeeb nope

@Lxnnyy

well of course you wouldn't care over skidding as some of it isnt your code (ducxy's treeview?)

https://cdn.discordapp.com/attachments/875744980201779210/882734525938028564/unknown.png

@Lxnnyy alr ill just dont obfuscate it, putting a giant text saying "my code is messy as idk what" will be better lol ty for the reply tho

@Zera theres credits for ducxy in this + i bought a src of ducxy with this treeview so i dont think thats a problem?

@Lxnnyy I swear last time I used delta it said .net reactor

@hookfunction people will skid so I do recommend obfuscating also, I got blackmailed with my Novaline source once so yeah I don't think you want that happening to your exploit

@SirWeeb hmm weird, when littlekiller updates delta he obfuscates it but he uses yeetfuscator

@SirWeeb thats weird, what obfuscator do you recommend?

@Lxnnyy i would use yeetfuscator but i belive its 35 dollars

@hookfunction I recommend .net reactor if you're looking for a free one https://www.eziriz.com/dotnet_reactor.htm

Tbh Obfuscation Isn't Really Needed Depending On What You Have Tho Since Nihon Has A Key System I'd Rather People Not Instantly Bypass So I Obfuscate But If You Have Stuff That Really Isn't Dependent On Stopping Bypassing, Or Breaking Then Ig Obfuscation Really Isn't Needed

If you're releasing an exploit with good functions, a key system (custom), or anything that could be skidded and is actually good then yes. For safety. I can give you a cracked CryptoObfuscator (you can find it on the web) if you want. Nertivia only sadly.

iComet:3221