diastill.blogg.se

1. Teensy driver windows drivers#
2. Teensy driver windows code#
3. Teensy driver windows Pc#
4. Teensy driver windows windows#

Success =check_for_numlock_sucess_teensy (reps ,millisecs ) println ( "$wsh = New-Object -ComObject WScript.Shell $wsh.SendKeys('')" ) // "press numlock via powershell"

Teensy driver windows code#

The following pseudo code provides an example for attempting to open a command prompt, while accepting feedback on a successful event.īool check_for_powershell ( int reps, int millisecs )

Teensy driver windows windows#

One solution for this (derived from the code above) is to have Windows programmatically press num/scroll/caps keys once a command is successful – allowing the Teensy to then sense the num/scroll/caps LEDs, and make the appropriate conclusions. For this reason, we need a feedback mechanism to know whether a command prompt was opened successfully and provide some “error correction” to the Teensy. Without this functionality, we are very limited in our payload deployment. Opening a Windows command prompt is the foundation for all our attacks. Once the Teensy senses a reaction, it can then continue sending keyboards commands safely. Once the Teensy is plugged in, this function will continuously check to see if the Keyboard is reacting to a “Num Lock” key press (by checking if the corresponding Led lights up).

Teensy driver windows drivers#

Initial Windows Initialization of the TeensyĪn elegant solution for figuring out when the Windows drivers are initialized and ready was found in a code snippet we found floating on the interwebz. If for some reason this sequence were to be interfered with or some other mishap should occur – the Teensy keyboard commands would go out of context and probably not produce our required results. For example, once we plug in the Teensy to a victim machine, how can it know when Windows has initialized the required drivers and is ready to accept keystrokes from it? Another good example would be opening a Windows command prompt through the Teensy – which requires a sequence of keyboard commands, timed in a certain manner. The Teesny has little support for input (NumLock, ScrollLock, CapsLock Leds) – making it harder to know if a specific operation has succeeded or not. This is probably one of the most challenging aspects of the design. Payload reliability – Execution and Deployment Should be able to cope with different Windows architectures and versions.Should use little to no foreign executables on the victim machine.The payload should be persistent and survive reboots.We needed to address these goals specifically: The basic functionality of our Teensy payload is to act as a “Trojan Dropper” for Windows based machines. The SD card can be connected easily, as shown on the PJRC site. The DIP switch needs to be grounded on one side, which was achieved by cutting off two pins from the one side, and connecting them with the last pin, which ends up in the Teensy ground. The SD card and DIP switch mount nicely on the Teensy, with no extra wiring needed. In order to meet our design goals, we realized we would need to add an SD card reader to the teensy, as well as add a DIP switch, which would allow us to configure basic payload settings before plugging in the Teensy into a victim computer an initiating an attack. The hardware required for this project is readily available through and amazon. The device should also be able to cope with advanced and complex payloads, while still retaining a small form factor. The Teensy would target Windows machines only (in our case, Windows 2008 servers), and should be able to cope with variables such as the architecture of the machine being attacked, whether UAC should be bypassed or not, etc. Our goal was to make a custom, “uber” Teensy, which would provide dynamic and reliable functionality in the field. By cannibalizing code and ideas from various projects and web resources, we were able to improve and refine our Peensy payload to suit our needs. Most notably, there are IronGeeks PHUKD library, SET Teensy payloads, and Kautilya.

Teensy driver windows Pc#

There has been a significant amount of previous talk about using the Teensy device to emulate PC keyboards, as well as various methods of delivering malicious payloads to computers from the Teensy.

The impatient can find the video demo below. From here, the “Peensy” (Penetration Testing Teensy?) was born. This assessment presented an excellent scenario for a USB HID attack, where an attacker would stealthily sneak into a server room, and connect a malicious USB device to a server with logged on console, thus compromising it. In one of our recent engagements, we had the opportunity to test the physical security of an organization. The Peensy – Advanced Penetration Testing Payloads