Pinned Tweet
Finally I met my boss CZ
It was like a dream 😍🤩
Very happy 😁 to see him today in #BinanceBlockchainWeek at #Paris 💙
He is my idol, the man who is full of positive energy, our teacher&leader and he is the true meaning of a leader
Pleasure to meet you @cz_binance 🙏💞
I'm proud to stand alongside the Binance Angels community through challenging times, and I remain confident in the value of standing together
Stronger Together. Always Building🚀🔶💛
#BinanceAngels #Binance #Web3 #BinanceHack
Full support, Richard and the entire #Binance team! 💛
We stand with you through this challenge. Your commitment to users and willingness to take responsibility mean a lot
Together, we'll weather this storm and come back stronger
Stronger Together. Always Building!🔶💛
Replying to @_RichardTeng
TRANSCRIPT:
Hi everyone, firstly, I want to thank you all for the support. Difficult times like these are a great reminder how strong our industry is when we work together.
We are grateful to our partners that acted quickly to freeze the hacked assets; to global law enforcement, who we’re working hand in hand with to seek justice;
But most of all - we are grateful to our users for their patience and understanding.
Rest assured that we are working non-stop to resolve this, to make the users whole, and live up to your trust.
I want to be clear: WE ARE COMMITTED TO COVERING ALL HACKED LOSSES THROUGH OUR COMPANY FUNDS. Your assets are safe.
The good news is that we are recovering stolen assets for users.
Binance has reserved over $6.34B of company funds to cover the stolen assets. $5B of these funds are already held in the exact token assets that were impacted, such as USDC, USDT, BTC, ETH, BNB etc.
I know many of you are still asking the same question: how can Binance actually prove that your assets were not affected?
Let me be direct about the first point. We NEVER use any customer funds, so they are not impacted. What was affected in this incident was Binance's own hot wallet. User assets are held under Binance's established security architecture. The vast majority sit in cold wallets, and are only moved into a hot wallet when a user makes a withdrawal.
One more thing I want to share. Binance has always been built for the long term. Most of what we earn from day-to-day operations is held in crypto assets. We have kept a lot of them in the company, and reinvested them — into the business, and into security. Because we believe in crypto, and in the long-term value of this industry.
That is precisely why we are able to absorb a loss of this size, immediately, with our own money.
We are working on the outstanding amount by buying the token assets through market and OTC channels. We will share more progress as soon as we can.
If you, as a user, are concerned, we encourage you to check funds on your Binance accounts. Wait for our initial Proof of Reserve for public verification, which is targeting Monday. You can reach out to our customer service with any questions.
Next, I want to give you an update on our understanding of the hack itself.
Our tech and security teams are still deep in the investigations of the hack.
This was not carried out by one person. Our initial investigation suggested that the security incident may have involved a compromised laptop, however our subsequent investigation has uncovered additional points of breach.
This was a complex attack. The attacker also used a self-destruct mechanism that destroyed tooling and traces as they went, making it more difficult for us to trace and investigate.
The attacker used a known multi-signature protocol EIP-7702, to obtain on-chain execution approval over a hot wallet. That delegation did not pass through our normal approval controls. That’s why we need to pause the withdrawal service to investigate, rebuild, and retest the entire infrastructure system.
So what are we doing now?
First, we are rebuilding the withdrawal service, and we are not switching it back on until it passes rigorous testing. We are very hopeful that users will be able to withdraw prior to our Sunday deadline, which is on track to be within 40 hours.
Second, we are conducting a full security review across the entire company — endpoints, cloud, key management, signing. Everything.
Third, we are completing the purchase of the remaining assets and will verify in our Proof of Reserves. We will be sharing a full Proof Of Reserves report by Monday, and we are hoping to give an initial view of Proof of Reserves before that.
Fourth, we are working with law enforcement, blockchain intelligence firms, token issuers and other exchanges to trace and recover stolen funds. We will do everything within our power to ensure that these bad actors will be held accountable.
Lastly, this is an industry-wide effort, and we are grateful to partners across the ecosystem who have moved quickly to help and support. We will weather this storm. Thank you for the support - and stay safe.
This is what commitment to users looks like💛
#Binance isn't just covering losses; it's going the extra mile to restore the exact assets affected
Actions like these build trust, strengthen confidence, and set a higher standard for the entire industry 🔶
Binance’s SAFU fund and Binance’s holdings include a large amount of assets such as BTC and ETH. We are currently buying, through OTC and on-exchange, all the stolen altcoins in fully matching amounts. We will update everyone again once the purchases are complete.
币安的SAFU基金和币安持有币种包括大量的BTC和ETH等资产,目前正在通过OTC和场内买入完全匹配被盗的所有山寨币来完成POR,购入完成后再次为大家同步信息。
This is how legacies are built 💛 #Binance may come out of this challenge with even greater respect, credibility, and trust than ever before True leadership is proven through actions, not promises 🔶
Thank you @EowynChen for the clear explanation and transparency 💛
Different systems, different risks. Pausing withdrawals while strengthening security is the right step. User protection always comes first!
We appreciate your efforts! 💛🔶
Seeing questions about why deposits are fine but withdrawals were paused. Fair question, so here's the actual difference:
1/ Deposits were never touched. The deposit path wasn't part of the incident. Also, users shouldn't have to worry about funding a position or getting liquidated.
2/ Withdrawals are the path that was affected. We paused them to stop any further loss while the security team can investigate and rebuild the infra before reopening it. We're not turning it back on until we know it's solid.
Two different systems, two different risks.
A special salute to @heyibinance for her incredible strength and dedication Working through an all-nighter while pregnant is truly admirable💛
And a huge thank you to every #Binancian who worked tirelessly through this challenging time
A huge thank you to the entire @binance team for your hard work, dedication, and commitment during this challenging time
We truly appreciate everything you're doing, and we have full confidence in you
Proud to stand with you! 💛
@binance @heyibinance @_RichardTeng @EowynChen 🫡
A crisis tests whether the strengths you claim are real.
I'm still in the middle of this, but I want to say it now rather than later: I'm proud to be working alongside this team. Accountable, fast, and they don't flinch. 💛
We'll earn back the trust. @binance @heyibinance @_RichardTeng
User protection comes first 💛
Binance is taking responsibility and committing to covering all losses through SAFU and company funds
Our priority now is strengthening security, working with global partners, and ensuring services resume safely
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.
Protecting users isn't just a promise
it's a responsibility backed by action
Covering the losses, prioritizing security before restoring services and cooperating with global law enforcement are important steps toward moving forward
User protection comes first
StrongerTogether💛








