[UPDATED: April 14th, 2016:
Good news everyone! MSFT has released an optional update that resolves this issue:
I’ve written a quick Powershell script to get a full inventory of affected computers (deal with the output yourself).
Worth noting that this is clearly novel, but, as of this time, MSFT hasn’t released a patch, which is weird given that Bastille disclosed the vulnerabilities to them November 24th, 2015. The recommended solution (from Bastille) is to move to a wired keyboard. Nice! But aren’t those vulnerable as well?! Is Tom Cruise crawling in my ceiling tiles?!!1
Here are the details and links to attack code: https://www.bastille.net/affected-devices