Adekunle Faheez (@mibunna) header
Adekunle Faheez (@mibunna) profile picture

I’m a simple man, all i want is everything.

Joined March 2025
Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)Photo by Adekunle Faheez (@mibunna)
I wrote an article in form of a series called "Spotting Vulnerabilities in Smart Contracts" In these series I will be writing about my personal experience during audits. The first part is titled "The Ghost in The Constructor", I hope you enjoy it and learn from it as well.
4
4
40
1,699
🏆 Audit Arena Week 19 results are inBig congrats to this week’s top performers: 🥇 @mibunna 17 pts 🥈 2nd place: @SyedGhufranHas1 @zriym17 9.5 pts 🥉 3rd place: @yun0hu @0xbube @mr_nob0dye @0xEzed 8.5 pts 4th place: @devmukhtar @maFa_686 @254Oti_ 7 pts 5th place: @acyutaharidas 5 pts 6th place: @GeorgievWeb3_ @royysd 3.5 pts Big congrats to everyone who took part this week.Keep pushing. Keep learning. Keep climbing.⚔️ See you in the next arena.
3
7
16
987
I’ve noticed a pattern amongst protocols that get hacked, the hacked codebases are not usually in scope when they go for audit Where I now have a problem are the ignorant web3 folks that rally against audits, what do they think will happen if protocols dont go for audits at all?
5
151
Update: The contest had zero valids, two out of the three H/M issues were invalidated due to trivial assumptions. The tool has a great potential which I will further test out in the future. Till then📽️ @0xriptide was the lead researcher of the contest by the way.
Was busy with other engagements and I couldn't participate directly in a recently announced contest, so I had to employ @hakiraio on my behalf since it's a mini codebase. And to my surprise it delivered, I'm impressed with how far AI agents have come.
1
98
🏆 Audit Arena Week 13 winners Another strong week in the arena. 🥇 @mibunna 21 pts 🥈 @0xbube 19 pts 🥉 @SyedGhufranHas1 @yun0hu @auditor_nate @crypticmind001 13 pts 4th: @devmukhtar @mr_nob0dye @maFa_686 @Thragg_0ti @idontmintrugs @kalyan__tr 10.5 pts 5th: @tobechukwuazogu 9.5 pts 6th: @waiwaTF 7 pts 7th: @GeorgievWeb3_ 6 pts 8th: @iam_ayanfeoluwa 3.5 pts Congratulations to the winners! On to Week 14.
4
4
2
25
1,206
🏆 Audit Arena Week 12 winners are in. This week was pure pressure. A lot of strong auditors entered. Only a few came out on top. 🥇 @Bobai23_ 5 pts 🥈 @mibunna 3.5 pts 🥉 3rd place: @yun0hu @0xbube @devmukhtar @nwoke_ephraim @mr_nob0dye @tobechukwuazogu @auditor_nate @GeorgievWeb3_ @maFa_686 @Thragg_0ti @0xTona_ @iam_ayanfeoluwa @idontmintrugs @crypticmind001 2.5 pts Respect to everyone who showed up and put their skills on the line. The arena rewards reps. See you in Week 13 ⚔️
2
3
1
15
462
Was busy with other engagements and I couldn't participate directly in a recently announced contest, so I had to employ @hakiraio on my behalf since it's a mini codebase. And to my surprise it delivered, I'm impressed with how far AI agents have come.
2
2
1
16
831
The output is pretty impressive too, I must say.
5
104
My public address- 0x401e502fbAD21EA437F95e8c219f5E9C18F2d0C4 #ethsecurity
1
55
Done with this bih baby!
The universe is so funny, look at contests spiraling out while I’m having exams And i can’t even split my time cause it’s my finals, I’m pained
1
4
98
The universe is so funny, look at contests spiraling out while I’m having exams And i can’t even split my time cause it’s my finals, I’m pained
4
1
1
13
638
Ready for whatever you are cooking 🥘
Competitive audits… but better
5
304
I think even this platforms need special advisers Their new implementations don’t cut it most times
Everybody's complaining about contests going downhill. Platforms have an AI problem. But they're solving the wrong one.
1
122
AI has replaced you brother
Hey fellow researchers. Getting back to auditing after 6 months. What are most important things i missed?
2
5
1,164
The amount of hacks within these past few days is alarming, what the? That’s to show how imbalanced the ecosystem is, the dark side is winning
2
67
🏆 AUDIT ARENA WEEK 4 WINNERS 🏆 The fourth challenge is officially closed. Here are the final standings 🥇 1st @itzshreyashh 🥈 2nd @0xbube 🥉 3rd (tie) @Bobai23_ @SyedGhufranHas1 @0xgritty_twts @mibunna @zriym17 @SachetDhanuka 4️⃣ @yun0hu @nwoke_ephraim 5️⃣ @DavidAd05917946 @darkstarpp 6️⃣ @__Shafeeq0x @devmukhtar @scarcemrk @itzz_okure @sharma6019 7️⃣ @KalpShah_eth 8️⃣ @shiazinho @mr_nob0dye 9️⃣ @StrangerMontana Massive respect to everyone who participated. Level keeps rising every week! See you in the next arena ⚔️
1
7
2
18
1,243
Adekunle Faheez retweeted
Since this rant is a roller-coaster of topics, I will divide it into four sections. 1-) How do the best bug bounty hunters deal with problematic project teams? Spoiler: they are mortals like us and can't magically fix anything. I think that by listening/chatting with the best bug bounty hunters, I've understood their strategy: Just keep hunting. From the start, they choose the target mindfully. Hunt on bigger targets (in terms of TVL and bounty size, read this amazing article by @WhiteHatMage on this: whitehatmage.github.io/posts…) but even then they don't assume that the process will go smoothly, and they focus on finding new vulnerabilities on a different target while their existing reports are being (not) resolved. They try to create as many opportunities as possible so that some bad faith actors won't totally stall them. However, this doesn't mean they don't care about unresolved reports. On the contrary, they behave very professionally in messaging channels and do not let go of a project that tries to avoid paying. This is their full-time job, and they want to get paid. 2-) Why this sucks? Unfortunately, the above situation shows how inclined we are to create more black-hats than white-hats, because there are only two scenarios that can create the incredible level of devotion I mentioned above: * You received one large payout, and because of that, no matter how many bad experiences you have, your belief that another large payout will come never fades. * You have an incredibly strong attraction to feeling like a hero and doing what is ethically right. Note: Many people do bug hunting *occasionally* (like myself), and the situation is completely different for that case. These two scenarios are related to creating devoted full-time bug bounty hunters. If we don't have established standards and legal enforcement (aka incentives), we will remain limited to creating only a ridiculously small number of consistent elite bug bounty hunters. We shouldn't wait for every project to get hacked in order for them to get incentivized to allocate more resources to security. 3-) Market actual security, not your newest product. Because products/services will change over time -- sometimes it will be AI, sometimes audit competitions -- but the need for security will never disappear. What we need to show project teams is not just which fancy tool to use to achieve security, but that they genuinely need a “security-first” mindset. Security is not achieved through a single best product, but rather by getting various services. Instead of only launching a large bug bounty or only paying for one expensive audit, distributing the budget across both of these will produce a much better outcome. It feels like, instead of sharing the pie wisely, we are allowing most of it to be captured by the newest trend. Nothing done with a “let's not miss the boat” mentality is truly innovation. There will be some successful products/services, but most of them will be forgotten, sunset, or be forced to evolve. 4-) Not all founders have been reading @RektHQ for years like we do Maybe you don't think much about it, but it is also important to realize that not all project teams have the same level of maturity. They just don't really think they need to allocate much to security. We need to teach some VCs that security is an actual thing and not a fucking marketing tool. You wouldn't believe how often I've heard bug bounty hunters say about major projects that “X project's codebase is terrible / is a mess.” Do you think the developers, founders, and VCs of those projects are even aware that this is the case?
seeing all the horror stories on here about bug bounties, and having lived some myself, i don't think i can see myself ever bounty hunting again we desperately need to radically rethink the incentives here
1
4
15
1,363
It’s crazy how much a deadlock can change your entire perspective
1
6
191
Adekunle Faheez retweeted
early returns and try/catch blocks account for 80% of my income as an auditor: developers are humans, and humans tend to put more emphasis on happy paths and the most traversed paths. With early returns, it often happens that crucial code is skipped (state updates, accounting, access-control bookkeeping). In the replies I’ll share a SOLO finding of mine that encapsulates this concept. That one bug alone paid $5k. try/catch blocks are a similar beast, they break a core concept of blockchains (and distributed systems in general) that transactions are Atomic: they either fully succeed or they revert. Similar to early returns, it often happens that failing external calls are accepted and downstream code keeps running with assumptions that were only true if the external call succeeded. Both of these patterns create "parallel universes" where state, assumptions and outcomes are different from the main path. these bugs are very commonly missed in tests too as devs tend to test happy paths more. Devs: Add tests for every early return and every catch branch. Auditors: check every execution branch with the same focus of the main ones
1
1
15
754
Adekunle Faheez retweeted
I’ve worked with billion-dollar protocols and organised ~150 security audits over the past 3 years. Here are 5 rules every Web3 project should live by in 2026: (BOOKMARK AND RETWEET) 1. Don’t rely on AI security alone before mainnet We are not there yet, and we won’t be there anytime soon to rely only on AI for security. AI should be leverage for auditors, a tool that helps them deliver better results, not a substitute. Dev teams running automated tools and calling it an audit is absurd. That’s how you start getting hacked. Security can be expensive, but it’s mandatory and existential. If you had $50M stored in your house, wouldn’t you invest heavily in protecting it? 2. High-paid devs ≠ secure code I’ve spoken to many founders who believe that because they hired expensive developers, mistakes won’t happen. They will. Everyone is biased toward their own code. Security requires an unbiased, professional opinion from a dedicated audit firm. Never assume your devs can’t make mistakes, because that assumption can cost you everything. 3. Clear documentation reflects a clear threat model This is extremely important for auditors. The clearer your documentation, the faster and more accurately they can understand your protocol and its intended behavior. If it improves the auditor’s work, it directly improves your security, so there’s no reason to neglect it. Messy or incomplete documentation increases risk and frustrates both auditors and users. You also need well-structured contracts and proper NatSpec reduce audit blind spots. Good structure makes complex systems easier to reason about and reduces the chance of missing critical issues. Follow the official Solidity guidelines and keep your code clean and consistent. Poor structure hides vulnerabilities and slows down the entire audit process. 4. Too many Crits and Highs? Don’t deploy If you have lots of Critical and High findings in your first audit, that’s a clear signal there are likely more bugs in the codebase. An audit is a time-restricted engagement, and if the system is full of issues, not everything may be uncovered within scope. That’s not the auditor’s fault. In this case, you need a second audit before even considering mainnet. 5. Have a detailed incident response plan You may think it can never happen to your protocol, but no one is 100% safe. There is always a real chance something goes wrong, and you need to be prepared. You need: • Clear communication strategy • Defined roles and responsibilities • Precise steps in case of a hack • Pre-made decisions such as pausing contracts or freezing assets Everything should be prepared in advance, down to the last detail.
3
4
27
1,668
How the ecosystem went from “We need more security researchers” to “We have an AI for that” in less than 24 months. In my recent article, I covered the current position of AI in the industry and how junior auditors can move past the noise while focusing on what really matters.
3
2
3
11
1,087