SCLauncher – Basic Shellcode Tester, Debugger And PE-File Wrapper

This program is designed to load 32-bit or 64-bit shellcode and allow for execution or debugging. In addition, it can produce executable PE files based on the desired shellcode.

This can ease testing as the output binary can be used by standard reverse engineering tools (i.e. IDA Pro (even free) and debuggers).

Release binaries are available. You can view a demo of this tool on YouTube

This program provides several options for working with your shellcode:

• You can use the -pause argument to pause this program before executing the shellcode. This allows for a debugger to be attached and breakpoints to be set.
  • Keep in mind that there are options available to have this utility set breakpoints for you, see the -bp argument.
  • You can produce PE files from your shellcode, then disassemble or debug them as you would a normal PE file.
  • You can run the the program directly under a debugger, providing the appropriate arguments through your debuggers interface.

Executing Shellcode From A File

The only required argument is to provide the path to the file that contains your shellcode. You do that by using the -f argument. This will be copied into memory and executed.

Additionally, you can use the -ep argument to adjust the entry point by X bytes. This allows for shellcode that does not begin execution at the beginning of the binary blob.

Finally, -bp determines if a breakpoint should be inserted before the shellcode. This will be done through a 0xCC byte, which is an INT3.

This allows you to run the program under a debugger, defining the command line arguments as appropriate.

Inserting a breakpoint will allow the debugger to interrupt execution before the shellcode is executed.

If you are not running under a debugger, do not insert a breakpoint as that will cause the program to crash.

Producing A PE File

You can use the -pe argument to produce a PE file that essentially wraps the shellcode. The shellcode is placed in the .text section.

The entry point is defined as the beginning of the section, unless the -ep argument is used.

This argument will define an offset from the beginning of the section and be used to update the PE files entry point (i.e. AddressOfEntry field).

Additionally, the -64 argument can be used to generate a 64-bit PE file, likely for 64-bit shellcode.

The resulting PE file can be analyzed via common reverse engineering tools such as IDA Pro, Ghidra or a debugger such as x32dbg/WinDbg/etc.

For more information click here