Jump to content

Categorizing payloads in library


Recommended Posts

Hey everyone i just had a thought... wouldnt it be better to categorize all payloads in different folders for what it is meant to attack? Like a folder for windows attacks, one for mac, one for linux, one for universal, one for bashbunny innstallers and so on.. I just feel like the library is going to be very messy if not :/

  • Upvote 3
Link to post
Share on other sites

Good idea. Even just OS/Target would be great.

OS/Target = Windows, OSX, Linux, Android, iOS, Other(Printers/TV/Routers/devices?) & Multi.

Type/function? (maybe not) = Recon, Exploit, Access, Prank, Other & Multi.

 

Edited by Just_a_User
Link to post
Share on other sites
9 hours ago, Sebkinne said:

I agree. I'm not sure of what exactly the organization should be, but I'm welcoming suggestions.

Maybe OS -> Type of payload or Type -> OS?

I thought about first a folder for which os and also a multi os folder for attacks that work on multiple os, then inside the os folder what type of attack (Like HID, RNDIS_ETHERNET,  ECM_ETHERNET and so on). :P and maybe also combined attacks like HID and ECM_ETHERNET :D

Link to post
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.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...