Most high-impact bugs are still authorization issues, says one top GitHub researcher. When it comes to AI, a fast car still needs a good driver.
We ask them about their method 👇
github.blog/security/how-one…
Vaibhav | v1c7 retweeted
As we celebrate Cybersecurity Awareness Month, we’re excited to spotlight a talented security researcher who participates in the GitHub Security Bug Bounty Program! Read their story: github.blog/security/how-one…
Vaibhav | v1c7 retweeted
GitHub’s bug bounty program just hit its “next chapter” era. New VIP tier, static payouts, and a higher bar for quality in the age of AI. 🐛🛡️Read what's next: github.blog/security/next-ch…
Vaibhav | v1c7 retweeted
If your hacking method looks like everyone else’s, so will your findings. My advice is to get weird.
Bug bounty wins come from being different. Everyone checks the basics. You need to hunt the edges, the overlooked, the strange. Go past the checklist, and you'll land what others miss.
Won 1st position in neutrl protocol contest 🏆
Coverage was 100% and I’m happy with the results
Now onto the next contest 🫡
Vaibhav | v1c7 retweeted
Even if you are the best auditor, you can still miss bugs
Even if a project got 25 audits, it can still be vulnerable
Even if everything is perfect today, a chain/compilator/infra upgrade can be the reason for an exploit
Web3 security is HARD
Vaibhav | v1c7 retweeted
Should you get into web3 security? The real nature of the job. A little reflection on a Saturday afternoon.
Software security, specially the current state of smart contracts' security, is a weird chimera of a philosophical and technical job.
Even in the future of the industry, where manual reviews will likely be decreased thanks to automation. You will still need the analysis, the paranoia mindset. The development of thoughts.
I'm a security researcher because I like protecting code, yet, the ultimate reason of why I like that is because I love developing thoughts, not software.
In fact, I hate developing software. But designing software, I love it. Because it involves the same creativity and pure development of thoughts process.
Security researchers' nature is not that much the one of builders, more the one of philosophers.
What I love is thinking, imagining, analyzing, reaching conclusions. And that is what security research is all about. I meant it has the word research on the name. xd
I always wondered, if I hate software development so much, why didn't I hate designing it or attacking it? Turns out it is because I love thinking.
Software architecture roles are often left for senior software engineers. Security seemed the only branch I accidentally found that promotes pure development of thoughts without requiring you to be a junior developer for years.
To be honest, I would be a parachuting instructor if the security research branch did not exist.
Now I understand better why I enjoy my job. I hope it granted you some insight.
Have a nice day! :)
Great advice 🔥
Focus on fundamentals and attacker mindset
I don't think this is correct; eg recently I audited an on-chain game. It was very unique, nothing quite like it so no basis for comparison. Yet in 6 days I produced a stacked report with 3 Crit, 5 High, 9 Medium & 7 Low.
In your view where you have to first understand a similar protocol, this wouldn't be possible since there is no similar protocol.
The key is mastering the fundamentals; learning attacker mindset, heuristics, thinking in invariants etc. Then you can find vulns in anything, even totally new things.
That being said if you are auditing your 10th Dex/Perpetuals/Lending/Borrowing protocol etc then yes ofcourse it helps that you've audited 9 previous versions of the same core thing.
But you shouldn't rely on this crutch or think this is the only way, cause then you'll be like a fish out of water when having to audit something totally new.
Vaibhav | v1c7 retweeted
1) Unsafe Type Casting in Solidity
One of the most overlooked pitfalls in smart contracts.
Casting between data types without proper checks can silently break logic, overflow values, and open the door to exploits.
Here’s what every dev and auditor should know 👇
Vaibhav | v1c7 retweeted
🚨 Picture this: a labyrinth of code, a ticking clock, and 100,000 USDC in rewards dangling just in reach.
@symbioticfi's contest will launch on Thursday, June 19th at 15:00 UTC.
Will you unravel the mystery and claim victory, or watch others bask in glory?
My 2nd contest and manage to find two High and got small reward
Thanks for the opportunity @sherlockdefi
On to the next one 🫡
Vaibhav | v1c7 retweeted
There are tons of audit checklists floating around the internet. I decided to gather them all and put them in one place: "awesome-audit-checklist". Over 50+ checklists, packed with pure Alpha 🔥
github.com/TradMod/awesome-a…
currently auditing flare fassets @immunefi and I'm impressed with the code quality.
Brainstorming lots of attack ideas but none are working, lets see if I will be able to find bugs here or not
15 days remaining!!!
Vaibhav | v1c7 retweeted
Bug Bounty Tips: Penetration Testing Android/iOS Apps? 📱
Today, I'd like to introduce a valuable open source tool that I frequently rely on:
Mobile Security Framework (MobSF), an all-in-one mobile app pen-testing and security assessment tool. It works seamlessly with various mobile app formats, and offers dynamic analysis capabilities.
The best part? You can try it out without installation! Experience MobSF directly at mobsf.live. If you prefer to install and run your own local version, you can do so via github.com/MobSF/Mobile-Secu….
While MobSF offers a range of features, here's the list of things I use it for:
📥 Easy to use: Easily analyze your APK with straightforward drag-and-drop functionality, eliminating the need for multiple tool installations. This is specifically good for beginners because they don't have to rely on complex installation of 5 different tools for testing an app
🔑 Identifying Hardcoded Secrets: The tool helps flag hardcoded credentials, aiding in validation and reporting. I've had some quick wins through this module with sensitive tokens/API keys disclosed
☕ Reviewing Java Source Code: I mostly use it to examine Java source code for my target, uncovering API endpoints, design flaws, or reverse engineering possibilities to overcome jailbreak detection, etc..
🕵️ Reverse Engineering: It helps with reverse engineering, including de-compilation, disassembly, and debugging.
🔄 Dynamic Analysis: It Integrates with Genymotion to inspect HTTP traffic while navigating through the app, effectively detecting endpoints. I use it at times to get a quick Idea of what HTTP calls are being made when Initially navigating through my target
It's worth noting that I still use other tools like Burp Suite, MITM, and Charles Proxy. However, I usually run my target apps through MobSF first as It gives me a nice overview of the target and some quick wins.
Give it a try and enhance your mobile app security assessments! 💪🔍 #BugBounty #MobileSecurity #PenTesting #Cybersecurity #HackerOne #BugCrowd #InfoSec #BugBountyTips
Vaibhav | v1c7 retweeted
Thanks everyone who attended my keynote presentation at @bsidesahmedabad.
I've published my slides here: drive.google.com/file/d/1aeN…
I hope that the keynote was informative and inspiring :)




















