Jump to content
Tuts 4 You

[Help] DotNetPatcher 4.4.2


Modify

Recommended Posts

  • 3 weeks later...
27 minutes ago, man of the war said:

0.png

Features

Here's a pseudo list of the things which are currently supported with DNPDeobfuscator :

  • String Encryption
    • String Encryption
    • String Encryption + Resource Encryption
    • String Encryption + Resource Compression
  • Integers Encryption
    • Local decryption
    • Dynamic decryption
    • Resource decryption
  • Resource Encryption
  • Resource Compression
  • Invalid OpCode -> I cheat on this one, nobody use it since it makes your file crashes.
  • Prune useless Methods / Types
  • Call Hiding
    • Call Hiding with Integers
    • Call Hiding with Strings

HowTo

  • Remove Invalid Metadata - > De4Dot does the job
  • Clean constant calculation -> Uses my constants tool pack
    • Use AppFuscatorConstantFill2.exe
    • Then use AppFuscatorOperationCalc.exe
    • Then use de4dot
  • Now you can use DNPDeobfuscator.
Link to comment
  • 1 month later...

DNPDeobfuscator and AppFuscatorConstantFill2.exe not working :-

DNPDeobfuscator :-

some DNP options disable and protect 30 kb assembly, try to unpack show Decrypt String error

Capture.JPG

 

AppFuscatorConstantFill2.exe :-

500 kb protect assembly show error

Capture1.JPG


 


 


 

Link to comment
  • 4 weeks later...

Easy solution: If is your own app you can take a look in the source code and delete parts of it,

obfuscate and repeat until you know what part of the code make the app crash when obfuscated,

then code the same function in a different way.

Edited by Reasen
Link to comment
  • 4 months later...
On 2/22/2016 at 6:44 PM, XenocodeRCE said:
 
 
 
 

 

On 2/23/2016 at 11:02 AM, ghostfish said:

Features

Here's a pseudo list of the things which are currently supported with DNPDeobfuscator :

  • String Encryption
    • String Encryption
    • String Encryption + Resource Encryption
    • String Encryption + Resource Compression
  • Integers Encryption
    • Local decryption
    • Dynamic decryption
    • Resource decryption
  • Resource Encryption
  • Resource Compression
  • Invalid OpCode -> I cheat on this one, nobody use it since it makes your file crashes.
  • Prune useless Methods / Types
  • Call Hiding
    • Call Hiding with Integers
    • Call Hiding with Strings

HowTo

  • Remove Invalid Metadata - > De4Dot does the job
  • Clean constant calculation -> Uses my constants tool pack
    • Use AppFuscatorConstantFill2.exe
    • Then use AppFuscatorOperationCalc.exe
    • Then use de4dot
  • Now you can use DNPDeobfuscator.
 
1
 

Ya'll not getting what this section of the forum is about, it's about protection and security enhancement, and for whatever reasons ya'll writing stuff like if saying: "Don't protect with DNP cuz DNP is sht" or "shts will always be cracked" or something similar between those lines, or at least that's how I see your replies to this thread... 

My way of thinking is that if you really have nothing to contribute to this secton or thread more specifically don't just comment at all, is rude to go on someone's thread that's looking for help and ya'll start posting only about opinions and not helping at all.

Btw no hard feelings, Just my 2¢ :)

<hr>

@OP, just like Cawk suggested removing the Invalid OpCodes feature is the way to go, you see, when you use this feature, DNP adds literally just that, invalid opcodes in order to make the assembly more troublesome to work with, this feature also brings some caveats as by itself it tends to break or corrupt the resulting protected assembly, because of the obvious invalid opcodes, for example it may add invalid opcodes at the beginning of a CTOR making it totally useless before even executing anything important, etc, etc...

Also DNP is an Open-Source project, there's nothing better than to have an open source project because you can do whatever you want with it, as long as the license allows so, also DNPDeobfuscator is also Open-Source thanks to Xenocode, you can see what it's doing in order to deobfuscate the assembly, you can then improve/enhance everything that DNPDeobfuscator is looking for and bring some countermeasures to it :D

Edited by 0xNOP
  • Like 2
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...