> For the complete documentation index, see [llms.txt](https://blog.r00t-hunter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.r00t-hunter.com/r00t-hunter/about-me.md). # About Me Hey, I’m Deepak. I work in cybersecurity with a focus on offensive security, web application testing, red teaming, reverse engineering, malware analysis, and digital forensics. Most of what I know comes from breaking things, fixing them, and understanding why they broke in the first place. I don’t learn from theory alone. I learn from real systems, real logs, real failures, and real attack paths. I run tools like Nmap when I’m curious, Burp Suite when I’m serious, and Volatility when I’m digging into memory and forensics. I don’t claim to know everything. This field changes too fast for that. Half of cybersecurity is continuous learning, and the other half is realizing your assumptions were wrong. Over time, I’ve worked across web security, system analysis, memory forensics, binary analysis, and red team-style thinking. I understand cloud at a practical level not deep enough to flex, but enough to know where things usually break. What matters more to me is mindset: how attackers think, how systems quietly fail, and how small mistakes turn into real compromises. 🎮 TryHackMe: tengetstroal\ 🧩 Hack The Box: ro0thunter#IN Yeah, the usernames still sound like something I made at 2 AM. That part stays. *** ### People Who Shaped My Thinking My college mentor pushed me toward practical, hands-on learning over rote memorization that shift in approach is the reason I build labs instead of just reading about attacks. During my internship at TechDefence Labs, Pavan Saxena gave me a line that's stuck with me ever since: *"If it's smart, it's vulnerable."* It's become a lens I apply to every system I look at the more "intelligent" or automated something is, the more assumptions it's making, and assumptions are where vulnerabilities hide. A close friend has also been part of this journey, showing up for me during the long nights of rebuilding labs / pushing me to keep going when projects fell apart / talking through ideas when I was stuck steady support that's easy to overlook but made a real difference. *** ### Closing Hunter Labs is where I document real experiments, mistakes, and lessons from cybersecurity no theory theater, just work that actually breaks and teaches. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://blog.r00t-hunter.com/r00t-hunter/about-me.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.