/root/payload, and the captured loot in
/root/loot. But SSH has another function, and with it you may never need to drop into the Shark's bash shell.
cp' in Bash or PowerShell, or 'copy' in CMD. And with that, here are the two scp commands that'll make your Shark Jack life a breeze.
C:\Users\bob\SharkJack\payloads\ipinfo, so if I navigate there in PowerShell I can use the scp command to ferry that file over to the Shark Jack's payload folder - overwriting anything that may already exist there.
.\.The next parameter, to, specifies where on the Shark Jack in the form of three elements: the user, the IP address, and the directory. In this case the user is root, the IP address of the Shark Jack is
172.16.24.1, and the directory is
[email protected]:directory– with
@separating user and host, and
:separating host and directory. If no directory is specified after the
:, the default will be the user's home directory. In this case, the root user's home directory is
/root/– so specifying
:payload/is the same as specifying
:/root/payload/(just with less typing).
payload.shfile over to the Shark Jack in
/root/payload/, overwriting any
payload.shfile that's already there.
-rargument is specified so say to recursively copy the files. This means it'll copy files from all of the nested directories, since each payload saves loot to its own folder. The rest of the command is similar to the previous, only reversed. In this case the from field is the remote host – again in the form of
[email protected]:directory. The to field is the current working directory, as represented by '
.' – or it could be any path such as