Red teaming doesn’t start with the exploit. It starts with the infrastructure. Most operators reuse it, reconfigure it, or leave fingerprints across jobs. This talk is a start-to-finish walkthrough of standing up a red team infrastructure stack: privacy-focused domain registration, hardened droplet, Nginx redirector, Sliver C2, and Interactsh OOB callbacks, all built live with the mindset that everything gets burned when the job’s done.

We’ll talk through the choices that matter, the ones that’ll get you caught, and why your infra should never outlive your engagement. Whether you’re running your first engagement or just tired of duct-taping the same VPS between jobs, you’ll walk out with a repeatable checklist you can actually use on your next gig.

No reused IPs, no stale certs, no leftover configs. One engagement, one stack, zero traces.

Registration: No registration
Cost: Free
Format: Hybrid