El CEO de Binance dice que Exchange se recuperó $450 Million From the Curve Finance Ataque

Following the recent Curve Finance attack, Binance CEO Changpeng Zhao announced that the exchange had recovered $450 million from hackers. The decentralized finance (definitivamente) platform Curve saw roughly $570 million siphoned from the application on August 9.

Contenido

Binance Boss Says Exchange Froze 83% of the Curve Finance Hack Funds, Domain Provider Says Exploit Was DNS Cache Poisoning

Four days ago, the crypto community was made aware that the Curve Finance front end was exploited. Curve fixed the situation but $570 million was removed from the defi protocol. The attackers, sin embargo, decided to send the funds to crypto exchanges. Binance CEO Changpeng Zhao (CZ) tweeted about the exploit the day it happened.

“Curve Finance had their DNS hijacked in the past hour,” CZ escribió. “Hacker put a malicious contract on the home page. When the victim approved the contract, it would drain the wallet. Damage is around $570K so far. We are monitoring.” In addition to Binance monitoring the situation, the exchange Fixedfloat managed to freeze some funds.

“Our security department has frozen part of the funds in the amount of 112 [éter]. In order for our security department to be able to sort out what happened as soon as possible, please email us,” Fixedfloat escribió the day of the hack. Then three days after the hack, en Agosto 12, CZ explained at 1:07 soy. (EST) that Binance recovered roughly 83% of the funds.

“Binance froze/recovered $450K of the Curve stolen funds, representing 83%+ of the hack,” CZ tuiteó el viernes. “We are working with [law enforcement] to return the funds to the users. The hacker kept on sending the funds to Binance in different ways, thinking we can’t catch it,” CZ added.

Curve Finance retweeted CZ’s statement and noted earlier in the day that the team has a brief report from the domain provider [iwantmyname.com] and said: “In brief: DNS cache poisoning, not nameserver compromise,” Curve Finance explicado while sharing the report. “No one on the web is 100% safe from these attacks. What has happened STRONGLY suggests to start moving to ENS instead of DNS.”

The domain provider iwantmyname.com’s reporte confirms Curve’s statements. “It appears that one customer’s domain was targeted,” iwantmyname.com’s disclosure report details. “Our external provider’s hosted DNS infrastructure was apparently compromised and the DNS records for this domain were changed to point to a cloned web server. Further investigation together with the external provider indicates that it was DNS Cache poisoning rather than any nameservers compromised.”

Etiquetas en esta historia
$450 Millón, $570k, Binance, Binance CEO, Changpeng Zhao, Curva, Curve fi frontend, Curve.finance, CZ, DeFi, Explotación defi, DNS Cache poisoning, ETH, Etéreo, Etéreo (ETH), Fixedfloat, Funds, Hack, hacker’s funds, iwantmyname.com, USDC, USDC funds

What do you think about Binance recovering $450 million from the Curve Finance hack? Háganos saber lo que piensa sobre este tema en la sección de comentarios a continuación..

jamie redman

Jamie Redman es el líder de noticias en Bitcoin-Tidings.com News y un periodista de tecnología financiera que vive en Florida.. Redman ha sido un miembro activo de la comunidad de criptomonedas desde 2011. Él tiene una pasión por Bitcoin., código fuente abierto, y aplicaciones descentralizadas. Desde septiembre 2015, Redman ha escrito más de 5,700 artículos para Bitcoin-Tidings.com Noticias sobre los protocolos disruptivos que surgen hoy.




Créditos de imagen: Shutterstock, pixabay, Wiki Commons

Descargo de responsabilidad: Este artículo es solo para fines informativos.. No es una oferta directa o solicitud de una oferta para comprar o vender, o una recomendación o respaldo de cualquier producto, servicios, o empresas. Bitcoin-Tidings.com no proporciona inversión, impuesto, legal, o asesoramiento contable. Ni la empresa ni el autor son responsables, directa o indirectamente, por cualquier daño o pérdida causado o presuntamente causado por o en relación con el uso o la confianza en cualquier contenido, bienes o servicios mencionados en este artículo.

Leer Descargo de responsabilidad