Resource icon

 BLAZINGPACK - Famous Polish AntiCheat Client (Deobfuscated) 80% DEOBFUSCATED

Blazingpack is an famous polish anticheat, which is pretty heavily obfuscated.
I provide an deobfuscation of it, strings are not deobfuscated.
I willl later release a full deobfuscation of this client including strings, etc. Luyten decompiler might crash a lot while decompiling it, i dont recommend it.
Cafababe editor lite, which is an byte code editor + with an decompilation feature should work well, also the names are not deobfuscated, but in next release i will do a full deobf.
Author
BlazingDestruction
Downloads
265
Views
1,663
First release
Last update
Rating
1.00 star(s) 1 ratings

Share this resource

Latest updates

  1. Okay so i did some more things read the description down below btw

    so yeah its kinda crazy how from like 55 mb this file went to 6 mb, so many trash code and trash...
  2. Another update, removed some trash code etc. Read description

    Its now really easy to read this, dont use Luyten it fucking sucks use cafabebe editor lite or...
  3. Code more readable and removed some crashers for decompilers

    The file should be decompiled more easily, still recommend using a good decompiler instead of jd...

Latest reviews

first of all -Redacted-, this is shittly deobfuscated and gives no advantage to normal jar. Secondary, you cant deobfuscate class names etc... they are irreversable changed and you cant do shit except reaming them all to Class1, Class2 etc...
BlazingDestruction
Okay! then deobfuscate this shit more and i will make an update and upload it.
2. Yes, i never claimed I can, i renamed them to Class1 etc because they were extremely long. Same with methods, they were extremely long so its easier to read it like this.
There were also a lot of crashers in this shit, trash code and invalid classes to make it much harder to reversee engineer.
There were things like also fake annotations, and flow obfuscation.
Most of these except few flow obfuscation is deobfuscated.
Only few strings are not deobfuscated, but feel free to give me their string algorithm and i will fork java deobfuscator and make an transformer for it, for some reason when i tried to copy their string encryption code, i get only ??????? as an result.
Also, the class main was encrypted and it was all heavily obfuscated, the client was 55mb. Normally minecraft client wouldnt be over 15mb no matter how much you add, and i swear they didnt add enough to make file that big. Its because of invalid classes and trash code which i removed.
So dont tell me this is not deobfuscated, when with normal jar you wouldnt do shit, also they used some sort of exploit, that you in luyten it says file not found, and in winrar it says that files dont have name, class normalizer helped with that.

Also i bet on eveything, that you used some shitty decompiler like luyten which cant even read most of classes. if you used fernflower or something good, you could read every class and the code would be actually good. you also could read 99.9% of methods.
Top