Where code whispers its secrets, Koroksec listens intently. We dive deep, hunting bugs where others neglect to look in new ways. In a world quick to expose, we prioritize thoughtful discovery and responsible unveiling.🧵1/5
Choosing Koroksec isn't just about security audits. It's about joining forces with a dedicated team of hunters who are committed to the unfaltering security and prosperity of your protocol. 🧵5/5
Where code whispers its secrets, Koroksec listens intently. We dive deep, hunting bugs where others neglect to look in new ways. In a world quick to expose, we prioritize thoughtful discovery and responsible unveiling.🧵1/5
As DeFi evolves and introduces new challenges daily, it's not enough to be reactive. Every project must stay one step ahead of threats. Our vision? A DeFi landscape where protocols operate confidently, free from the shadows of vulnerabilities. 🧵4/5
Found a quick and fun bounty w/ @erc1337_Coffee after hunting for only a little over an hour- some are evident right away when you’ve studied hard and stay focused
Here's the story of my first bug on @immunefi 🐛😱
The timeline from choosing the program to getting paid was ~7 days 🔥
- payout: $1k
- severity: Low
- program: IPOR
The full story ��� 🧵 (1/9)
Thrilled to share that I will be hosting private audits soon! @erc1337_Coffee and I will be launching them through @koroksec so stay tuned for more info 👀 In the meantime check out the new website https://t.co/0EimLv8e9B 🎉
I love the simplicity and ease of use of Github, but it still feels so proprietary and monitored— alternative Git implementations are great but aren’t being picked up yet
.@SoloditOfficial is one of the best tools that you can use when doing vulnerability research- go use it now if you aren't already! You heard what the man said.
It’s INSANE how many people this article by @cmichelio has reached; probably one the most impactful pieces of media that piqued the interest of thousands of soon-to-be auditors: https://t.co/ebcVYmuzGi
I find it a lot easier auditing contracts that have clear paths of execution. If a function is only meant to work on values of 0-1000, then make that explicit with require statements. Devs can't assume users will always use correct inputs.