DotNetHooking

Introduction

This project demonstrates how to use the .NET native code hooking technique. For more details of the technique, see the attached presentation slides.

Source Navigation

The high level flow of this code is:

This assembly is loaded via a mechanism of AppDomainManager
The HookScanContent class is instantiated registering an assembly load event handler
When System.Management.Automation, which contains implementation of our target method "ScanContent", is loaded, this assembly locates its native code address and installs a hook on it to redirect to the ScanContentHookHandler method
When PowerShell content is executed and the ScanContent is called, our ScanContentHookHandler is executed instead of original ScanContent

Hints

Few things worth noting:

This project targets .NET 2.0. This lets this assembly be loadable on practically any platforms since .NET Framework 2.0 is installed by default since Windows 7, and such an assembly can be loaded into a process using a newer version of .NET Framework. Therefore, such an assembly can be loaded into through PowerShell v2 to v5 universally.
This assembly is signed and compiled as a strongly named assembly. This allows this assembly to be registered with Global Assembly Cache (GAC). Registering with GAC is required to load this assembly into any process because CLR cannot find this assembly when this assembly is registered as an AppDomainManager but not located in the folder where an EXE file of the process exists or GAC either. Registering this assembly with GAC allows CLR to find it regardless of where the EXE file exists.
Code in this project intentionally emits error checks or exception handling. One using this code should add error handling as necessary.

Installation

As noted above, this assembly must be registered with GAC or located in the same folder as a target executable file (powershell.exe, in our case). While registering with GAC will be required in the real use cases, skipping registration is more convenient for debugging and testing. The below is the instructions for both ways:

No GAC Installation (+ testing with locally copied powershell.exe)

Build the solution with Visual Studio 2017
Launch the command prompt and navigate to an output folder
```
> cd <Folder where the DLL was built>
```

Copy powershell.exe to the current folder for testing

> copy C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe . /y

Set environment variable to specify a custom AppDomainManager

> set APPDOMAIN_MANAGER_ASM=HookingAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8b8e7ea5047757d, processorArchitecture=MSIL
> set APPDOMAIN_MANAGER_TYPE=HookingAssembly.CustomeAppDomainManager1

Start the copied powershell.exe

> powershell.exe
[*] AssemblyLoad event handler registered.
[*] Loading assembly System
[*] Loading assembly Microsoft.PowerShell.ConsoleHost
[*] Loading assembly System.Management.Automation
[*] The ScanContent method has been hooked.
Windows PowerShell
Copyright (C) Microsoft Corporation.All rights reserved.

GAC Installation (+ powershell.exe)

Build the solution with Visual Studio 2017
Launch the elevated command prompt for Visual Studio 2017 and navigate to an output folder
```
> cd <Folder where the DLL was built>
```

Install the assembly to GAC

> gacutil /i HookingAssembly.dll
Microsoft (R) .NET Global Assembly Cache Utility.Version 4.0.30319.0
Copyright (c) Microsoft Corporation.All rights reserved.

Assembly successfully added to the cache

Set environment variable to specify a custom AppDomainManager

> set APPDOMAIN_MANAGER_ASM=HookingAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8b8e7ea5047757d, processorArchitecture=MSIL
> set APPDOMAIN_MANAGER_TYPE=HookingAssembly.CustomeAppDomainManager1

Add the current folder to %PATH%, so that the hooking DLLs can be found
```
> set PATH=%PATH%;%~dp0
```
Start powershell.exe
```
> powershell
```

To uninstall the assembly from GAC:

> gacutil /u HookingAssembly

Simulate Detection by AMSI

On the hooked PowerShell session, run this command: