Binance claims that the GitHub code breach is “outdated” and presents just a small threat
A previous GitHub request to remove the content indicated that the material posed a “significant risk” to Binance, despite the exchange’s claims that the information posed a “negligible risk” to users.
The cryptocurrency exchange Binance has denied a story that said a “very sensitive” cache of internal codes and passwords had been leaked on GitHub for months. Binance said that the code was old and didn’t pose any danger.
A cache of “code, infrastructure diagrams, internal passwords, and other technical information” was discovered, according to a Jan. 31 report from 404 Media. This cache included details on the exchange’s password and multifactor authentication processes.
According to the article, Binance was able to get GitHub to remove the files by submitting a copyright takedown notice on January 24. In the request, the exchange said that the data “poses [a] significant risk” and was uploaded “without authorization.”
But according to Binance’s official statement to Cointelegraph, the person in question “shared very outdated information on GitHub,” and the security team at Binance verified that the cache in question did not “resemble what we currently have in production.”
“Information posed negligible risk to the security of our users, their assets, or our platform,” Binance noted. It said that the data was so old that “any third parties or malicious actors” couldn’t use it.
The cryptocurrency exchange Binance has taken legal action against the user and has requested that GitHub remove the user’s content from their platform. The company claims it is doing this to prevent “unnecessary confusion or unwarranted fears about the publication of private data” and to keep its intellectual property safe.
Nevertheless, Binance asserts that the material in question is “our client’s internal code,” stating that it presents a substantial danger to Binance and results in serious financial loss for both the company and its users.
Wallets