Need help with MemJect?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

226 Stars 67 Forks MIT License 41 Commits 12 Opened issues


Simple Dll injector loading from memory. Supports PE header and entry point erasure. Written in C99.

Services available


Need anything else?

Contributors list

# 2,218
36 commits
# 407,116
1 commit

MemJect C Windows x86 License

Simple dll injector designed to load dll from memory. Supports PE header and entry point erasure. Written in C99.


  • load dll from byte array in memory, without storing dll file on disk
  • decrypt encrypted dll buffer
  • erase DLLEntryPoint
  • erase PE header

Getting started


C99 compiler for Windows is required in order to compile MemJect. Microsoft Visual Studio is required to load solution for easy compilation (MemJect.sln).


The very first step in order to compile MemJect is to clone this repo from GitHub to your local computer. Git is required to step futher, if not installed download it here. Open git bash / git cmd / cmd and enter following command:

git clone
folder should have been succesfully created, containing all the source files.

Compiling from source

When you have equiped a copy of source code, next step is opening MemJect.sln in Microsoft Visual Studio. If you don't have Visual Studio, compile MemJect.cpp using your compilator.

Find below line in MemJect.cpp and replace csgo.exe with your destination process name: ```c

define PROCESS_NAME "csgo.exe"

Find below line in **MemJect.cpp** and supply your dll in form of byte array there.
You can use [my python script]( to convert dll to array of bytes or almost any hex-editor with `export to C` function.
static const uint8_t binary[] = {
0x4d, 0x5a, 0x80, 0x00, 0x01, ...

Then change build configuration to

Release | x86
and simply press Build solution.

If everything went right you should receive

binary file.


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.