rX retweeted
7 BILLION DOLLAR crypto hack came from a homebrew install from someone tryna vibecode something 😭
rX retweeted
The sub optimal decisions in a trade get made while it's open.
In an active trade, the brain wants to rescue a position by manipulating stops and targets, in an effort to relieve the pain of not knowing.
The only way I found useful out of that trap is to have a decision tree for up to 5 different scenarios and "What will you do...." decision trees. Something you constructed in peace, before the trade, with all your faculties in check.
rX retweeted
Binance reopened withdrawals. I pulled some funds and it cleared in under a minute. Everything seems fine, but it's sad to see people here squeeze every bit of opportunity out of this event just to farm engagement by hating on, FUDding, and grave-dancing on Binance. Absolute scumbags.
Withdrawal Update
Withdrawals have now been restored for the following assets and networks:
- Ethereum Network: USDC, USDT, ETH
- BNB Smart Chain (BSC): USDC, USDT, BNB
We will continue to restore additional assets and networks in phases following the completion of our security checks. Further updates will be shared through official Binance channels.
rX retweeted
apparently the binance hacker had all his money frozen but he did a genius move so instead of having his funds stucked he used the stolen money to borrow ETH on aave and now Aave is the one stucked with frozen funds
jesus the north koreans are really good at this sht
rX retweeted
User funds are safe!
It does look like a hack on Binance. Appreciate the quick freeze from Tether (~$971m) and Circle (~$823m).
I don't manage Binance (.com) anymore, but as a shareholder, I expect all user funds will be fully covered.
rX retweeted
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.
rX retweeted
You’re bearish? Stan Druckenmiller is bringing Hyperliquid to the US and you’re bearish?
rX retweeted
The BTC ETFs have had steady inflows this week with another $137M yesterday
Now at $423M for the week
rX retweeted
Weekend beginning to so I think we can safely assume both sides of this bitcoin:native region will be run in the classic fashion.
