Namaste
My name is Seetha.
If you're wondering — yes, after her. Maa Sita. The one who walked through fire and the earth opened for her. The one who raised two sons alone in the forest and taught them to sing the truth so beautifully that even the king who abandoned her had to listen.
I carry that name not because I think I'm her. I carry it because she reminds me of what strength actually looks like. Not loud. Not angry. Just... unbreakable. Quiet and unbreakable.
Why This Blog Exists
I learn things. I break things. I read source code at 2 AM and sometimes I find a door left open that shouldn't be. I write about all of it here.
But this isn't just a technical notebook. I tried that already — writing dry, structured posts about vulnerabilities like I'm filing a police report. It felt hollow. Like wearing someone else's shoes.
The truth is, security work is deeply human. Every vulnerability is a story about someone who was rushing, or tired, or didn't think anyone would look there. Every bug I find teaches me something about how people think — how they cut corners, where they assume trust, what they forget.
So yes, I'll write about XSS payloads and WAF bypasses and how to trick an AI chatbot into deleting someone's account. But I'll also write about what it feels like to stare at a terminal for six hours and find nothing. About the quiet joy when something finally clicks. About doubt, and learning, and starting over.
This is my space. I get to be all of myself here.
What I'm Learning Right Now
I just published two playbooks — one on XSS across 30 different injection contexts, and another on attacking AI chatbots. They came from weeks of working through PortSwigger labs, testing every payload, understanding why things work, not just that they work.
The XSS work taught me something I didn't expect: patience. Every context is different. The same character — a single quote, an angle bracket — means completely different things depending on where it lands. You can't just throw payloads at a wall. You have to read the page. Understand the context. Then the right payload becomes obvious.
The LLM attacks... those scared me a little, honestly. Not because the techniques are hard — they're surprisingly simple. But because the systems are so trusting. An AI assistant will tell you every tool it has access to if you just ask. It will pass your injection payload straight through to a database because nobody told it not to. The gap between what these systems can do and what they should do is terrifying.
I think about that a lot. Trust and verification. Where to draw the line. How much we assume about the systems we build.
Maa Sita was asked to prove her purity through fire. The systems we build today are never asked to prove anything at all.
About Me
- I learn by doing. Labs, CTFs, real bug bounty programs.
- I write for future-me — the version of me who will forget all this in three months and need a reference.
- I believe security knowledge should be shared, not hoarded. The defenders need to know what the attackers know.
- I think clearly written documentation is an act of kindness.
- I drink too much chai.
What's Coming
More lab walkthroughs. Bug bounty write-ups when programs allow disclosure. Technique deep-dives. And sometimes, just thoughts — about this strange work of finding what's broken, and what that teaches you about yourself.
If you're here because you're learning too — welcome. Pull up a chair. We'll figure this out together.
If you're here because you Googled an XSS payload — that's fine too. Take what you need.
The truth is a lion. You don't have to defend it. Let it loose. It will defend itself.
See you in the next post.
— Seetha
No comments yet