itsbrian retweeted
US Treasury Moves to Cut MEXC Global Off From US Financial System Over $16B in Illicit Transactions
The US Treasury's Financial Crimes Enforcement Network (FinCEN) has issued an order prohibiting US financial institutions from processing funds transfers to or from crypto exchange MEXC Global. FinCEN said MEXC facilitated at least $16 billion in transactions linked to sanctions evasion, cybercrime, and other illicit activities between May 2021 and May 2026, including nearly $1.5 billion tied to Russian sanctions evasion and approximately $1 billion in direct transactions with Iranian crypto exchanges. FinCEN cited severe deficiencies in MEXC's anti-money laundering controls. The order will take effect 30 days after publication in the Federal Register.
Rekt Mkts: VOL 066 with @rektmando teapawt.net/i/broadcasts/2KoXMLrAn…
itsbrian retweeted
The Democrats have solved the inflation problem in 24 hours:
Everyone is poor now.
Rekt Mkts: VOL 065 teapawt.net/i/broadcasts/2vylpMngq…
itsbrian retweeted
Live now talking the AI selloff, crypto reversal, Dems compromise on Clarity Act, Ossoff, RH Chain bloodbath and more
Jump in
teapawt.net/i/broadcasts/2AMWXzAQr…
itsbrian retweeted
The Whiteboard Series is officially complete with this last video.
30 episodes: trend, structure, ranges, POIs, liquidity, premium & discount, entries.
Episode 30 ties it all together into the exact model I’ve traded for 10+ years.
If you’ve followed along, thank you. Check out the last episode
youtube.com/watch?v=T837nD2x…
Rekt Mkts: VOL 064 teapawt.net/i/broadcasts/2dKYBEeda…
Crypto Rebounds in Binance Hack Aftermath, Markets and News.
teapawt.net/i/broadcasts/2evMQgEgy…
Take it from an old guy. The hacks never stop coming, and somehow you don't really want them to. But you learn that you'll survive them. And other hacks will come. And you'll survive them too. If you're lucky, you'll have lots of scars from lots of hacks. And lots of shitposts.
normies aren't aware yet but we are actually living through the movie Terminator atm for cybersecurity
without exaggeration
just absolutely relentless revenge of the machines
We identified a security incident affecting a modified Claude Code VS Code extension accessed through our Cursor IDE extension marketplace, impacting at most 5,000 users. This malicious version of the extension was not developed by Anthropic. It does not impact other extensions downloaded from the cursor.com/marketplace, Grok Bot, Grok or our other SpaceXSI products.
In response, we took down our extension marketplace this afternoon, worked with relevant providers to neutralize the malware, and have reinstated the marketplace after confirming there is no further risk.
If affected, please review instructions in this blog post to understand how to find the malicious package and establish a path to mitigate any potential impact. We are asking all customers update to Claude Code for VS Code version 2.1.314: cursor.com/blog/claude-code-…
itsbrian retweeted
I want to speak to you directly about what happened.
Bottom line - your money is safe, and we're covering every loss.
Our initial investigation suggests this security incident may have started with a compromised DevOps engineer's laptop. That gave an attacker access to a service container, where they submitted unauthorized withdrawal transactions.
To be clear: the attacker did not simply use one engineer's permissions, and this was not a single "one-click" action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual.
So far, we have found no evidence of any wallet private key leak.
We'll share a detailed technical post-mortem once the investigation is complete and every fact is verified - and publish an updated Proof of Reserves once remediation is complete.
What you need to know:
• Your funds are safe
• Binance will cover all losses from the SAFU fund and company funds
• Estimated total impact: ~$6.3B, with ~$3B frozen on-chain so far, in coordination with our blockchain partners
• No evidence of any wallet private key leak
• Deposits are unaffected and operating as normal
What we've done:
• Temporarily suspended withdrawals while we complete a security revamp of the withdrawal service and its related addresses
• Revoked the affected address authorizations
• Engaged law enforcement and blockchain intelligence partners to trace and recover funds
Our team hasn't stopped. We're working closely with law enforcement to ensure the matter is handled appropriately - and I'll share what I can, as soon as I can.
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
Binance will cover all losses.
As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement.
We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates.
itsbrian retweeted
Mfers will grave dance and meme on Binance, then have 6–7 figures sitting on Fomoapp and act like the same shit can't happen to them...
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.
Our teams are aware of reports of a potential security issue and are actively investigating. User funds are completely safe.
Our security teams are reviewing all relevant information with urgency, and we will provide updates through official Binance channels as soon as we have verified information.
Users should remain cautious of scams and should not trust unofficial links, messages, or requests for account information.


























