Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
October 11, 2021 18:42
December 21, 2017 00:03
October 11, 2021 18:46
June 12, 2020 19:49
September 27, 2017 01:04
June 12, 2020 19:49

Chat Support


BlobRunner is a simple tool to quickly debug shellcode extracted during malware analysis.
BlobRunner allocates memory for the target file and jumps to the base (or offset) of the allocated memory. This allows an analyst to quickly debug into extracted artifacts with minimal overhead and effort.

BlobRunner Sample

To use BlobRunner, you can download the compiled executable from the releases page or build your own using the steps below.


Building the executable is straight forward and relatively painless.



  • Download and install Microsoft Visual C++ Build Tools or Visual Studio

Build Steps

  • Open Visual Studio Command Prompt
  • Navigate to the directory where BlobRunner is checked out
  • Build the executable by running:
cl blobrunner.c

Building BlobRunner x64

Building the x64 version is virtually the same as above, but simply uses the x64 tooling.

  • Open x64 Visual Studio Command Prompt
  • Navigate to the directory where BlobRunner is checked out
  • Build the executable by running:
 cl /Feblobrunner64.exe /Foblobrunner64.out blobrunner.c


To debug:

  • Open BlobRunner in your favorite debugger.
  • Pass the shellcode file as the first parameter.
  • Add a breakpoint before the jump into the shellcode
  • Step into the shellcode
BlobRunner.exe shellcode.bin

Debug into file at a specific offset.

BlobRunner.exe shellcode.bin --offset 0x0100

Debug into file and don't pause before the jump. Warning: Ensure you have a breakpoint set before the jump.

BlobRunner.exe shellcode.bin --nopause

Just-In-Time (JIT) Debugger

The optional parameter --jit can be used to debug the shell code with the configured Just-In-Time (JIT) debugger. To trigger the debugger - BlobRunner removes execute access from the newly allocated memory region. This causes the program to raise an AccessViolation (0xC0000005) exception when attempting to execute the loaded shellcode.

Instructions for configuring the JIT debugger on windows can be found here. For x64Dbg see setjit or setjitauto.


BlobRunner.exe shellcode.bin --jit

Once the debugger is loaded grant executable access to the region. Using x64Dbg you can execute the command setpagerights using the address returned by BlobRunner.

setpagerights <region>, ExecuteReadWrite

Debugging x64 Shellcode

Inline assembly isn't supported by the x64 compiler, so to support debugging x64 shellcode the loader creates a suspended thread which allows you to place a breakpoint at the thread entry, before the thread is resumed.

Remote Debugging Shell Blobs (IDAPro)

The process is virtually identical to debugging shellcode locally - with the exception that the you need to copy the shellcode file to the remote system. If the file is copied to the same path you are running win32_remote.exe from, you need to use the file name for the parameter. Otherwise, you will need to specify the path to the shellcode file on the remote system.

Shellcode Samples

You can quickly generate shellcode samples using the Metasploit tool msfvenom.

Generating a simple Windows exec payload.

msfvenom -a x86 --platform windows -p windows/exec cmd=calc.exe -o test2.bin

Feedback / Help

  • Any questions, comments or requests you can find us on twitter: @seanmw or @herrcore
  • Pull requests welcome!