This is a list of known issues you may experience while using this PoC software and how to work around them.

• HIDX StealthLink - Issues / Known Challenges
  • HIDXExfil: The term 'HIDXExfil is not recognized ...
  • HIDXShell: The term 'HIDXShell is not recognized ...
  • Fatal error, tries exhausted must stop
  • Error: No O.MG Device found. Check VID/PID
  • Messages missing content or malformed
  • Doubled Messages
  • Slow Shell or Data Transfer
  • Python Universal Client Poll Times
  • Python Universal Client Error: Lost device, must attempt to reconnect
  • Access denied (insufficient permissions)

In the current PowerShell instance the function has not been imported. This may happen for a number of reasons. However generally using Import-Module again or copying the function back in will solve this issue. If it persists check your shell path and execution policy to ensure unsigned functions can be loaded.

In the current PowerShell instance the function has not been imported. This may happen for a number of reasons. However generally using Import-Module again or copying the function back in will solve this issue. If it persists check your shell path and execution policy to ensure unsigned functions can be loaded.

If you get this error, the auto-reconnect code has given up. This means that the software has lost communication to the cable greater then the allowed tries. This means the O.MG Device may have turned off HIDX Stealth Link or was removed after a successful connection. The -Tries argument in HIDXExfil or HIDXShell can be used to increase this retry amount

Prior to connecting no O.MG Device was found. If this happens it means either the O.MG Device does not support HIDX Stealth Link (Non-Elite) or HIDX Stealth Link was not enabled. Ensure your configuration and try again with the POC code.

In order to balance speed and reliability messages have limited error checking before being sent over the HIDX Stealth Link. This can result in message chunks being lost. If you see a message or a command (such as dir) where output is malformed you can resend the data again or continue, the original data is not harmed.

Messages are doubled. This is because two instances of the HIDXShell are running, best option is to terminate one or both of them and restart as a single instance (if possible).

HIDX travels through the cable as a means of connecting to systems which would not normally have a network connection or when needs require extra stealth. Because of this transfer is slower, it will take more time to transfer files or read data from the shell. This is to be expected.

In certain situations you can set the "Experimental Speed Multiplier" under USB Settings on the O.MG Elite device to increase speed on supported devices.

Presently the Python Universal HID Host tool polls slower due to the logic being written very verbosely to make it easier to understand. Further optimizaitons can be made to tremendously speed it up but at the expense at readability.

If you get this message the code will try to reconnect, however if it times out with an exception ! Error detected in read()

You need to run the tool as root.