CryptoCoBean (@CryptoCoBean) header
CryptoCoBean (@CryptoCoBean) profile picture

Surviving crypto since May 2021 | @thehyperpodcast | https://nitter.gq/t.co/cLfPtvakWd

Joined September 2021
Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)Photo by CryptoCoBean (@CryptoCoBean)
Feels as though if we're going to get some form of downside acceleration based on a catalyst we're in a good spot for that on the indexes and BTC.
22
3
2
172
29,250
Can’t wait for $ANT to be just like every IPO ever
50
104
14
1,890
331,121
CryptoCoBean retweeted
btw golden rule of our sector is immediately withdraw everything get your funds off lighter it doesn't matter if this is just a small 10m hit or not
I obv had and still have what most would consider significant exposure to Binance. But I also withdrew a much bigger amount the moment rumors spawned, which is why I shitposted about it to warn even when news didn't arrive in feeds yet, just to play it safe as tx were never this fast & cheap. There were ~43h between the initial FTX rumors and FTX freezing withdrawals. The first paranoid schizo to leave gets clowned 99/100 times for "wasting" effort, but doesn't lose millions in the 1/100 case. Additionally, for exactly moments like this, I always recommend utilizing leverage alongside strict risk management to minimize capital held on venues in case withdrawals don't succeed. Always min-max your capital exposure, especially on LTFs. There's never a reason to park inactive liquidity on venues. Although leverage has the gambling image, it fundamentally remains a capital efficiency tool.
13
10
1
213
11,651
CryptoCoBean retweeted
Market so bad Donalt decided to do another Technical Round up episode without a sponsor
1
3
74
CryptoCoBean retweeted
Now that you can post 20 pics, here are 20 of the best CT posts of all time
112
241
37
1,922
115,688
CryptoCoBean retweeted
Just fyi, i'm shutting the stonk board down eom. It's incredibly data intensive and incrediblly expensive to maintain. We went from over 10k dau to almost zero... partially bc stonk's decline but also bc other devs stepped up and created competing products... some of which are quite good. I appreciate you guys using and loving something I made. 🫡
73
10
7
703
36,878
CryptoCoBean retweeted
Only way to bottom is if we all start MAX BEARPOSTING. The Finex Whales [Tether Mafia] will see it and countertrade us. ~ Dr. Axius.
51
18
9
530
36,949
CryptoCoBean retweeted
Most of you may have used MEXC one day. Your wallets may unfortunately soon get flagged in a lots of places. Dura lex sed lex. But the order is effective 30 days after publication in the Federal Register. If you have funds, much easier to pull out today. And if your wallets ever touched MEXC, send funds now to a regulated exchange and withdraw to a fresh wallet from there. Better safe than sorry. Oh and btw, no Hyperliquid season 3 for you.
[ ZOOMER ] US TREASURY SANCTIONS MEXC, SAYS THEY ARE LINKED TO SANCTIONS EVASION BY NORTH KOREA, IRAN, AND RUSSIA: FINCEN
44
24
3
422
62,543
CryptoCoBean retweeted
its riveting how well this signal works time and time again in crypto
18
25
1
474
30,045
Binance published the postmortem on its $6.34 billion hack. It started in June. An engineer searched for an AI coding tool. Downloaded a tampered Homebrew installer. Binance caught it. Replaced the laptop. Rotated the credentials. But the attackers had already learned who worked on the wallet team. September. A second engineer gets approached on a real job platform. By someone posing as a project director. Live video interview with "HR". Then a take-home assignment. Downloaded onto a work laptop. The assignment swapped pyenv for a malicious copy. Binance's security tools didn't flag it. October 20. The attacker used that machine and Binance's own internal AI tool to reach two more wallet engineers. One had a container deployment token sitting on his laptop. October 29. Container deployed. Signing service reached. Funds started leaving at 20:05 UTC. Binance suspended withdrawals. The money kept leaving. The attacker had already authorized his own contract on the hot wallet, on-chain. Halting withdrawals didn't touch it. Revoking it was harder. The wallet uses MPC. No single private key exists to sign the revoke. So Binance had to design a revoke procedure while the funds were still moving. The last stolen ETH left almost four hours after the first transfer. The security model designed so no one person could steal the keys. Also meant no one person could stop it. Binance says it recovered about 2.85 billion. And put aside enough to cover the rest. The FBI says North Korea did it. Five months of recruiting, interviewing and waiting. The most expensive take-home assignment ever submitted.
Binance just published how $6.34 billion walked out the door. June: an engineer searches for a popular AI coding tool, clicks a search result, and installs a tampered homebrew. Binance catches it, replaces the laptop, rotates the credentials. the attackers now know who works on the wallet team. September: another engineer gets a job offer on a real job-hunting site. first-round interview with “HR” over live video. “HR” shares their social media, personal photos and videos included, so he trusts them. second round is with the “CEO” of a company that doesn’t exist. at the end of the call he’s asked to download a take-home “assignment” onto his work laptop. the assignment quietly swaps out pyenv for a malicious copy. No antivirus flags it. october 20: the attacker uses binance’s own internal AI tool to get into two more engineers’ machines. One of them has a container deployment token sitting on his laptop. october 29: container deployed. Signing service reached. $6.34 billion moved. Binance shut off withdrawals. the money kept moving anyway, because the attacker had already given their own smart contract permission over a hot wallet, on-chain. binance’s off switch didn’t reach that far. then they tried to revoke the permission. the wallet uses MPC, so there’s no single private key to sign the revoke with. they had to build a revoke procedure on the spot while funds were still leaving. last stolen ETH went through at 23:56 UTC. almost four hours after the first transfer. Phew!
178
604
94
6,506
670,260
CryptoCoBean retweeted
We identified unauthorized activity affecting our GitBook documentation earlier this morning. The documentation was fully restored to its previous state as of 9:15 AM ET. As a precaution, we advise users not to click on any links within the documentation while our investigation remains ongoing. We are actively reviewing the incident and will provide further updates as appropriate.
73
133
73
1,080
137,210
CryptoCoBean retweeted
Wake up Binance hacked for like 6B Expect price down 30% Down 3% Not sure if strength or the nuke is just delayed If price isn't down significantly by Monday bottom of this bear market probably already in Might just have to go through hell chop to digest this
218
283
32
5,779
403,805
CryptoCoBean retweeted
I think the number is potentially up to $5.8B. Tether has blacklisted a large portion of this.
Hackers have withdrawn $3.5B+ and counting
9
23
10
249
39,283
CryptoCoBean retweeted
Patiently waiting for the next higher low to form. Once that's done, we can get the real show on the road. $BTC
27
22
2
374
21,671
Evolving thoughts on @papertrade_xyz as the farmers have realized they haven't got a trade anymore The house is making a fraction of what it was, farming isn't viable, so what's left is probably real business Its enough to be a real business but not a great business imo
4
1
1
61
6,760
CryptoCoBean retweeted
Solana is now 95% faster trillions
biggest upgrade in solana history today
290
430
127
4,330
229,832
CryptoCoBean retweeted
The sooner you quit anything pumpfun or memes related, the faster you actually make it Or you will continue reading the slop post farming the hopeless & children for the next cycles - your choice
48
63
12
782
34,358
CryptoCoBean retweeted
Compiled a list of protocols that have shut down in 2026. 82 protocols year-to-date. I've never seen anything like this before.
180
146
97
943
196,011
CryptoCoBean retweeted
Made a thing to make HyperCore node runners lie easier. You can find the whole map of HyperCore nodes, how fast they are to forward blocks and RTT in Tokyo. Building those for @proliquid_xyz to get the fastest data on orderbooks, screeners and perps prices. Sharing it to everyone peers.proliquid.xyz Hyperliquid.
4
4
1
29
2,553