Burner images for Phison controllers can be found here. These are typically named using the convention "BNxxVyyyz.BIN". If your drive uses the Phison 2303 (2251-03) controller, the output should look similar to this:Ī "burner image" is required for dumping and flashing firmware on your drive. Just open the tool and hit the "Get USB Flash Drive Information" button while you have your USB inserted into your PC.
We can use a program called Flash Drive Information Extractor to gather the required information about our USB. Determining the Microcontroller of Our USB Flash Driveīefore starting, we want to make sure our USB uses the supported controller. Please continue at your own risk there is no guarantee that your device will work, even though there shouldn't be any issues. Please read the "Setting Our Device into "Boot Mode" Manually" section at the end of this article for help on opening it. One of my friends had to literally saw up his USB device because he was too hasty. Make sure you can open the case of your USB device without damaging it.Sometimes owning a confirmed device doesn't mean the PS2251-03 is actually being used, as manufacturers seem to use different controllers even within same device models. I will use an 8 GB Toshiba TransMemory-MX USB 3.0 drive in this tutorial. You can find a list of known supported devices on GitHub. Also, we need to have an USB 3.0 flash drive with a Phison 2303 (2251-03) microcontroller.
CHROME IMAGEBURNER USB ANDROID
The process is kind of like compiling and flashing ROMs to your Android device.
CHROME IMAGEBURNER USB CODE
In this tutorial, we are going to determine the microcontroller of your USB flash drive, compile the source code published in GitHub for the tools we need, and move over to building a custom firmware with an embedded HID payload that will turn our harmless USB flash drive into a malicious keyboard designed to help us compromise our victim machine. Even though almost every USB flash drive is exploitable, the only released reprogramming method is for "Phison" microcontrollers. This scenario is often called an "HID Payload Attack," since you have to hand over your script to the Bad USB for the execution (more on that later). This allows us hackers to reprogram the microcontroller in them to act as a human interface device (HID), e.g., a keyboard, and perform custom keystrokes on our target machine. Most common USB flash drives are exploitable due to the "BadUSB" vulnerability. In addition, it would be nice to have something related on our WonderHowTo world.
CHROME IMAGEBURNER USB HOW TO
Recently, someone asked how to make your own "Bad USB," and I promised to make a how-to on this topic. Many of you don't even know about my existence here on Null Byte, so I thought of contributing something rather interesting.
0 kommentar(er)
