Skip to content

Build Process

Chris Ross edited this page Sep 4, 2017 · 2 revisions

Building Remote Recon

Barring any missing dependencies or files from the project, you should be able to open the solution and build right away. You may have issues with IntelliSense if it cannot locate the mscorlib.tlh typelib file. I've included that file in the solution root directory, so you only need to copy it to the appropriate location. There is a specific build order for all of the projects in the RemoteReconKS solution. There are post-build events for each project that are necessary.

Build Order

For RemoteReconKS, the resulting class library is converted to a byte array and copied into a header file for the Native project. This is all done with powershell and the New-RemoteReconHeader.ps1 script (adapted from here)

RemoteReconKS Header file.

When the Native build is complete, powershell is used to base64 encode the class library and place into the $Nativex86/x64 variable, within the RemoteRecon.ps1 script. Lastly, RemoteReconCore is converted to a jscript payload using DotNetToJScript. You can view the flags used with that tool to generate RemoteRecon.js . The large base64 encoded blob is the only portion of the js file that needs to be copied into RemoteRecon.ps1 .

RemoteRecon js and ps1

RemoteRecon is now fully weaponized and ready to use. Of course you can skip this entire process and use the pre-built RemoteRecon.ps1 script :)

Building Remote Recon

  1. Home
  2. Dependencies
  3. Build Process

Using Remote Recon

  1. Installation and Execution
  2. Capabilities
Clone this wiki locally