avid reader engineer of things
dark forest
Joined February 2021
- Tweets740
- Following5.7K
- Followers52.5K
- Likes58.6K
Pinned Tweet
Proposed to my partner in front of Mt. Fuji at sunrise
(she said yes)
You can just do beautiful things
Everything is computer
And computer is absolutely fucked right now
ok safe to say binance is pwned
The biggest assets were approximately:
• 1.615B USDT
• 62.6M RLUSD
• 29,934 wBETH
• 11,372 XAUt
• 6.19M UNI
• 198.4M ENA
• 7.175T PEPE
• 27.8M USD1
• 2.26M LINK
• 127,853 AAVE
about $2.5B at the explorer’s prices.
1. The attacker deployed a delegate contract, 0x63e842b0...73e9c6fAe, from the relayer at 15:59 UTC.
2. About four hours later, the relayer submitted an EIP-7702 authorization transaction
That installed the malicious 7702 delegate code on Binance 14.
3. The relayer then made a call to Binance 14, executing the delegate code, and transferring Binance 14’s ETH and token balances.
4. The calldata is labeled sweep(address, address[]). The second argument is a list of recognizable token-contract addresses plus the zero-address (eth).
5. The same relayer later used the same delegate to move 780M USDC from Binance Hot Wallet 34 into the same pool
• The relayer 0x7C... was funded by three Tornado Cash 0.1 ETH withdrawals over the prior two days.
• The same pool also received 28,005.6 ETH from Binance 16 24 seconds after the main sweep.
• The pool then forwarded 195,460 ETH to a fresh, unlabeled EOA
• That EOA has only one transaction and currently holds the 195,460 ETH.
What's a bit unclear is why the relayer was needed in the first place. If they had the private keys to the Binance wallets, they could have just sent the assets out in an atomic bundle without needing a relayer at all.
So it seems likely that they didn't have the private keys and instead just had the 7702 auth signatures, which must have been phished somehow.
I think we can go ahead and assume DPRK.
Everyone tweeting about futures being green of course there won’t be a black Monday is sick in the head
You really want to tempt fate in this absurd world? Reading those posts makes me think it’s 5x likelier to happen not less
It’s so funny to see the $TRUMP mm’s try to pump it right before another set of unlock nukes
This coin is going to literal $0 and I will enjoy every step of it
There are few things as enjoyable as someone trying to negotiate with you on Facebook marketplace and just saying no
I’d rather throw this motherfucker away than let you get $3 off
If you cheered on or worse were an insider to trumpcoin you should probably just shut the fuck up about the hunter biden coin
Yes it’s a scam but you’re already a clown no reason to be a hypocritical clown
I remain impressed by how many people in CT haven't given in to complete cynicism although I think a fair amount of that is acting non-cynical to induce others into following them
I do not believe in your flywheel
I do not believe your liquidity pairings are a differentiator
In an age of things being easier to build than ever we still simply see a rotation to a new chain and a replay of the same meta
The premise and promise of crypto was so much more than it has ever achieved in practice
I have no real issue with using AI to help build mint sites and such
But if you're an artist who has historically put a lot of work into your brand, I think trying to keep LLMisms out of the language is important to an experience feeling more refined and designed
Finally watched obsession and my god
Just two straight hours of being unnerved
Even better is that my partner has always called me Bear 😬😭
My prior is that the KOSPI pump will get slammed down again
Anytime you get a big nuke in leveraged assets, the people who won and now have the capital are the shorters
You’ve moved the means to move the market to the bears
Financial infrastructure companies should **not** let their clients hang themselves with their own rope
Just because AWS lets you run single AZ databases doesn’t mean the same logic should apply to a bridge provider. If a minimum config exists, it will be used.
LayerZero is at fault along multiple axes here while absolving themselves of everything.
Crazy how much this is written to distance themselves from blame when it was fundamentally a successful attack on their infrastructure.
Yes, the kelp team should’ve multi-DVN’d. But they still lost control over multiple incredibly sensitive parts of their stack and have clear blame here. It’s not like they weren’t internally aware that they had clients with 1/1 DVN setups with 9 figures at stake.
Also whoever pulled this off seems to have deep insight to the internal security architecture of LZ.
The tail risk in crypto has dramatically increased
Another data point in favor of the theory that we are currently undergoing the Computer Security AIpocalypse: an AI-augmented white-hat researcher discovered and reported a vuln in the old Zcash “Sprout” pool: nitter.cf/zooko/status/203905768…
I have sympathy for every drift user and 0 for the team
With what happened to bybit + every other admin key compromise, you have a duty to handle admin keys way more seriously
With $200MM at stake I expect institutional grade safety around upgradability/keys
It is their failure
