feat: Add stub code comments for "AntiDump" feature and enhance README.md

- Added the shellcode generation code as comments within the "AntiDump" stub for better context and understanding.
- Enhanced README.md with more detailed descriptions and an outline of planned future features.
This commit is contained in:
keowu
2025-07-13 20:05:55 -03:00
parent f647c39590
commit 508a204d21
4 changed files with 115 additions and 4 deletions

View File

@@ -2,7 +2,9 @@
**Ryūjin Protector** is an open-source **Bin2Bin** obfuscation, protection, and DRM tool for **Windows PE** binaries targeting the **Intel x64 architecture(Only)**.
![Ryūjin Protector Banner](imgs/ryujinreadme.png)
<p align="center">
<img src="imgs/ryujinreadme.png" alt="Ryūjin Protector Banner" width="80%">
</p>
---
@@ -14,13 +16,14 @@
- Mathematical Operators Virtualization(aka: Ryūjin MiniVM)
- Obfuscated code Encryption(Using TeaDelKew Algorithm)
- Anti-Debug User + Kernel
- Anti-Dump
- Anti-Disassembly(Planned)
- Troll Reversers(Exclusive)
- Anti-Dump
- Anti-Disassembly(Planned - **TODO**)
- Custom Passes(Planned - **TODO**)
---
## Goals
## Demos and Presentations
Ryūjin was designed and developed for the study of obfuscators with Bin2Bin capabilities, making it a viable project for use by third parties as well as serious information security students. This includes: Commercial Developers, Indie Developers/Cheat Developers, Anti-Cheat Developers, Malware Developers, Malware Analysts, and Security Researchers.
@@ -30,6 +33,18 @@ Ryūjin was designed and developed for the study of obfuscators with Bin2Bin cap
This is only a small demo with only one Ryūjin feature, others feature together produce a better result.
**Really Easy to Use:**
**Ryūjin** is extremely easy to use — you can choose between the GUI mode or the CLI mode. Both will produce the same result in a precise, functional, and stable way.
GUI Mode Demonstration:
![Ryūjin Protector Demo GUI](imgs/demo1.png)
CLI Mode Demonstration:
![Ryūjin Protector Demo Console](imgs/demo2.png)
For both options, you will need exclusively a PE file (Apanas, executable, for now) along with a PDB file containing the symbols for that PE file, so that you can protect and generate a new binary. Additionally, you can consult the WIKI at any time to discover other options and possibilities, such as custom passes.
---
## Getting Started