Uploaded October 2025 | Updated September 2026, 2 weeks ago
00:00 - Introduction
00:45 - Start of nmap
03:50 - Running RustHound with the credentials we were given
06:40 - Clicking outbound control a few times from Henry to see an obvious (but long) attack path
09:30 - Using BloodyAD to perform the Targeted Kerberoast attack
13:20 - Using BloodyAD to add ourself to a group then NetExec to reaed GMSA Passwords
15:50 - Using BloodyAD to change the password of a user and then use Certipy to create a Shadow Credential for the next user
19:30 - Looking at certificates in Bloodhound and Certipy to see one certificate has a SID under Enrollers
21:30 - Using powershell to show and restore deleted objects
25:15 - Running Certipy with Cert_Admin to see it is vulnerable to ESC15
32:55 - Performing ESC15 by generating a certificate with Certificate Request Agent property, which then lets us generate an administrator certificate to get root
35:20 - Beyond Root: Fixing the CA_MD_TOO_WEAK error by creating a new OpenSSL Config and not using UV to run certipy
00:00 - Introduction
00:45 - Start of nmap
03:50 - Running RustHound with the credentials we were given
06:40 - Clicking outbound control a few times from Henry to see an obvious (but long) attack path
09:30 - Using BloodyAD to perform the Targeted Kerberoast attack
13:20 - Using BloodyAD to add ourself to a group then NetExec to reaed GMSA Passwords
15:50 - Using BloodyAD to change the password of a user and then use Certipy to create a Shadow Credential for the next user
19:30 - Looking at certificates in Bloodhound and Certipy to see one certificate has a SID under Enrollers
21:30 - Using powershell to show and restore deleted objects
25:15 - Running Certipy with Cert_Admin to see it is vulnerable to ESC15
32:55 - Performing ESC15 by generating a certificate with Certificate Request Agent property, which then lets us generate an administrator certificate to get root
35:20 - Beyond Root: Fixing the CA_MD_TOO_WEAK error by creating a new OpenSSL Config and not using UV to run certipy









![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)
