Author: mleykin

Project Title: Hackerman

Project Team: Me, Myself and I

One Sentence: On-premises vulnerability assessment tool.

Weekly Accomplishments + Pics:

I have acquired a lcd mini screen and FINALLY got it to operate properly (after killing and resurrecting my raspberry pi 10 times, yes really) I am working out one or two issues with this pumpkin pi that I hope to resolve by the end of the week. Also the poster is done!

Material List:

Areas of Concern: Still need to figure out a way to boost my wifi pumpkin to be more powerful and need to find a way to effectively demonstrate my tools, may be difficult without getting into technicalities. I am also concerned about my covers fitting onto my parts. I have been having a lot of difficulty with the low quality my parts have been coming back as and will need to redesign around this, looking for better 3D printing avenues.

Project Title: Penetration of Endpoints and Networks Infiltration System.

Project Team: Me, myself and I.

Weekly Accomplishments:

• This week was dedicated to researching methodology into constructing components:
  • Plenty of guides for making a rogue access point:
    •   https://null-byte.wonderhowto.com/how-to/build-pumpkin-pi-rogue-ap-mitm-framework-fits-your-pocket-0177792/
    • I will likely be looking at this for my guide if I choose to build one.
    • 
  • Also there are plenty of guides already of poor man’s bash bunnies:
    • https://www.cron.dk/poor-mans-bash-bunny/
    • https://blog.hackster.io/build-an-affordable-bash-bunny-with-a-raspberry-pi-zero-w-11a4abf7bde5
    • If I decide to build it I will be using these guides.
  • The RFID reader/writer was the hardest as there are no reliable methods to do this without spending a lot of money or trusting a sketchy manufacturer, I might consider replacing this device with something else (maybe something to due with bluetooth) if I cannot find a good way to do this.

Changes to Approach:

After receiving some feedback, I am now considering adding some bluetooth device to my jacket to exploit those possible attack surfaces, also I might just buy cheaper versions of all of these gadgets to prevent problems in the future. I will be weighing the costs and benefits of each approach.

Materials List:

The Penetration of Endpoints and Networks Infiltration System

Michael Leykin

Description:

1. A vulnerability assessment tool for a physical location target. My project incorporates a variety of ethical penetration testing tools integrated in the lining of a jacket, meant to look inconspicuous.
2. This project is for experimental purposes and really does not consist of any legitimate uses, except those of malicious intent or a security team that is very dedicated to vulnerability assessments of every possible attack surface.
3. As far as use goes, all the user would have to do is put this jacket on themselves like a normal jacket and then turn it on. Then they would have to turn on their computer at home so it can receive password hashes from the jacket later (if any are found). When on the location the user can do a number of actions that depend on their goals. If they come across a key card attached to someone or laying on a desk they can scan this card with the RFI scanner (located on the right sleeve) to make a copy of this card and access different parts of the building or a machine that they previously did not have access too. If the user comes across a unattended workstation they can insert the bash bunny (located on the left sleeve), select a payload they wish to inject and then inject the machine with malware, keyloggers or just retrieve data from the particular machine. Lastly while the user is walking around their target location they will be collecting password hashes from victim users connecting to the jacket’s fake wifi network as they try to connect to their legitimate wireless network. These are the basic uses of my project that could be used by a potential malicious actor or security team.
4. So as far as the components of my project, there is nothing unique. All of these penetration testing tools exist in a variety of flavors in a plethora of products. What is unique, however, is the combination of these tools on a single platform that allow the user to conveniently combine the functionality of them at one time to get further into a system then just one of these tools could on their own.

Inspiration images/artists/designers/projects:

So my main inspiration behind this project was the existing penetration testing hardware. A lot of these existing tools can be found on site like Hak5, but I will be making most of my devices because the existing devices are overpriced and can be remade cheaper using a raspberry uno. But here is a quick list of the tools I will be incorporating (in function):

• The Wifi Pineapple  
  • What this does is mimic a preferred network to perform man-in-the-middle attacks. Allowing me to obtain credentials of victims that happen to get fooled by the mimicked network.
• The Bash Bunny
  • This essentially emulates a trusted usb device (like a keyboard, mouse…etc) to then inject a multitude of payloads onto the victim device very quickly. It doesn’t matter whether or not the machine is locked, this will run its selected payload.
• The Keysy
  • This device can read and then duplicate the rfid signal produced from a security badge or fob, allowing physical access to where I could not before.

Digital or Scanned Sketches:

(Apologies for the poor drawing skill)

Materials/tools you’ll use/need:

(Working List)

• RFID Scanner/Writer
• A Raspberry Pi
• A USB WiFi Adapter
• A SD Card flashed with the Raspbian OS
• Raspberry Pi Zero Wifi
• Pi Zero USB Stem
• 2 x Tactile Push Button Switch With LED lights
• DIP switch with 4 switches
• 2 x 330R resistors
• A inconspicuous jacket with a lining, that I can take apart

Skills/concepts that you will need to master:

Soldering (maybe), sewing, some coding and some circuitry.

Timeline:

• Milestone 1 (March 25): Obtain/build all pen testing tools and have them operating separately in a test environment.
• Milestone 2 (April 8): Have all tools sewn into/incorporated into jacket in some way, but not closed (tools are still visible) yet.
• Milestone 3 (April 22): Have all tools configured with appropriate software and successfully concealed in the jacket.

The Fallback Plan:

The only place where this could really go wrong is in the construction of my tools, if this happens, I will have to open my wallet and buy them (unfortunately) but hopefully I will not have to resort to this. My bare minimum requirements is to have some form of the original functions incorporated into the jacket (software/design/hardware might be outdated for modern systems but the components are still concealed and present in the jacket).