Jump to content

payload.sh debugging/logging?


battleop
 Share

Recommended Posts

When I plug my sharkjack I get nothing in the loot directory.    Just to start I'm using the default payload.sh scrip that comes on the jack.    Is there any debugging or logging I can look at to see what it does not like?    Nothing is being written in /var/log.

Link to comment
Share on other sites

Nothing that gets logged related specifically to the payload afaik. You can run logread to see events. Events tagged especially for the Shark can be viewed using: logread -e Shark   I guess you are connecting the Shark to the network the "common" way (via a switch port). There should be no real problem with that default payload and getting loot. Is the network restricted in any way? By MAC address making the Shark not able to connect? You can always try the payload I put up on my GitHub that "steals" the MAC address of an endpoint and then uses that MAC address when connecting to the network to run nmap and save loot. It worked when I wrote it, but I know the default Shark payload should work as well.

https://github.com/chrizree/Hak5-SharkJack-MAC-pilfer-and-nmap-scanner

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...