FBI Is Reportedly Investigating 3Commas' API Leak

Friday, 30/12/2022 | 06:12 GMT by Arnab Shome
  • 3Commas' CEO recently admitted to the leaked APIs.
  • Earlier, he denied such leaks and called some circulated leaked API databases fake.
fbi, 3commas
(Photo: Bloomberg)

The United States Federal Investigation Bureau (FBI) is probing the data breach at Estonia-based 3Commas that exposed thousands of linked API keys, Coindesk reported on Friday, though there is no official confirmation yet.

FBI Shines Light on 3Commas API Leak

The investigation began after the confirmation of 3Commas' CEO, Yuriy Sorokin on the authenticity of the publicly shared database of 3Commas APIs. Earlier, he was in denial of any such breach and even called the previously leaked API databases fake.

The concerns around the security measures of 3Commas began in late October when then-functional crypto exchange FTX issued a security alert in response to an unauthorized trade from a customer account. Though FTX and 3Commas concluded that the hackers created a 3Commas account to execute the malicious trade, the Estonian company said, "the API keys were not taken from 3Commas but from outside of the 3Commas platform."

In a consecutive blog post, Sorokin acknowledged that 3Commas had "hard evidence that phishing was at least in some part a contributory factor" leading to users' losses.

According to the crypto-focused publication, a 60-member 3Commas victim group earlier approached the US Secret Service and other law enforcement agencies with complaints of their missing cryptocurrencies .

An official 3Commas ad.

The Publicly Leaked 3Commas APIs

The latest controversy around 3Commas started when an anonymous Twitter user recently shared a database of the leaked 3Commas API on social media. It included 100,000 Binance and KuCoin API keys linked to 3Commas. Earlier, 3Commas said that the APIs were leaked due to phishing, and the platform's security was intact.

Now many have pointed out the internal involvement in these API breaches. However, Sorokin squashed these claims on Thursday, saying: "3Commas stresses that it has found no evidence during the internal investigation that any employee of 3Commas was somehow involved in attacks against the API data."

"Since becoming aware of the suspicious activities taking place, we immediately launched an internal investigation. We will continue with the investigation in the light of the new information and also notify law enforcement authorities accordingly."

On top of that, the latest API leak on the public platform alarmed other crypto giants, as Binance's CEO Changpeng Zhao issued a public warning, asking users to disable their 3Commas API.

Earlier this month, Binance canceled a user's account who complained of losing funds due to an API breach. However, Binance declined to reimburse the user, saying that the exchange could not confirm the losses.

The United States Federal Investigation Bureau (FBI) is probing the data breach at Estonia-based 3Commas that exposed thousands of linked API keys, Coindesk reported on Friday, though there is no official confirmation yet.

FBI Shines Light on 3Commas API Leak

The investigation began after the confirmation of 3Commas' CEO, Yuriy Sorokin on the authenticity of the publicly shared database of 3Commas APIs. Earlier, he was in denial of any such breach and even called the previously leaked API databases fake.

The concerns around the security measures of 3Commas began in late October when then-functional crypto exchange FTX issued a security alert in response to an unauthorized trade from a customer account. Though FTX and 3Commas concluded that the hackers created a 3Commas account to execute the malicious trade, the Estonian company said, "the API keys were not taken from 3Commas but from outside of the 3Commas platform."

In a consecutive blog post, Sorokin acknowledged that 3Commas had "hard evidence that phishing was at least in some part a contributory factor" leading to users' losses.

According to the crypto-focused publication, a 60-member 3Commas victim group earlier approached the US Secret Service and other law enforcement agencies with complaints of their missing cryptocurrencies .

An official 3Commas ad.

The Publicly Leaked 3Commas APIs

The latest controversy around 3Commas started when an anonymous Twitter user recently shared a database of the leaked 3Commas API on social media. It included 100,000 Binance and KuCoin API keys linked to 3Commas. Earlier, 3Commas said that the APIs were leaked due to phishing, and the platform's security was intact.

Now many have pointed out the internal involvement in these API breaches. However, Sorokin squashed these claims on Thursday, saying: "3Commas stresses that it has found no evidence during the internal investigation that any employee of 3Commas was somehow involved in attacks against the API data."

"Since becoming aware of the suspicious activities taking place, we immediately launched an internal investigation. We will continue with the investigation in the light of the new information and also notify law enforcement authorities accordingly."

On top of that, the latest API leak on the public platform alarmed other crypto giants, as Binance's CEO Changpeng Zhao issued a public warning, asking users to disable their 3Commas API.

Earlier this month, Binance canceled a user's account who complained of losing funds due to an API breach. However, Binance declined to reimburse the user, saying that the exchange could not confirm the losses.

About the Author: Arnab Shome
Arnab Shome
  • 6654 Articles
  • 102 Followers
About the Author: Arnab Shome
Arnab is an electronics engineer-turned-financial editor. He entered the industry covering the cryptocurrency market for Finance Magnates and later expanded his reach to forex as well. He is passionate about the changing regulatory landscape on financial markets and keenly follows the disruptions in the industry with new-age technologies.
  • 6654 Articles
  • 102 Followers

More from the Author

CryptoCurrency

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|} !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}