Skip to main content

Teensy as a Metasploit Attack Vector


Recently I was playing with the Teensy www.pjrc.com/teensy and I wanted to test it as a Metasploit exploit/payload attack vector.  The Social Engineering Toolkit (SET) in Metasploit exploit/payload sounded like the perfect thing to try.  I followed the instructions at www.offensive-security.com/metasploit-unleashed/SET_Teensy_USB_HID_Attack and they worked almost flawlessly.  A couple of hints I'd give are:
1) Update SET prior to starting.  Simply use the menu, or do a 'svn update' from the SET directory
2) I was surprised when SET didn't ask me for my IP address.  I RTFM, and I noticed that the AUTO_DETECT in the set_config file was set to ON, which means that it automatically gave the payload the IP address of my Ethernet address.  So remember to change this if you want to get through a NAT or something.

For my Teensy, I selected:
WSCRIPT HTTP GET MSF Payload
WINDOWS REVERSE_TCP_METERPRETER
BACKDOOR EXECUTABLE
PORT

Then SET made a exploit/payload image, and I uploaded it to the Teensy.  The instructions at the URL above show a "Teensy 2.0 (USB Keyboard/Mouse)" option under Boards, and I didn't have that. But I had a Keyboard option under USB, and the Teensy 2.0 under Boards, and when I selected both of these, the SET image compiled just fine.

I uploaded it to the Teensy, and put it in a victim box.  The Teensy was recognized as a Teensy USB Keyboard, installed the keyboard drivers, and started popping up screens galore... notepad files, command prompts, and about 15 Start->Run Windows that it filled in with various text and executed, and the whole process takes about 15 seconds!  Then it errored out on an C:\x.exe file, saying that Windows couldn't find it.  What was worse, MS Security Essentials detected a backdoor in System32, and killed the exploit process by stopping it from executing (why the aforementioned c:\x.exe error occurred).  I guess the Teensy doesn't slip past AV very well.  Good to know.  So I uninstalled Security Essentials, rebooted, and tried again.  This was awarded with a Meterpreter session on my attack platform! 

My take away from this endeavor is that while the Teensy may be useful to pwn a system that you may have physical access to, it pops up so many windows that there is no way that you could social engineer it and hand it to someone and have them sit through all the windows while it infects their system... they'd unplug it and run to their IT shop for help.   So I put this in my toolbox as a quick way to install a backdoor myself, keeping in mind the AV hit potential.  

Comments

Popular posts from this blog

HP c6180 Printer and Vista

Hp c6180 driver issues with Vista Home Premium My wife has a Vista Home Premium laptop, and the HP C6180 Photosmart printer keeps disappearing from her available printers.  The only way I've found to fix the problem is to reinstall all the HP software. When I do this, I have to download the (large..507M software from HP, or reinstall the printer (ONLY the printer, not the scanner) with the installation disk, as the drivers are not discovered with a "Windows Update" setting.  My guess is that is because HP doesn't like people to install only the printer driver, which would be easy, but they want folks to install all their crapware as well, so they are withholding the drivers from the on-line Microsoft printer database.  So keep your installation CD!  I've also found that unless I install everything on the CD or in the Full Version download (HP Customer Participation Program, HP Imaging Device functions, HP OCR SW, HP All-In-one SW, HP Photosmart Essential, HP

atftpd vs tftpd-hpa

Recently I was trying to tftp files from a Windows computer to a Kali box.   One version of Windows worked, but another didn't.    After much troubleshooting, here were my symptoms: I could tftp a file from-to any Kali box from-to another Kali box I could NOT tftp files to a specific Windows 7 box from any Kali box I could NOT tftp files to a Chrooted-Ubuntu-Chromebook box from a Kali box After MUCH troubleshooting, going through every setting in atftpd, it seemed like it literally was a client OS problem.  Different clients simply would not download files---unacceptable. Thus, I switched to tftpd-hpa.   To install: apt-get install tftpd-hpa files go to/come from /srv/tftp, but it needs to be a tftp user. Thus, I needed to: chroot -R /srv/tftp Also, if you want to be able to put files ON the tftp server (from a client), you need to modify /etc/default/tftpd-hpa: change "TFTP_OPTIONS="--secure"  to "TFTP_OPTIONS="--secure --create" I al

Security Onion on the Antsle

My Setup of Security Onion on the Antsle: Recently my IDS box, an Intel Atom D2500 Fanless Mini-ITX PC, D2500CCE, died.  Truth be told, I think it came from the factory in a bad state, as I originally thought I had a bad graphics driver, but I then noticed that, after much troubleshooting, it wasn't a driver issue at all.  The box just sometimes wouldn't boot up correctly with video.  It seems heat related, something like not enough thermal paste on the CPU, as after it is powered off for a while it is more likely to boot than when it is warm.  Along with that issue, this box maxed out at 4GB of RAM (only has 2 memory slots, each of which will only take a 2GB card max) and had a single processor, so it was under powered for Security Onion. So, I decided to quit limping along on P.O.S. boxes, and buy a little more heavyweight box for my networked IDS.   Security Onion requires a minimum of 8GB of RAM, and 4 cores per their specs page https://github.com/secur