Uploaded February 2026 | Updated September 2026, 2 weeks ago
00:00 - Introduction
01:00 - Start of nmap
03:20 - Adding the API Key to our WPScan
08:00 - Discovering a POC for the GiveWP plugin and getting a shell
12:00 - Looking at the WP Database, not getting much information
18:00 - Discovering an HTTP endpoint in the environment variable, setting up chisel to look at it
22:00 - Looking at the custom web page, it is vulnerable to a PGP CGI Vulnerability
30:00 - Shell on the second pod
31:00 - Discovering a Kubernetes (k8s) token, copying it back to our box and setting up kubectl to examine Kubernetes and dumping secrets
39:50 - Showing we didn't need KubeCTL we could have used curl, showing hacktricks age that has some nice tips on setting this up to easily query the k8s api
44:50 - With a password from k8s, we can login to the box and execute a runc wrapper with sudo. It is running version 1.1.11 which is vulnerable to an sandbox escape.
52:15 - Showing an alternative way to exploit this binary through exploiting the wrapper with a simple path traversal in mounts
00:00 - Introduction
01:00 - Start of nmap
03:20 - Adding the API Key to our WPScan
08:00 - Discovering a POC for the GiveWP plugin and getting a shell
12:00 - Looking at the WP Database, not getting much information
18:00 - Discovering an HTTP endpoint in the environment variable, setting up chisel to look at it
22:00 - Looking at the custom web page, it is vulnerable to a PGP CGI Vulnerability
30:00 - Shell on the second pod
31:00 - Discovering a Kubernetes (k8s) token, copying it back to our box and setting up kubectl to examine Kubernetes and dumping secrets
39:50 - Showing we didn't need KubeCTL we could have used curl, showing hacktricks age that has some nice tips on setting this up to easily query the k8s api
44:50 - With a password from k8s, we can login to the box and execute a runc wrapper with sudo. It is running version 1.1.11 which is vulnerable to an sandbox escape.
52:15 - Showing an alternative way to exploit this binary through exploiting the wrapper with a simple path traversal in mounts




![Intercepting Android App Traffic with BurpSuite
00:00 - Introduction, talking about RouterSpace and why we cant just do what we did in that video
01:25 - Installing Genymotion, Virtual Box, and ADB; while talking about why I dont use Android Studio/AVD. Simply because genymotion just works.
02:05 - Make sure you upgrade your memory, processors, and enable Virtualization in your VM Settings!
02:30 - Running Genymotion and starting a Pixel 3 XL
03:37 - Converting BurpSuites Certificate to PEM Format with openssl x509 -inform der -in [name of cert] -out burp.pem
04:20 - Renaming the certificate to 9a5ba575.0, and showing how we got that name
06:00 - Starting the device and showing the certificate authorities
07:00 - Copying the certificate to /system/etc/security/cacerts/, and showing how to remount to rw
08:10 - Showing how to set the proxy through both the GUI and via ADB
09:50 - Installing GAPPS
10:30 - Showing how to unset the proxy from ADB
11:00 - Creating an alias to set and unset the proxy via adb
12:00 - Opening the google play store and logging in and install Wayzn to see if we can intercept traffic
15:20 - Showing we intercepted traffic from Wayzn, then installing Instagram
16:50 - Attempting to login to instagram and getting an error message
17:20 - Setting up Frida both on our computer and android device
19:20 - Showing Frida is working, getting ps output from the android device
19:55 - Downloading the instragram ssl pinning bypass script
21:20 - Using frida to start instagram and loading the script to bypass the SSL Checking
22:15 - Setting the proxy and showing us intercept instagram traffic Intercepting Android App Traffic with BurpSuite](https://i.ytimg.com/vi/xp8ufidc514/mqdefault.jpg)





