3

I'm using ILSpy to look at a .dll. A Majority of the classes are in english, but some of the classes are in the weird letters that I can't explain. I'm wondering if there is an error with the .dll or ILspy or if you it needed to be decompiled differently.

enter image description here

BenMorel
  • 34,448
  • 50
  • 182
  • 322
jackson5
  • 31
  • 1

1 Answers1

6

Because the code has been obfuscated, it's a way of making the code so hard to understand that it deters reverse engineering.

Usually PreEmptive's Obfuscation tool comes in Visual Studio, check it out. You could also try Market Place, Nuget & Visual Studio Gallery for more.

If you wish to de-obfuscate the DLL it might be possible with an old copy of the code and refactoring based on that. Otherwise you will find that Obfuscation is typically one way, eg renaming a btnSave to a1 is irreversible​.

Jeremy Thompson
  • 61,933
  • 36
  • 195
  • 321
  • Is there a way I can compared this code to an older version of the code. The old version wasn't obfuscated and I'm able to read the code. – jackson5 May 14 '17 at 02:13
  • It will be painstakingly​ difficult to compare and almost impossible to de-obfuscate, they may have even baked their own cryptography in as well. – Jeremy Thompson May 14 '17 at 02:16
  • See my edit you might be in luck with an old copy of the code and a lot of refactoring! – Jeremy Thompson May 14 '17 at 02:33