Binance Co-CEO Takes Responsibility for $6.3B Hack, Details Security Overhaul

Binance Co-CEO Takes Responsibility for $6.3B Hack, Details Security Overhaul


Key Highlights

Binance co-CEO Richard Teng has accepted responsibility for the October 29 security breach, which involved approximately $6.3 billion in cryptocurrency assets.

In a November 3 interview with CNBC’s Squawk on the Street, Teng described how attackers allegedly used fake developer tools, fraudulent recruitment interviews and malware to penetrate the exchange’s internal systems. He also outlined the security measures Binance has introduced, along with its plans for an independent review.

He said Binance had closed the entry points used in the attack and rebuilt affected systems, while acknowledging that the breach should not have happened.

“This shouldn’t have happened. We take full responsibility on that front,” Teng said.

During the interview, CNBC asked Teng about reports that attackers had used an internal AI tool to gain control over additional engineers and whether Binance had restricted access to the system.

Teng described a campaign that allegedly began in June. According to his account, attackers first created a fake version of a developer tool and persuaded a Binance engineer to install it.

In September, they allegedly posed as recruiters and conducted job interviews with another engineer. The process included a coding exercise containing hidden malware designed to evade security tools.

Teng said the attackers subsequently moved through internal systems and AI tools before reaching the infrastructure responsible for authorizing wallet transactions.

He disputed the suggestion that the breach resulted from a single compromised laptop or one employee mistake.

“So this is not one single mistake or one one click,” he said, describing the operation as a coordinated campaign that developed over several months.

Teng said Binance’s initial response was to close the entry points exploited by the attackers and rebuild the affected infrastructure.

He told CNBC that the exchange had rebuilt the affected wallet infrastructure from the ground up in a separate environment. It had also rebuilt the internal tool involved in the attack with tighter controls.

According to Teng, Binance has also:

  • Replaced devices identified as affected.
  • Revoked credentials linked to the incident.
  • Scanned employee devices across the company.
  • Updated its monitoring systems.
  • Added controls for detecting unusual activity.

He said Binance would continue reviewing and updating its security measures following the incident.

The exchange has not published a complete technical account of how attackers obtained access to the internal AI tool or how they used it to reach the wallet authorization system.

Teng says AI can help detect security threats

CNBC also questioned Teng about the risks of using AI agents to manage money, given that attackers had exploited internal AI tools during the breach.

The question followed Teng’s public comments about AI agents and their potential to conduct financial activity around the clock.

Teng acknowledged that AI had changed the security environment but said the technology could also improve threat detection.

He said AI tools could help Binance identify anomalies, flag suspicious activity and respond more quickly to potential threats.

The exchange has not disclosed which specific AI systems it plans to use for security or how their effectiveness will be assessed.

Independent expert to review Binance’s security response

In a separate CNBC interview segment, Teng said Binance would commission an independent expert to review the company’s security measures and response to the breach.

“We are also getting an independent expert to review everything that we have done, and we’ll keep strengthening our defenses,” he said.

Teng did not identify the independent reviewer, specify a timeline for the assessment, or confirm whether its findings would be made public.

FBI attributes attack to North Korea

Teng said the FBI had attributed the attack to North Korea.

The FBI issued its own statement on October 31, saying North Korea was responsible for the theft of more than $6 billion from Binance. The bureau referred to the activity as TraderTraitor.

Blockchain intelligence firms also examined the incident. TRM Labs attributed the attack to TraderTraitor with high confidence, while Chainalysis said the breach was likely carried out by the same North Korean-linked group.

While the FBI identified the North Korean-linked group responsible for the attack, its statement did not substantiate separate viral claims alleging that a Binance employee had been involved in a romantic relationship with a suspected operative.

Binance co-CEO Yi He rejected that allegation on November 1, saying blockchain investigator ZachXBT had not made the claim attributed to him.

ZachXBT’s actual findings focused on the movement of funds linked to the Binance incident and a separate Bitget exploit. His post did not mention a romantic relationship or an unattended laptop.

Binance’s recovery efforts after the breach

In an October 30 video update, Teng said Binance had reserved more than $6.34 billion in company funds to cover the affected assets. Around $5 billion was already held in the same tokens involved in the incident, including Bitcoin, Ether, USDT, USDC and BNB. The exchange planned to acquire the remaining assets through open-market and over-the-counter purchases.

Binance also said industry partners had frozen approximately $3 billion in assets linked to the breach. This figure is separate from the funds the exchange allocated to replenish affected assets.

Tether reported freezing more than $1.567 billion in USDT, while Circle confirmed a freeze of more than $800 million in USDC in coordination with law enforcement. Other reported restrictions involved additional stablecoins and an Arbitrum Security Council intervention that locked approximately $30.5 million in ARB and ETH.

The incident also extended into DeFi markets. The Crypto Times reported that a wallet associated with the attack supplied approximately $60 million in USDT to Aave V3 Ethereum Core and borrowed 19,762 WETH, worth about $44.6 million at the time. Aave subsequently restricted its markets as part of its response.

These figures describe different actions and should not be combined into a single recovery total. Frozen assets are not necessarily funds returned to Binance.

Binance resumes withdrawals after replenishing assets

In its October 31 update, Binance said it had replenished approximately 90% of the affected amount and was targeting November 1 to resume withdrawals. It also reported that ten major assets, including BTC, ETH and USDT, had reached full backing.

The exchange said the remaining replenishment involved less-liquid tokens that it was still acquiring through market and over-the-counter channels. Binance also planned to restore its Secure Asset Fund for Users (SAFU) to approximately $1 billion after using part of the reserve to support replenishment.

A November 2 report by The Crypto Times said Binance had resumed withdrawals and reported that approximately 95% of the affected assets were covered.

These figures describe the exchange’s efforts to replace affected assets; they do not mean that the attacker returned the stolen funds.

Teng’s latest comments focus on Binance’s security changes, particularly its controls around internal tools and AI systems. The independent review remains pending, with its reviewer, scope, findings and publication timeline yet to be disclosed.

Also Read: Coinbase Policy Chief Says Bipartisan Crypto Push Gains Election Momentum


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *