Skip to content
PoC for proxying COM objects when hijacking
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
TestCOMClient Removed PostBuild event Aug 30, 2019
TestCOMServer Fixes bug with FindOriginalCOMServer Sep 10, 2019
COMProxyTesting.sln Initial commit Aug 29, 2019
LICENSE Initial commit Aug 29, 2019 Update Aug 29, 2019


A COM client and server for testing COM hijack proxying. If you are running a COM hijack, proxying the legitimate COM server may result in better stability, thats the idea around this PoC.

This also provides an example in-process COM server DLL that can be taken and modified for your tooling. This implementation will read whatever COM CLSID is being hijacked, attempt to find the legitimate path in HKLM\Software\Classes\CLSID, and proxy the COM interface so the COM client receives the expected pointers.

How to setup the test case?

Build both projects. The TestCOMClient will create a WScript.Shell object and run calc. The TestCOMServer is a COM server DLL that will start a thread printing to the screen every second.

Run this in a .reg file for the hijack:

Windows Registry Editor Version 5.00

@="Test Hijack"

You can’t perform that action at this time.