Protect .Net application from Deobfuscators? [closed]

Question

Closed. This question needs to be more focused. It is not currently accepting answers.

---

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 2 years ago.

Improve this question

I know that we can protect .Net applications from decompiling by using obfuscators.

But I read somewhere that there is some Deobfuscators (like de4dot ) that can deobfuscate .Net obfuscated applications. They can Neutralize the effect of some obfuscators like Eazfuscator.NET . So, they can decompile even obfuscated .Net applications.

Is that right? If yes, how to protect applications from deobfuscators?

Answer 1

No app is 100% protected, but the commercial obfuscators make a pretty good job of making it hard.

Answer 2

In short, you can't. You can only make life difficult for people, but ultimately, if they want to access your code, they can do.

Answer 3

Use an obfuscator to prevent this - obfuscators change the structure but not the meaning/intent of your source code so as to make it very hard for a cracker/hacker to understand the code. Take a look at Crypto Obfuscator which employs various techniques like symbol renaming, string encryption, control flow obfuscation, etc.

It also has special defenses against de4dot - if you try to run de4dot on assemblies obfuscated with Crypto Obfuscator, it will crash.

DISCLAIMER: I work for LogicNP Software, the developer of Crypto Obfuscator.

Answer 4

Why not? You can try ILProtector. It is free .NET protector. It protects .NET code using code virtualization. In this case level of code protection increases manyfold compared to obfuscation. Your code is not recognized by disassemblers and decompilers such as de4dot, IL DASM or .NET Reflector.