AI / LLM Security
The newest attack surface, shipped weekly. I test LLM features for prompt injection, data leakage, insecure tool-use and model abuse — and weaponise GPTs to accelerate the hunt itself.
Offensive Security · AI & Cloud · Available for engagements
I break into things before someone with worse intentions does. As an offensive security consultant I think like the attacker against banks, fintechs and the platforms that move people's money — chaining the small oversights everyone overlooks into the breach that actually matters, then handing the team a clear way to shut the door for good. Lately that means securing the AI features and cloud-native stacks teams ship faster than they can test.
I spend my days pretending to be the adversary. As an offensive security consultant at NetSentries, my job is simple to say and hard to do: get in the way a real attacker would, prove what it costs, and explain it clearly enough that it actually gets fixed. Most of that work lives in finance — banks, fintechs and the systems behind people's money — where one broken access check is the difference between a headline and a non-event.
I work black-box and zero-knowledge on purpose; I'd rather earn every piece of access the way an outsider would than be handed a map. When the manual testing gets repetitive I write Python to do it for me — the same instinct that's led to eight published CVEs and thank-yous from 300+ organisations, Google, Sony and the BBC among them. Off the clock I hunt private programs on Bugcrowd and Yogosha, and I run The Cyber Explorers to pull more people into this field.
I'm equally at home as a security analyst — turning the noise from a dozen tools and a sprawling attack surface into a clear, prioritised picture of what's actually exploitable and what it would cost. A growing share of that is now AI / LLM penetration testing and cloud security, pressure-testing the models, features and infrastructure teams stand up faster than they can secure.
The newest attack surface, shipped weekly. I test LLM features for prompt injection, data leakage, insecure tool-use and model abuse — and weaponise GPTs to accelerate the hunt itself.
Cloud is the new perimeter. I hunt exposed buckets, over-permissive IAM, leaked keys and metadata SSRF across AWS, GCP and Azure — turning misconfigurations into demonstrable impact.
Where the real money still hides. I go deep on auth, access control and business logic — the flaws a scanner can't reason about — not just the easy reflected XSS.
Modern apps are just APIs wearing a UI. I pull apart REST and GraphQL for the broken-object-level-auth and mass-assignment bugs that quietly hand over other people's data.
Once I have a foothold I look for the way up and the way across — the misconfig, the forgotten host, the reused credential that turns one box into the whole network.
Half of every engagement is finding what the target forgot it owns. I map the full external footprint and mine open and dark-web sources for the exposure nobody's watching.
I'd rather build the tool once than run the same check a hundred times. Python pipelines turn my recon and exploitation into something that scales across an entire program.
Not a checklist — a story. I replay real threat-actor TTPs end to end against the MITRE ATT&CK matrix so a client sees exactly how a breach against them would unfold.
People are the perimeter. I run convincing phishing and post-exploitation campaigns with Evilginx and Gophish, then turn the fallout into training that actually sticks.
NetSentries Technologies
FireCompass ★ Star Performer
Bugcrowd · Yogosha Strike Force
Codewits Solutions Pvt. Ltd.
Eight published vulnerabilities — each a real flaw in real software, found, reported and credited to me.
A practical, no-fluff roadmap I wish I had when I started. Bug bounty rewards consistency over talent — follow the path, build the fundamentals, and let the depth compound. Work only inside authorised scope and always read each program's policy first.
Understand how the web actually works before you try to break it.
Study the OWASP Top 10, then go deep on a few beginner-friendly, high-yield bugs.
Practice in safe, intentionally-vulnerable environments before going live.
As a beginner, lower the competition before you chase the payout.
Map the attack surface before firing payloads — depth beats breadth.
A great report is half the value — make impact undeniable.
The mindset that matters: you will get many duplicates, N/As and informationals before your first valid bounty. Treat every "failure" as recon for the next target. Stay in scope, stay ethical, and never stop reading other hunters' write-ups.
A reusable workflow for approaching any target. Tick through it top-to-bottom — your progress is saved locally in your browser.
I take on penetration-testing and red-team engagements, private bug-bounty invites, and security collaborations. If there's a target that's been keeping you up at night, let's talk.
rootxvishal@proton.me