Extreme Obfuscator
Extreme Obfuscator
Extreme Obfuscator
An obfuscator for .NET assemblies. Before I begin, I'd like to point out that this is not the "best" obfuscator out there, but it's better than nothing and it's also free.
Also note that even though it says "Executable" in the picture, DLLs are supported too, I just forgot to change the name.
Before:
After:
Features:
- Symbol renaming (changes the names of types including classes, fields, properties, events, nested types)
- Multiple renaming schemes for symbol renaming: Alphanumeric, Chinese and Unprintable
- Ability to include/exclude public types for symbol renaming (useful for releasing libraries/DLLs)
- String encryption and constant encryption (constant encryption only supports integers at the moment)
- Anti-ILDASM protection (prevents ILDASM from decompiling the assembly)
As this is quite early in development (I've worked on this for a day or two), you may experience some bugs. Feel free to report them and provide me with the file causing the problem. And yes, I know it's ironic to be protecting an obfuscator with a third-party one but since this is still early in development, I'm not going to do that until it's mature enough.
Known bugs:
- Obfuscation will only work on basic WPF applications. Windows Forms, Console Application and Class Library should work fine.
Credits:
JB Evain
FatCow Hosting
Virus Scans:
https://www.virustotal.com/file/caaf...is/1356185373/
http://virusscan.jotti.org/en/scanre...01cfbeb3c4be11
Also, obfuscating a protected assembly again can make it harder to understand or deobfuscate, although it may not work for all assemblies.
An obfuscator for .NET assemblies. Before I begin, I'd like to point out that this is not the "best" obfuscator out there, but it's better than nothing and it's also free.
Also note that even though it says "Executable" in the picture, DLLs are supported too, I just forgot to change the name.Before:
After:
Features:
- Symbol renaming (changes the names of types including classes, fields, properties, events, nested types)
- Multiple renaming schemes for symbol renaming: Alphanumeric, Chinese and Unprintable
- Ability to include/exclude public types for symbol renaming (useful for releasing libraries/DLLs)
- String encryption and constant encryption (constant encryption only supports integers at the moment)
- Anti-ILDASM protection (prevents ILDASM from decompiling the assembly)
As this is quite early in development (I've worked on this for a day or two), you may experience some bugs. Feel free to report them and provide me with the file causing the problem. And yes, I know it's ironic to be protecting an obfuscator with a third-party one but since this is still early in development, I'm not going to do that until it's mature enough.
Known bugs:
- Obfuscation will only work on basic WPF applications. Windows Forms, Console Application and Class Library should work fine.
Credits:
JB Evain
FatCow Hosting
Virus Scans:
https://www.virustotal.com/file/caaf...is/1356185373/
http://virusscan.jotti.org/en/scanre...01cfbeb3c4be11
Also, obfuscating a protected assembly again can make it harder to understand or deobfuscate, although it may not work for all assemblies.
Originally Posted by master131
.
.
