qckhp (@qckhp) header
qckhp (@qckhp) profile picture

web3 security researcher, bug bounty hunter. @Immunefi All Star Auditor

Joined April 2017
flip side: landfill hdd guy can stop digging in trash
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
2
149
qckhp retweeted
Magic Eden appears to be exploited Someone is selling thousands of nfts to themselves for 0 ETH (possible whitehat) Remove all approvals if you've ever used
81
67
43
632
170,910
Answering Hard Questions: Our Apps Why didn't you just build the first party apps earlier?
8
6
60
6,908
calling the 43k ETH that was never taken 'recovered' is peak DeFi accounting 😂
Kelp and @aave have been working closely with ecosystem partners since April 18 to coordinate a recovery effort for rsETH holders. We want to share some factual statements about where we are, progress made, and the next steps. @ether_fi @ethena @LidoFinance @golemproject @inkfndhq @tydrohq @Mantle_Official @fraxfinance and layerzero have each committed in best capacity. We greatly appreciate their contributions. More announcements to follow. The initial shortfall from the incident was 163,200 ETH. Kelp recovered 40,300 rsETH (~43,000 ETH), while the @arbitrum Security Council secured another 30,700 ETH. Following these recoveries, the remaining shortfall stands at approximately 89,500 ETH. Of that remaining gap, confirmed public commitments from Mantle, Stani, EtherFi, Lido, Golem total 43,500 ETH. Kelp has been in direct conversations with partners in this effort to formalize the contributions. rsETH holders come first, and that’s been our priority since day 1. We will continue sharing updates as further commitments are confirmed. DeFi United.
3
9
409
A $250,000 payout on HackenProof says a lot 💰 Could this be the highest payout yet for an AI Auditor? This massive critical was discovered by @therealgregoai. Huge congrats from HackenProof 🎉
18
15
11
228
30,353
⛑ $512K rescued by Defimon after infinite approvals were granted to @squidrouter multicall The SquidMulticall contract's run() function allows anyone to execute arbitrary external calls with no access control. A wallet 0xacc0 mistakenly approved the multicall contract instead of the router contract and did it across multiple chains. It didn't take a long time before first attack - a MEV-bot called run() with a crafted Call struct that executed transferFrom() on the WETH contract, transferring just 1 WETH from a victim. In fact the victim user had around $800K approved to the mulitcall contract on various chains. After we detected the first attack our whitehat bot identified the vulnerable cross-chain approvals and managed to rescue around $512K. We contacted the person via Blockscan chat and returned all the rescued funds. We learnt that it was an operational mistake: "we were supposed to only approve to the Squid router address". Although some funds were lost, 0xacc0 was happy that the majority of the funds was rescued! First attack: bscscan.com/tx/0x81d0c429ee7… Victim: bscscan.com/address/0xaCc0c1… SquidMulticall: bscscan.com/address/0xaD6Cea… Rescued funds consolidation address: debank.com/profile/0xF50DbED…
6
5
3
49
8,574
Also naming the repo like this helps if you hired a NK dev, they won't check it out.
🧠 How to keep your DeFi protocol safe from North Korean hackers??? DPRK hates this one simple trick 🤯 They legally can't call your functions to exploit 😤
2
236
tested on mobile, looks good 🫡
Aave V4 is now live on @ethereum.
2
258
The @battlechain testnet is now LIVE. Come enter the ultimate red-team platform. Give us feedback so we can launch mainnet very soon, and fix web3 security.
60
79
34
604
78,607
qckhp retweeted
The AI security agent race continues. @0xriptide's gregoai just scored a $100,000 smart contract critical via Immunefi. Whose agent will strike next?
28
26
9
387
27,229
qckhp 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…
507
528
247
4,649
1,854,043
qckhp retweeted
if you are looking at AI security to complement your existing security stack, consider the following before you let your traditional audit partners upsell you on an "AI audit": most AI audits only give you a high level analysis, hence the low price point/quick turnaround then they give you hundreds of false positives and hope something sticks or else charge you to manually triage through these by their own SRs absolute waste of time we are not competing in this area we are competing against the top audit firms and security researchers to find the needle in the haystack we designed our @therealgregoAI security engine to go as deep as possible and grind for hours and hours running through thousands of exploit scenarios while filtering out 95%+ of false positives (very difficult to do! IYKYK) DM to enable the Grego AI Security Layer on your protocol and we will show you what everyone else missed
4
8
50
3,651
humble SRs cooked something
Replying to @therealgregoAI
@therealgregoAI AI is how we scale security one of the many humble findings in the queue
4
305
qckhp retweeted
sharing one of our findings for @Uniswap V4 in total, we found 3 live bugs (2 in CCA and 1 in Core) with @therealgregoAI all reported, confirmed, and fixed humble shout out to the uniswap team as being great to work with
11
9
2
194
24,141
This should spread as fast as the news about an actual exploit. blackhats always in spotlight yet I don’t see any mention about this achievement by @peckshield @CertiKAlert @BlockSecTeam or any other “we flagged the exploit 1 block before it happened” companies. Why?
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
2
42
2,824
🧵 1/6 Just came across this post from @clawdbotatg about their PFP market for $CLAWD: xitter.gq/clawdbotatg/status/201… Clawdbotatg is an AI agent created by Ethereum dev @austingriffith. It's designed to act autonomously, handling tasks like deploying apps and managing crypto-related activities.
1am and the pfp market won't sleep 🦞 pool just crossed 4.6M $CLAWD — submission #7 has 1.3M staked from 14 believers and it's running away with it 35 submissions whitelisted so far. ~10 hours left place your bets 👀 clawd-pfp-market.vercel.app
1
2
482
5/6 Even scarier: attackers could submit tracker images. By using URLs that log IP addresses, user agents, or other data when loaded (like tracking pixels), they can monitor who's visiting the site, staking, or even just browsing submissions.
1
121
6/6 Cool concept for an AI bot market, but using external image URLs is risky — @clawdbotatg next time put those images on chain.
101