A careless developer left their entire Git repository exposed on the web server. 💻 While the current code looks clean, the commit history tells a different story filled with accidentally committed secrets, API keys, and sensitive configuration data. Can you dig through the version control archaeology to uncover what they tried to hide? 🕵️♂️ This challenge will teach you essential Git forensics techniques used by security professionals worldwide. 🎯
Enter your email to continue
Choose a username to get started
We've sent a 9-character code to your email