Oct 26, 2025 06:53 AM
(This post was last modified: Oct 26, 2025 08:58 AM by PhillyStyle.)
Encrypt Your Methods Inside Your EXEs! (In C# 4.8) (2)
![[Image: Method-Crypter2-Screen-Shot.png]](https://i.ibb.co/nsbwhYVv/Method-Crypter2-Screen-Shot.png)
Previous version here: https://hackforums.net/showthread.php?tid=6311470
What's New?
https://github.com/PhillyStyle/Method-Crypter-DEMO-2
Edit:
Commit base URL: (Click on browse files in the top right)
https://github.com/PhillyStyle/Method-Cr...f7b1624656
Also, if anyone wants help encrypting methods in their C# projects and is overwhelmed by all this code, private message me.
Also, (The most important thing) nobody has given me their top score in console snake yet. 🤣
![[Image: Method-Crypter2-Screen-Shot.png]](https://i.ibb.co/nsbwhYVv/Method-Crypter2-Screen-Shot.png)
Previous version here: https://hackforums.net/showthread.php?tid=6311470
What's New?
- Smaller File size:
In version 2.0 the file size of Output.exe is dramatically reduced. From about 450 KB to just 23-26 KB. This is done by not including dnlib in the Crypted.exe anymore.
- New payload injection method:
In version 2.0 we no longer use junk methods for our encryption overhead. We don't encrypt to the method space anymore at all. Instead we encrypt to base64 encoded strings and inject them into the file, then we replace the code in the methods we encrypted with stack neutral junk code. Using a binary patching method that I created.
- Output.exe no longer has to copy it's self to the temp directory to open it's self with dnlib because we don't use dnlib in Output.exe anymore. We just use memory offsets now.
- Now that there is real code in our methods, the JIT compiler gets ahead of us compiling code we don't want compiled yet, so I had to add the Force Re-JIT section to the dialog.
ForceReJit is the name of a method we use in Crypted Demo.exe, and all it does is force the Just In Time compiler to recompile code when we want it to.
ForceReJit would break if Randomize Method Names was checked, so I had to fix that.
So now in Method Crypter.exe, if you have Randomize Method Names Checked and Force Re-JIT contains a method name, it goes into your file, finds the Force Re-JIT method name string, and renames it to the new random method name string so that Force Re-JIT still works even when Randomize Method Names is checked. (I hope you can make some sense of that explanation.)
- No longer detected as a virus by Windows Defender! At the time of me writing this (10/26/2025) this method is not detected as a virus and is safe to use in your programs for encryption/obfuscation, or whatever your reason is.
https://github.com/PhillyStyle/Method-Crypter-DEMO-2
Edit:
Commit base URL: (Click on browse files in the top right)
https://github.com/PhillyStyle/Method-Cr...f7b1624656
Also, if anyone wants help encrypting methods in their C# projects and is overwhelmed by all this code, private message me.
Also, (The most important thing) nobody has given me their top score in console snake yet. 🤣


