[GET TARGET_ID not working on a 1.3 bunny?]

6 hours ago, PoSHMagiC0de said:

Pretty much you will loop through so many times to see if it is taking some time for the bunny to issue the IP.  I know I always get a hostname.  IP I don't use but this should work the same.  The LEDs will let you know which part it is checking for and the bunny should open notepad and type out results as it gets them.

Fantastic, works like a charm, thanks a lot!

[GET TARGET_ID not working on a 1.3 bunny?]

I am having trouble using GET TARGET_ID in payloads.

To verify it's this specific command causing the trouble, I set up this short script:

ATTACKMODE RNDIS_ETHERNET
LED STAGE3
Q DELAY 3000
GET TARGET_IP
# Check target IP address. If unset, blink slow red.
if [ -z "${TARGET_IP}" ]; then
    LED FAIL2
    exit
fi
LED FINISH

and indeed it ends up blinking red. Firmware is 1.3. Any idea? Or is there something wrong in the script?

Thanks!

[[PAYLOAD] DrumpCreds 2.0 ( SMB, w/o Internet, w/o USB Storage )]

Okay, been entering the critical part manually, logged into the bunny. Accepting all commands, except the required GET. get.sh resides in /payloads/extensions on my bunny (1.3).

[[PAYLOAD] DrumpCreds 2.0 ( SMB, w/o Internet, w/o USB Storage )]

Problem occuring while testing on a Windows 10 machine, btw

[[PAYLOAD] DrumpCreds 2.0 ( SMB, w/o Internet, w/o USB Storage )]

I've been using 2.1. Just gave 2.3 a go, ended up with the same red-blinking LED (about once a second). Great enhancements in 2.2 though.

[[PAYLOAD] DrumpCreds 2.0 ( SMB, w/o Internet, w/o USB Storage )]

As I'm having a problem with this payload (slowly blinking in red), I'd love to see the debug-output, however I cannot seem to make the debugging work. I created an ampty text file called "DEBUG" in the switchfolder, without any results. Any suggestion? Thanks!