combatwombat27 Posted November 22, 2021 Share Posted November 22, 2021 So, I was thinking, wouldn't it be an issue if I switched to arming and THEN plugged into the network? Couldn't it potentially start the (in this case) nmap scan before it is up and on the network. Would it not be best to plug it into the network and THEN switch to attack mode? Second question. Is there a way to see what firmware I'm already running on the shark jack? Third question. I see on the UPDATE_PAYLOADS command is only available on firmware 1.2.0 but when I check the firmware page it goes up to 1.1.0. Am I missing something? Link to comment Share on other sites More sharing options...
dark_pyrro Posted November 22, 2021 Share Posted November 22, 2021 Not sure what you mean by the first question. Both arming and attack mode is mentioned. Second question; ssh into the Shark and run: cat VERSION Alternatively set up C2 and add the Shark (but that's a load of work just to get the version) Third question; you most likely stumbled upon some documentation that isn't really supposed to be released yet. Possibly a new variant of the Shark incoming that could be inspired by the O.MG cables (perhaps). Link to comment Share on other sites More sharing options...
combatwombat27 Posted November 22, 2021 Author Share Posted November 22, 2021 47 minutes ago, dark_pyrro said: Not sure what you mean by the first question. Both arming and attack mode is mentioned. Second question; ssh into the Shark and run: cat VERSION Alternatively set up C2 and add the Shark (but that's a load of work just to get the version) Third question; you most likely stumbled upon some documentation that isn't really supposed to be released yet. Possibly a new variant of the Shark incoming that could be inspired by the O.MG cables (perhaps). Thanks so much for the detailed response. This helps a lot. As far as the first question, I'm wondering if I should put in attack mode before plugging it into the network jack. The reason I ask is I was worried if I did that, that payload.sh might start running before I have it connected to the network. I'm trying to avoid breaking / not using the attack scripts correctly. Hope that makes more sense. Link to comment Share on other sites More sharing options...
dark_pyrro Posted November 22, 2021 Share Posted November 22, 2021 Flip it to attack mode, then attach it to the network when it is finished booting. But, it's possible to do it the opposite way as well. Darren is talking about that @ about 5 minutes into the video below. Link to comment Share on other sites More sharing options...
dark_pyrro Posted November 22, 2021 Share Posted November 22, 2021 And, yeah, the Shark Jack Cable seems to be a new (unreleased) product since it's on a picture in the new documentation at the new help.hak5.org address. https://help.hak5.org/shark-jack/getting-started/shark-jack-basics#shark-jack-cable Link to comment Share on other sites More sharing options...
Irukandji Posted November 23, 2021 Share Posted November 23, 2021 13 hours ago, dark_pyrro said: And, yeah, the Shark Jack Cable seems to be a new (unreleased) product since it's on a picture in the new documentation at the new help.hak5.org address. https://help.hak5.org/shark-jack/getting-started/shark-jack-basics#shark-jack-cable Quick hide it /s. This has been a Crazy year for the tech industry. Even for hak5. Example Pineapple Enterprise and the MK7AC module. Hasn't been released. Link to comment Share on other sites More sharing options...
dark_pyrro Posted November 25, 2021 Share Posted November 25, 2021 No real secret needed to be hidden really, it's pictured in the shop as well as being a part of payload comments and commits on the Hak5 GitHub. The MK7AC module has been released by the way. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.