Search the Community

Showing results for tags 'scripts'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple / Jasager
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • Mark V
    • Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • Mark I, II, III
  • Active Projects
    • Bash Bunny
    • Lan Turtle
    • USB Rubber Ducky
    • SDR - Software Defined Radio
    • Community Projects
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • Community
    • Forums and Wiki
    • #Hak5
  • Other Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Found 4 results

  1. Once I deploy the LAN Turtle, SSH into it using my own VPS, is it possible to run my own custom python scripts using the LAN turtle terminal. For example: I write my own python keylogger script and SCP it onto my LAN Turtle. Is there a way to run this? I'm unsure if this will work as this is connected via ethernet, not necessarily a normal USB stick. Thanks for your time.
  2. I created a shell script to help manage my ducky scripts and to copy what i wanted to use to the root of the drive. After creating it, i wanted to post it just incase anyone else might find it useful and came across this thread. I made this shell script on a mac, and also tested it out on another linux based box and didn’t have any problems. The only thing I had to do on the mac was download the “dialog” command via brew. Currently my SD card contains the following directory structure: As you can see, some of these scripts are from the repository. The Directories are the same name as the script, each directory has the script and the compiled version of the script ready for the duck. When i put in the SD card, i run the menu.sh to bring up the “script manager” what is does is just read the contents of the directory structure and puts it in a menu. I find the one i want and hit enter and it will copy it to the root drive and the script exits. if the inject.bin does not exist where the script is located at, then it will compile it. A lot of the top vars can be changed if you need to. I mostly created it based on how i run and manage the scripts. GitHub for DuckMenu Source: #!/bin/bash #ducky_menu.sh #Version: 1.0.5 #by JM MainFile="inject.bin"; #the compiled file for the rubber ducky CurrentPath=$PWD; #The path of were the menu.sh was ran, this can be hardcoded if needed ScriptsPath="$CurrentPath/scripts"; #path of where the scripts are at, usually a sub folder of the current EncoderPath="$CurrentPath/Encoder/encoder.jar"; #location of the encoder MakeDirMoveFiles=true; #if you have the code in the scripts director and what it to be in it's own directory ScriptExt="txt"; #the extenstion of the script PathName=""; #global var, leave blank choices=""; #global var, leave blank MakeDirFromFiles() { cd $ScriptsPath for file in *.$ScriptExt; do mkdir -- "${file%.$ScriptExt}"; mv -- "$file" "${file%.$ScriptExt}"; done cd $CurrentPath } DoCopy() { cpFrom="$ScriptsPath/${PathName[@]}/$MainFile" cpTo="$CurrentPath/$MainFile" cp "$cpFrom" "$cpTo" dialog --title 'File Copied' --msgbox "$cpFrom was copied to $enTo" 6 60 } RunEncoder() { enFrom="$ScriptsPath/${PathName[@]}/${PathName[@]}.$ScriptExt" enTo="$CurrentPath/$MainFile" java -jar $EncoderPath -i "$enFrom" -o $enTo dialog --title 'File Compiled' --msgbox "$cpFrom was comiled to $enTo" 8 60 } DoMenu() { i=0 x=1 while read line do array[ $i ]="$line" if [[ -n "$options" ]]; then options=("${options[@]}" "$x" "\"$line\"" "off") else options=("$x" "\"$line\"" "off") fi (( i++ )) (( x++ )) done < <(ls $ScriptsPath) cmd=(dialog --separate-output --checklist "Select options:" 22 76 16) choices=$("${cmd[@]}" "${options[@]}" 2>&1 >/dev/tty) if [ -z "$choices"] ; then choices=0 fi if (($choices > 0)) ; then arrayID=`expr $choices - 1` PathName="${array[$arrayID]}" if [ -f "$ScriptsPath/$PathName/$MainFile" ]; then DoCopy $PathName else RunEncoder $PathName fi clear echo "Good Bye Happy Ducking!" else clear echo "No Options selected..Good Bye!" fi } if $MakeDirMoveFiles ; then MakeDirFromFiles; fi DoMenu;
  3. Well, hello there! A brief introduction I just reciently got my hands on the Ducky, and still learning to use it, but I can already see the potential of it. Looking for examples I stumbled upon the wiki list that had some examples, and some "easy scripts generators", which was really nice. But i got myself thinking: Where are all the contributions? I mean, if this product has been out for some time, there sure must be a long list of community-made scripts avaliable, right? Surprisingly, I didn't found much. Which led me to start creating what I now present here as a Work-In-Progress project, hoping to hear the community's response to it. The idea A CLI which will serve as a manager to both, your local scripts and the community ones. It will keep track of all your scripts, allowing you to sort them by the target OS -even by version of OS-, by name or by description, making it really easy to store dozens of scripts without losing your mind. It will also keep track of community-sourced scripts, allowing you to browse them without even having them on your system, only downloading them when you decide to use them. You could search through thousands of scripts as easily as it is searching the local ones: By user, by OS, by effects... How? Community repositories ,ala Linux... but on GitHub! Any user could upload their own scripts to the repositories - from inside the manager! -, making them avaliable for anyone to use. All scripts would be managed through a list of github repositories, which the program would automatically parse and update the local data for. Any user could have their own repository, which any user could source from; but of course, there would be an official repository (or several) from which the program would get it's sources by default. For bonus points, the Manager will - hopefully- also have: Quick configuration of scripts: The manager will automatically let you edit the required parameters before encoding them. So, scripts that require a host to connect to, ports, emails, etc. will be easier and faster to use. Automatic encode and loading: Encode any script and load them onto your SD card from inside the manager, with any avaliable keymap. Multi-language: Designed to be translated, all strings used by the program is inside an easily editable file, for each language. Anyone could translate it to any language in less than a day. Ducky flashing: Repositories also contain firmware for the ducky. Flash from inside the manager with any of them, without having to ever store them. Also, save a backup of your old firmware automatically. Because safety always comes first. Integrated editor: Why have a program to manage your scripts and another to create them? Just code from inside the manager. With syntax recognition incorporated, of course! - not that the language is difficult anyways -. Curent state I have just started coding this today, in Golang. It's already capable of managing hundreds of local scripts with no problem, so I'm pretty certain I'll have a Beta to publish for testing in not that much time - though I can't spend the day on it! -. Of course the first version wont have all the planned features, but they will come, if the community wants it. So that's it, basically. I'm here looking for thoughts and comments about it, so please feel free to express yourself about this idea! I will update this post as I get things done - assuming you guys want it, of course. - (Code is not publicly avaliable yet, will make it public with the first Alpha/Beta)
  4. Hi I ordered my USB Rubber ducky for some day's ago and i just want to now if any know where i can get good script's from I have checked github but many of them seems silly. Plz help