Binance asserted the data posed a “minor risk” to users, although a previous GitHub takedown request described it as a “significant risk” to the exchange.
Binance has challenged a report alleging the exposure of a “highly sensitive” internal cache on GitHub, arguing that the code was outdated and posed only a “negligible risk.” The report, dated January 31, claimed the cache included “code, infrastructure diagrams, internal passwords, and other technical information,” revealing details about password procedures and multifactor authentication methods. Binance reportedly requested a copyright takedown from GitHub on January 24, describing the exposed information as posing a “significant risk” and being posted “without authorization.”
Nevertheless, a spokesperson from Binance informed Cointelegraph that the person had “shared very outdated information on GitHub,” and their security team verified that the cache did not “resemble what we currently have in production.”
Binance asserted that the information “posed negligible risk to the security of our users, their assets, or our platform.” The exchange argued that the data was so outdated that it would be unusable by any third parties or malicious actors. Despite this, Binance emphasized the protection of its intellectual property and the prevention of unnecessary confusion or unwarranted fears about private data publication.
This led to the issuance of a takedown request with GitHub and the initiation of legal action against the user. However, Binance’s request to GitHub repeatedly stated that the information was “our client’s internal code, which poses a significant risk to Binance and causes severe financial harm to Binance and user’s confusion/harm.” Further questions on the matter from Binance remain unanswered.
