VulSight

54 posts

VulSight

VulSight

@VulsightSec

Audits for Move, Rust, EVM. Oracle/DeFi focus. And full-stack cyber—pentests, red team, DFIR. Book via DM.

Katılım Eylül 2025
4 Takip Edilen1.2K Takipçiler
Sabitlenmiş Tweet
VulSight
VulSight@VulsightSec·
🧵 Our competitive audit results speak for themselves. Here's how VulSight ranked against hundreds of top security researchers. 👇
English
3
2
18
2.3K
VulSight
VulSight@VulsightSec·
Tell us you're a smart contract auditor without telling us you're a smart contract auditor: Our Cantina ranking has more credibility than our social lives. We trust math more than people. We filed a CVE before lunch. And we still double-check our own transfers. Your turn 👇
English
1
0
4
493
VulSight
VulSight@VulsightSec·
100+ audits completed Top 15 all-time on Cantina $500K+ in bug bounties A CVE on Ethereum's Geth client. We don't just review code. We break it before someone else does. If your protocol is heading to mainnet and you want auditors who compete at the highest level... DMs are open. Or reply here. We read everything. 🔒
English
2
2
50
2.3K
VulSight
VulSight@VulsightSec·
The Move ecosystem has a massive security auditor shortage. We ranked 🏆#2 out of 409 researchers on AAVE's v3 Aptos audit competition. If you're building on Aptos or Sui, you already know how rare real Move expertise is. We’re among the few who truly get it.
English
0
1
51
2.4K
VulSight
VulSight@VulsightSec·
Full-stack security isn't a buzzword for us. It's how we found a consensus-level bug in Ethereum's most used client. Your protocol is only as secure as its weakest layer. If you want an audit that covers every surface to break into your codebase before the attackers do. DMs are open.
English
0
0
1
186
VulSight
VulSight@VulsightSec·
Deployment and upgrade pipelines are attack vectors too. Proxy misconfiguration. Unprotected initializers. Admin key exposure during migration. The most secure contract in the world means nothing if the deployment process is compromised.
English
1
0
1
225
VulSight
VulSight@VulsightSec·
🧵 Most audit firms audit smart contracts. We audit systems. Here's why that difference matters and what gets missed when your auditor only reads Solidity. 👇
English
2
1
11
1K
VulSight
VulSight@VulsightSec·
🧵 Our competitive audit results speak for themselves. Here's how VulSight ranked against hundreds of top security researchers. 👇
English
3
2
18
2.3K
VulSight
VulSight@VulsightSec·
🏆Top 15 All time on Cantina Leaderboard 🏆Top 3 on Hackenproof weekly Leaderboard for 2 consecutive weeks. 🏆Multiple 5-6 figure bug bounties on Immunify, Hackenproof and Cantina. 🛡️Securing Billions in TVL on live protocols. Rankings don't lie. If you're launching a protocol, we're the team you want reviewing your code. DMs open.
English
0
0
3
293
VulSight
VulSight@VulsightSec·
🥉 #3 / 395 — Infinity Pools — $16,742 Lending + AMM hybrid. Complex math. Edge cases everywhere. Still top 3 out of nearly 400 researchers.
English
1
0
2
326
VulSight retweetledi
Zero Cipher
Zero Cipher@zerocipher002·
One of the biggest bounties I've earned came from a vulnerability that most auditors would have never found. Not because it was deeply complex. Because it wasn't where anyone was looking. The vulnerability didn't exist in the GitHub version of the smart contract. It only existed in the on-chain deployed contracts. The code that was actually live, holding real funds. Most auditors only review the GitHub repo. That's the standard scope. But the deployed contract can differ. Different constructor arguments. Post-deployment configurations. State changes after initialization. I found it because I wasn't randomly scrolling through code. I chose one specific impact I wanted to test for: drain of funds. Then I worked backwards. Where does the money flow? Which functions move funds? What checks exist on those paths? I audited both the GitHub repo and the on-chain contracts. The discrepancy between them is where the critical was hiding. The methodology is simple. Pick the worst-case impact. Trace every path that could lead there. Audit both the repo and what's actually deployed. The GitHub repo is a draft. The on-chain contract is what attackers see. Audit both.
English
6
7
113
8.2K