es3n1n / obfuscator

PE bin2bin obfuscator
https://blog.es3n1n.eu/posts/obfuscator-pt-1
GNU General Public License v3.0
605 stars 57 forks source link
bin2bin cpp cpp23 obfuscation obfuscator reverse-engineering windows

Obfuscator

A native code obfuscator written in c++23.

Available transforms:


Usage

Available options:
    -h, --help                   -- This message
    -pdb         [path]          -- Set custom .pdb file location
    -map         [path]          -- Set custom .map file location
    -f           [name]          -- Start new function configuration
    -t           [name]          -- Start new transform configuration
    -g           [name]          -- Start new transform global configuration
    -v           [name] [value]  -- Push value

Examples:
    obfuscator hehe.exe -f main -t TransformName -v SomeName 1337
    obfuscator hehe.exe -f main -t TransformName -v SomeName 1337 -g TransformName -v SomeGlobalName 1337
    obfuscator hehe.exe -f main -t TransformName -v SomeName 1337 -v SomeName0 1337 -g TransformName -v SomeGlobalName 1337
    obfuscator hehe.exe -map mymap.map -pdb mypdb.pdb -f main -t TransformName -v SomeName 1337 -v SomeName0 1337 -g TransformName -v SomeGlobalName 1337

Writeup


Building

This project is designed to be used on both Linux and Windows, and on any architecture. Although you may need to update your compiler/libc++ to the latest version, as we're using some fancy C++23 features.

cmake -B build -DOBFUSCATOR_BUILD_TESTS=0
cmake --build build --config Release

If you are using Visual Studio on Windows, you can generate the sln project using the first command and build the project using the generated .sln file.

Contributing

Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

Bug reporting

Before reporting any bugs that could be related to code generation, please ensure that you attach the random seed used by the obfuscator. You can obtain this seed from the obfuscator logs; it is printed as the first message and looks like this:

12:11:30.150 | [  info  ] random: seed is 0xcb91ccbef7cbcdc1

Special thanks

License

GPL-3.0