threadtear VS obfuscator

If you're very paranoid, Threadtear does have some amount of protection against potential code execution when decompiling, although it hasn't been updated in a while and it's still always a risk (albeit one I never personally encountered). If you suspect that the file you want to decompile does have a way to execute code when decompiling it, you could try using a virtual machine for some added protection.

I used recaf for the plugin.yml, I used deobfuscator to remove the obfuscation, then I used threadtear for decompilation. I use threadtear pretty much always, but it's allatori deobfuscation is somewhat lacking which is why I used a separate program. Also it does not show resources in the jar, which is why I had to use recaf.

learn java then get https://github.com/GraxCode/threadtear read all files be weary if its obfuscated

I messaged the offending plugin's devs on Discord. The creator of Tweakin says that the trojan detection in his plugin might be related to this issue, LuckPerms staff says that their libraries detections are either false positives or another plugin infecting LP libs and IV dev hasn't responded yet.

Allitori is the easiest shit to deobf Use Superblaubeere27 obf, it is still easy to deobf but easier for skids like you to use https://github.com/superblaubeere27/obfuscator

i personally find https://github.com/superblaubeere27/obfuscator on default settings to work well. alternatively, you can use https://github.com/sim0n/Caesium too.