
Independent Security Researcher | Collaborating with @zenith256 @cyfrin @PashovAuditGrp | Available for private audits, Solana/Rust & EVM 🗓️
Book an audit ⇢
Joined March 2014
- Tweets831
- Following355
- Followers2.2K
- Likes3K
Pinned Tweet
Replying to @DadeKuma
Note: I just made this repo public, so it would be awesome if you could star it 🌟
I've also included an audit template that you might find useful for creating your own!
⬇️
github.com/DadeKuma/audits
I'm monitoring 5 critical/high severity bugs merged into main, but not yet included in a release. They're 99.9% ineligible for a bug bounty if reported right now.
I will disclose them privately once they are live. I'm no longer paying hundreds of $ in fees to platforms just to hear "thanks, but OOS" (learned this the hard way).
This would be so much better if bug bounty programs accepted pre-prod bugs, as:
- Blackhats can't exploit them yet
- Whitehats can find and help mitigate them before going live
Instead, reporting these bugs early zeroes out the impact, leading to OOS / $0 paid.
And blackhats could do the same thing: just monitor the bug and exploit it instantly once it goes live.
Whitehats who report it have to wait days/weeks, or even months.
Why isn't this a thing? Are companies really betting on finding these internally before release? If so, why were they merged into main in the first place?
Imagine if API fees were the actual cost for OpenAI and other SOTA models, and they removed subscriptions entirely.
That would mean whitehats are spending around $195,000 in tokens for a potential reward of $200K (let's generously assume this is the average), all while taking on massive risks like the project refusing to pay, or not finding any critical vulnerabilities at all.
Whitehats are cooked if bounties don't increase their maximum payouts.
4
33
4,511
DadeKuma retweeted
Understand code deeply. Embrace complexity. Explore different fields.
These habits helped these Zenith auditors find hundreds of crits and place top 5 in many competitions.
But they had more to share.
So we asked them: “What do you wish you’d known when you first started?”
Blackhats: get instant 20% reward, no max cap.
Whitehats: usually get 0% after months of waiting. If feeling generous, 10% with a ridiculously low max cap.
This quoted post is unavailable.
9
1,614
Please, don't let C4 die 🙏
Or that contests remain the most effective form of audit when it comes to finding more bugs faster per dollar than any other method.
@zellic_io should open source the @code4rena platform and operational manual so projects or foundations or VCs or @ethereum or @_SEAL_Org can run these as I always felt they were: public goods. cc @samczsun
2026 is officially the worst year for web3 ever 🥲
Replying to @code4rena
After careful consideration, we’ve made the decision to wind down @code4rena. This community has meant a great deal to everyone who has been part of building it, and sharing this news is not easy.
1
32
1,220
"Non-technical teams are now shipping production code"
Next news:
Coinbase gets hacked.
This is an email I sent earlier today to all employees at Coinbase:
Team,
Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future.
Why now
Two forces are converging at the same time. We need to be front footed to respond to both.
First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth.
Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day.
All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core.
What this means
To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice?
- Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles.
- No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.
- AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role.
In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs.
To those who are affected
I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done.
All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information.
To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements.
Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters.
How we move forward
To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together:
Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it.
The Coinbase that emerges from this will be more capable than ever to achieve our mission.
Brian
3
22
1,706
I hate this dumb AI timeline. Within a few years, 80% of current security auditors will be gone, and not for the reason you think.
People don't realize that AI costs are actually increasing with each new model, not decreasing. Companies are selling at a loss just to capture the market; they'll pull the rug once we're all fully dependent by massively increasing prices.
Those who rely entirely on AI have already stopped thinking for themselves. When this system eventually collapses, they will be left completely helpless.
DadeKuma retweeted
I Saved Injective's $500M. They Pay Me $50K.
I like hunting bugs on @immunefi . I'm decent at it.
- #1 — Attackathon | Stacks
- #2 — Attackathon | Stacks II
- #1 — Attackathon | XRPL Lending Protocol
- 1 Critical and 1 High from bug bounties (not counting this one)
Life was good. Then I found a Critical vulnerability in @injective .
This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk.
I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity.
Then — silence. For 3 months. No follow up. No technical discussion. Nothing.
A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either.
I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten.
I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve.
Full Technical Report: github.com/injective-wall-of…
Inspired by ily2, I temporarily paused private audits to focus fully on bug bounties a month ago.
My results so far:
- Submitted 4 High + 1 Critical. All valid, 100% signal.
- 2/5 were duplicates. Zero payout.
- 2/5 were closed as "Informative". The reasons:
- "We already know and are OK with it." No fix, no payment.
- The other one was a straight-up scam lmao. Fixed with no pay; reasoning was "behavior is considered by design." I can't say much, but it would've resulted in a permanent protocol DoS and locked funds.
- 1/5 Critical passed triage, pending review...
I'm going to keep grinding for a while.
WTF
Security researcher ily2 has just earned a staggering $3,000,000 from submitting a critical smart contract bug via Immunefi.
That's the largest single payout in web3 security in recent memory.
In total, he's submitted 3 reports. All 3 were paid. 100% accuracy.
His leaderboard update is coming soon, but you can pledge IMU to him now and earn when he finds the next one:
immunefi.com/pledge/ily2
1
13
1,091
DadeKuma retweeted
After years of working in security, I've launched Cyba Blockchain Security @cybasecurity
This is a long-term commitment to building security properly; beyond audits, beyond reviews or tooling alone.
Long road ahead, but this is the right one for me.
nitter.cf/CybaSecurity/status/20…
1/3
Cyba Blockchain Security is now live.
Cyba (pronounced sai-ba) is a researcher-led blockchain security firm focused on manual audits, deep protocol reviews and practical security research.
Founded by @abarbatei, with 10+ years of security experience across Web2 and Web3.
cybasecurity.io

















