Social engineering

No tool matches.

• msfpchome

  Quickly builds msfvenom payloads with opinionated defaults for lab reverse shells.

  help

  [*] MSFvenom Payload Creator (MSFPC v1.4.5)
  
   /usr/bin/msfpc <TYPE> (<DOMAIN/IP>) (<PORT>) (<CMD/MSF>) (<BIND/REVERSE>) (<STAGED/STAGELESS>) (<TCP/HTTP/HTTPS/FIND_PORT>) (<BATCH/LOOP>) (<VERBOSE>)
     Example: /usr/bin/msfpc windows 192.168.1.10        # Windows & manual IP.
              /usr/bin/msfpc elf bind eth0 4444          # Linux, eth0's IP & manual port.
              /usr/bin/msfpc stageless cmd py https      # Python, stageless command prompt.
              /usr/bin/msfpc verbose loop eth1           # A payload for every type, using eth1's IP.
              /usr/bin/msfpc msf batch wan               # All possible Meterpreter payloads, using WAN IP.
              /usr/bin/msfpc help verbose                # Help screen, with even more information.
  
   <TYPE>:
     + APK
     + ASP
     + ASPX
     + Bash [.sh]
     + Java [.jsp]
     + Linux [.elf]
     + OSX [.macho]
     + Perl [.pl]
     + PHP
     + Powershell [.ps1]
     + Python [.py]
     + Tomcat [.war]
     + Windows [.exe // .exe // .dll]
  
   Rather than putting <DOMAIN/IP>, you can do a interface and MSFPC will detect that IP address.
   Missing <DOMAIN/IP> will default to the IP menu.
  
   Missing <PORT> will default to 443.
  
   <CMD> is a standard/native command prompt/terminal to interactive with.
   <MSF> is a custom cross platform shell, gaining the full power of Metasploit.
   Missing <CMD/MSF> will default to <MSF> where possible.
  
   <BIND> opens a port on the target side, and the attacker connects to them. Commonly blocked with ingress firewalls rules on the target.
   <REVERSE> makes the target connect back to the attacker. The attacker needs an open port. Blocked with engress firewalls rules on the target.
   Missing <BIND/REVERSE> will default to <REVERSE>.
  
   <STAGED> splits the payload into parts, making it smaller but dependent on Metasploit.
   <STAGELESS> is the complete standalone payload. More 'stable' than <STAGED>.
   Missing <STAGED/STAGELESS> will default to <STAGED> where possible.
  
   <TCP> is the standard method to connecting back. This is the most compatible with TYPES as its RAW. Can be easily detected on IDSs.
   <HTTP> makes the communication appear to be HTTP traffic (unencrypted). Helpful for packet inspection, which limit port access on protocol - e.g. TCP 80.
   <HTTPS> makes the communication appear to be (encrypted) HTTP traffic using as SSL. Helpful for packet inspection, which limit port access on protocol - e.g. TCP 443.
  … (7 more lines — see the tool's home page)

• setse-toolkithome

  Social-Engineer Toolkit for phishing and payload demos when social testing is in the rules of engagement.

  help

  ┏━(Message from Kali developers)
  ┃
  ┃ The command se-toolkit is deprecated. Please use setoolkit instead.
  ┃
  ┗━

• veilhome

  Payload generation focused on AV evasion demos; document the exact technique, not the brand name.

Where an authored purpose exists, it is written for this path. Otherwise you see the package summary. Help text is captured live from a Kali system where available.