Unpacking/Deobfuscating a .NET application protected with Crypto obfuscator v5.x

[bball0002]

Originally Posted by franckypic

-So as kao said I have to rip 2 full classes and one managed ressource to create a cryptor / decryptor.

You do not need to do this. CryptoObfuscator's string decryption is supported by SimpleAssembly Explorer. You can of course make a string tool for practice, but it really is not needed as it is already done.

[Nehmia]

Hi Kao,

I've been waiting for your reply for so long now. I'ven't been able to solve the errors by myself. Could you please give me a hand on this since you've pretty good experience with these things? Please, i would really appreciate it if you can give me an advice or comment on the problem I posted before.

Thanks in advance

[bball0002]

SimpleAssembly Explorer has a control flow deobfuscator. Just use that. You can deobfuscate to analyze code, and then you can patch the same method in the obfuscated exe.