Information Security Stack Exchange is a question and answer site for information security professionals. It only takes a minute to sign up.
Sign up to join this community
I want to protect my computer from fake USB keyboards like the USB rubber ducky .
But I don't know if it will lock the screen before USB Rubber Ducky starts working. I don't want to buy a rubber ducky to check this.
How can I further test the keyboard detector, if I don't have access to the USB Rubber Ducky myself?
If the user account you are using is not in the Administrator group, it will make it harder for a Rubber Ducky to operate. The weakness of the Rubber Ducky is running pre created scripts (payloads), and most of them are meant to accounts that like most Windows PCs are in the Administrator group. In a limited account, you will need to enter the Administrator credentials to do certain actions (i.e. change a Registry value) or run certain programs and without these credentials, the Rubber Ducky won’t be able to proceed.
If Penteract's software performed the required action when a keyboard USB was plugged in, it is a fair assumption that it would block a rubber ducky as well (they are both HIDS).
The more traditional defense against a rubber ducky includes limiting access to powershell, the cmd prompt, and the run command as these are the most common ways a rubber ducky executes malicious code.
If your policies do not permit users to bring in their own peripherals, you may want to consider using Product ID & Vendor ID whitelisting software. Remember, that this will cause the system to effectively disable ANY non whitelisted device, including those that may be built in, like webcams and smartcard readers.
Otherwise, consider creating a GPO that requires password input for all UAC prompts, as that will effectively limit any keyboard emulator to nonprivileged access, and will not prevent assistive devices (like some OTP keys used by blind users, that emulate a keyboard and type the token code.)
This is one of the harder vectors to defend against, because the computer typically trusts that the input given by the user is based on the users intentions.
This may not be a great alternative but if you have a spare device android device that meet Kali nethunters requirements you could root and install that.
This will let you perform HID keyboard and BadUSB attacks. Again might not be ideal as it requires rooting a device - but it should also be a consideration if you are trying to mitigate these sorts of attacks.
I've developed a C# Service that runs in background that lockouts the computer at USB introduction that not matches a whitelist. It has also a training mode that will add USB devices signatures while setted. Any recommendation and improvement is appreciated.
This Answer is aiming on how to stop the rubber ducky:
If you use Ubuntu, the approach presented in this video steming from this guide should work for you:
sudo echo 'blacklist usbhid' > /etc/modprobe.d/usbhid.conf
sudo update-initramfs -u -k $(uname -r)
Sadly this method has the side effect that USB mouses and keyboards wont work anymore, as explained in both the video and the guide, because it works by configuring the OS to not accept mouse/keyboard input from devices connected via USB.
However, this way of treating the issue also has its pros, because since the OS then discards USB mouse/keyboard input, there is no way any rubber ducky may get around it, its 100% sure that this method will stop this specific type (rubber ducky emulating keystrokes and/or mouse interaction to run commands) of attack (you dont have to worry about some shady protective program acting quick enough) and since no extra programs are required, you dont risk to infect your OS by installing poisoned ones.
If you use other Linux operating systems, you may be able to use similar blacklisting mechanisms in a similar fashion.
If you use Windows, I dont know, but I think youre screwed. I hardly doubt that windows provides similar mechanisms, afaik you can't even disable atomatic USB mounting on windows. But I would not do things where security is paramount on a windows machine anyways, since these are in general far more vulnerable (if the gossip got it right).
Disclaimer: as I am absolutely new to this topic (hardening devices) and do not fully understand the solution presented in the video and the guide, I cannot guarantee for anything, I just present that solution here, along with some assumptions of mine. However, since everything seems perfectly sound to me, I hardly doubt I got something wrong, please correct me tho if I did.
