duckhunt VS blender-dactyl-keyboard

The cheapest way is a solution that monitors for high-speed keystroke injection, which is what the rubber ducky is generally used for. One such project is https://github.com/pmsosa/duckhunt (I have no affiliation with this project. It appears to have been updated about 2.5 years ago)

(Found some code that does it, but I'm not sure if it's the same one that first I saw a while back)

If it acts as a keyboard, then it is a fast one and can be prevented. https://github.com/pmsosa/duckhunt

If you worry about badusb use this https://github.com/pmsosa/duckhunt it blocks keyboard input when detected too fast typing.

Looks like it doesn't even run on Linux. https://github.com/pmsosa/duckhunt#todo

It depends on the sophistication of the attack. You could for example try to detect it based on the manufacturer. That is your best option to prevent the attack by blocking it to act as a keyboard. If spoofed, or you don't have such a measure, you can try to detect it and then stop it. Typically, by focusing on the behavior from the keyboard. E.g., connected and tying without pause, monitoring the actual first commands from the keyboard,.. Have a look at https://github.com/pmsosa/duckhunt for example.

So as a side project, I wanted to try and "make" my own split keyboard. I stumbled upon [this](https://github.com/SeanGilroy/blender-dactyl-keyboard) project and decided It would be a great first build, as it fits most of my requirements for a split keyboard.

The Blended Dactyl