Binance refutes concerns about exchange code leaked on GitHub

According to 404 Media, the information had been in the publicly available GitHub repository for months

01.02.2024 - 09:12

755

2 min

What’s new? On January 31, journalists from 404 Media reported on the Binance crypto exchange code leak. According to them, “A highly sensitive cache of code, infrastructure diagrams, internal passwords, and other technical information” has been stored in a publicly accessible GitHub repository for months. Binance responded by saying that the information was outdated and its leak did not pose a significant risk.

Material by 404 Media

What else is known? The exchange’s statement contradicts the data given in the 404 Media report. Thus, journalists write that on January 24, Binance asked GitHub to remove the files, noting that they were published without permission, and their presence in the public domain poses a significant risk. GitHub granted the request.

404 Media found no evidence that the files were obtained or used by attackers, but “the cache contained a wealth of information that could be useful to hackers looking to compromise Binance’s systems,” the publication writes.

In turn, a Binance spokesperson said in a comment to Cointelegraph that the files posed little risk to the security of users, their assets, or the platform because they were so outdated that they could not be used by third parties or malicious hackers.

The security team confirmed that the cache did not “resemble what we currently have in production,” he concluded.

Binance позволила крупным трейдерам хранить средства за пределами биржи

Согласно данным FT, сотрудничать с биржей уже начали швейцарские Sygnum Bank и Flow Bank

However, Binance said it intends to protect its intellectual property and seeks to mitigate damage from“unnecessary confusion or unwarranted fears about the publication of private data,”

In addition to the already approved request to remove the information from GitHub, the exchange will file a lawsuit against the user who published it.

Author: