Jump to content
Tuts 4 You

EAZFuscator .NET 2022.1 Max Preset (BlackHat) - New 2022.2 Added

Go to solution Solved by ElektroKill,

Recommended Posts


EAZFuscator .NET 2022.1 Max Preset (BlackHat) - New 2022.2 Added

Update 04-June 2022
Version 2022.2

Unpack Password - BH2022.2



Old 2022.1 Info -

This unpackme is protected with latest version of EAZfuscator = https://www.gapotchenko.com/eazfuscator.net/features

Password to unpack = EAZ2022 (I made a RAR file with password protection because I was unable to upload the unpackme directly. I was getting error due to false virus alarm)

Your job is to unpack the file fully. Partial unpacking won't be accepted.


Link to comment

Hello, I have reached this point (see attached file), now what should I do ?


Link to comment

unpacked and changed the msg
used EazFixer that is why XOX ther is standing

ok i changed are little bit no vm any more now what is left is the key and the strings. then this thing is fully unpacked i hope.

Edited by Underground
Link to comment
  • Solution

Hi, I want to present two different methods one can use to change the text which appears on the button.

1. Debugging using dnSpy - This method does not require any unpacking. Steps:

  1. Eazfuscator always encrypts strings before applying the virtualization. This means that the text in the button is encrypted.
  2. Since we know the string is encrypted by Eazfuscator, we find the string decrypter method.
  3. In order to find the string decrypter, first we navigate to entrypoint (dnSpy has a handy context menu action for this). Entrypoint looks a bit like this:
    Then we navigate to the method highlighted in the image. This class should contain the following code:
    Then finally we navigate to the class highlighted in the image and find a method which looks similar to this:
    This is the string decrypter. After we located this method we can go to the next step
  4. In order to hijack and modify the result we need to place breakpoints strategically. In this case i set a breakpoint on the last occurrence of "return text;` located at the end of the method.
  5. Now that we have set breakpoints, we can move forward to actually debugging the application. To do that we press F5 on the keyboard to start debugging and click OK on the dialog prompt.
  6. A breakpoint is hit, in the Locals window we see that our return variable "text" has a value of what looks like some cryptic string.
    We hit F5 to continue the debugging process.
  7. Our breakpoint was hit again, this time the string is ".ctor". We continue to debug using the F5 key.
  8. Continue to debug until the value of "text" is "CHANGE MY MESSAGE". Now we can get to changing the value. Let's right click the "text" local and select "Edit Value".
    The context menu disappears and we can now edit the value.
    We type in out new value,
    And press enter.
    Success! the value is now changed!
  9. We continue to debug the application until the main window appears.
  10. We have successfully modified the message without modifying the file at all. Using the same method we can press the button and modify the text displayed in the message box.

2. Deobfuscate and devirtualize the file - This is much much harder and requires custom tools to be developed.

  1. After deobfuscating and renaming the file using a renamer of our choice, we open the file in dnSpy and find the code we need to change. As the virtualization has been removed this is quite trivial.
  2. We can right click the string, select "Edit IL Instructions" and modify the operand of the "ldstr" instruction highlighted to our string.
  3. We can then save the file by going to File -> Save Module and selecting the location and pressing OK.
  4. Running the modified file results in the message being changed to what we wanted.

I hope my rather easy to follow guide (for the first method) is beneficial to some people who want to learn other methods besides unpacking which can be used to change the behavior of a application!

Fully deobfuscated, devirtualized and renamed file is attached below.EAZ.deobfuscated.exe

More on unpacking and devirtualizing Eazfuscator:
For the basic protection public code is already available, e.g. EazFixer
For devirtualization, no public tools exist. Eazfuscator is pretty much a 1:1 VM so it is not very hard to restore. Only real annoyance is the equality comparison obfuscation and code encryption which Gapotchenko refers to as "homomorphic encryption" when it is really not that. It just encrypts both sides of a comparison and uses the decrypted value as the key of the code following the comparison.

  • Like 5
  • Thanks 1
Link to comment

ah ok found some dev tools for EAZfuscator ther dont work for this version ther work for EAZfuscator but not this version ther only need to updatet.
And how you found the key for the resources?
And i know so far that this tool fu with you if you us dedot because of the anti dumper dector or is that future not used in this unpackme?Damit i dit see this num 23+= with out using breakpoint and thx for that with the il instuction now i can remove the anti temper and then de4dot can be used normal

For devirtualization, yes ther exit but not for this version you ccan update the tools that exit for the old version to update that to the new version.

Edited by Underground
Link to comment
  • 2 weeks later...
  • 1 month later...

New 2022.2 Sample Unpackme Added. Everyone can try to unpack that.

  • Thanks 1
Link to comment
  • 1 month later...

2022.1 challenges was having only EAZFUSCATOR 2022.1 so after dealing with Strings, Cflow and Resources, VM was the main task. 






Some Public Resource to look for understanding more about EAZ -

EAZ De-virtualization is not so easy as It seems.
If there is Homo-morphic Encryption then It is harder even.

This challenge does not have homomorphic encryption so no need to brute force the Key and you can continue the Unpacking. For more Info, You can check the Previous solved Challenges of EAZFUSCATOR.



2022.2 challenge was stacked (not actually but somehow) as the Sample was having ConfuserEx Anti-Dump so after applying EAZ over it, One of the EAZ calls got proxified.
So If you are doing Static Unpacking, It probably would cause the issue but not in case of dynamic Unpacking.

  • You can manually fix the proxified methods and can continue the process to unpacking it. 





I cleaned the Assembly after Unpacking and Devirting so It looks nice. You can guess Symbols from the assembly itself by modifying de4dot Renamer or can do manually. in Case of Stacking (depends on How EAZ is stacked), It is not advisable to clean Assembly as It may break other protectors unpacking. 


EAZ_unp_2022.1_cleaned.exe BH_unp_2022.2_cleaned.exe

  • Thanks 1
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...