Crypto trading bot platform 3Commas has finally admitted to a catastrophic security failure after weeks of vehement denials. In a public statement that sent shockwaves through the digital asset ecosystem, 3Commas CEO Yuriy Sorokin officially verified that a hacker had successfully leaked a database containing the platform’s API keys. The confirmation follows mounting pressure from high-profile industry leaders, major cryptocurrency exchanges, and affected users who have suffered substantial financial losses due to unauthorized trades executed on their accounts.
The acknowledgment marks a dramatic about-face for 3Commas, which had previously dismissed numerous reports of compromised data and accused affected users of falling victim to external phishing scams or fabricating evidence. Now, with the empirical proof of the breach brought to light, the platform is facing an intense backlash from a disgruntled crypto community demanding accountability and immediate financial restitution.
CEO Confirms Breach and Collaborates with Major Exchanges
The admission came to light on December 28 through a detailed Twitter thread published by Yuriy Sorokin. In his posts, the 3Commas chief executive conceded that the data published by the hacker online was entirely factual. The compromised information included API keys that allowed unauthorized third parties to interact with user accounts across several major cryptocurrency trading venues.
Upon realizing the undeniable validity of the leaked data, Sorokin stated that the platform immediately reached out to prominent exchanges—including Binance and KuCoin—to proactively revoke all API keys associated with 3Commas. This emergency measure was taken to sever any lingering back-door access the attacker might have utilized to drain funds from user portfolios.
The breach immediately triggered alarms across the wider cryptocurrency industry. Binance CEO Changpeng "CZ" Zhao took to social media to sound the alarm, advising all platform users to swiftly disable 3Commas’ access to their accounts. Zhao stated that he was "reasonably sure there are widespread API key leaks" originating from the automated trading service, urging traders to take defensive action immediately to protect their assets from ongoing exploitation.
Addressing the internal mechanics of the security lapse, Sorokin noted that 3Commas had thoroughly investigated whether the incident was an inside job orchestrated by rogue personnel. While the internal review failed to uncover definitive proof of malicious internal collusion, Sorokin acknowledged that a limited group of technical employees previously held administrative privileges allowing access to the core infrastructure. In response to the crisis, the company revoked these access privileges starting as early as November 19.
Sorokin issued a public apology for the firm’s handling of the crisis, noting that the company has since implemented stricter security protocols and enlisted the cooperation of law enforcement agencies to launch a comprehensive, formal investigation into the breach.

A History of Denials and Gaslighting Accusations
The official confirmation by 3Commas stands in stark contrast to the company’s previous public relations strategy. For weeks, as rumors and whistleblower reports began to mount regarding anomalous trades and drained balances, 3Commas vehemently denied that its systems had been breached. Even moments before Sorokin’s public confirmation, the official 3Commas corporate Twitter account continued to publish statements refuting claims that its database had been compromised.
This pattern of denial has become the central grievance for a growing coalition of victims and industry commentators. Critics argue that the platform’s stubborn refusal to investigate early warnings allowed the exploit to persist, compounding the financial damage inflicted on unsuspecting traders. Rather than transparently addressing potential vulnerabilities, the firm repeatedly pointed fingers at its customer base.
Community Outrage and Demands for Financial Restitution
In the wake of the CEO’s confession, the crypto community has mobilized, directing fierce criticism at 3Commas and demanding that the platform make whole those who lost funds through the compromised API keys. Social media platforms have become a focal point for disgruntled users venting their frustrations over how the situation was managed from the top down.
Prominent crypto trader and victim Coinmamba voiced extreme frustration on Twitter, pointing out that 3Commas spent weeks deflecting blame and gaslighting users instead of taking immediate responsibility and sealing the architectural vulnerabilities. Coinmamba publicly challenged the company’s leadership, asking whether 3Commas intends to issue financial refunds to the traders who lost capital due to the platform’s admitted security failures.
Another well-known community figure, Garlam, echoed these sentiments, accusing 3Commas of psychological manipulation. Garlam stated that the firm actively gaslighted the entire community into believing that individual users were entirely at fault for allegedly falling victim to external phishing campaigns or mismanagement of their own security credentials.
Additional community voices, including prominent analysts and commentators, heavily criticized the corporate communication strategy deployed during the height of the crisis. According to these critics, 3Commas could have successfully mitigated further unauthorized trading waves had management chosen to confirm the data leak weeks earlier. Instead, the company chose to label distressed victims as "bad faith actors" and publicly claimed that those reporting missing funds had "falsified evidence."
As law enforcement agencies step in to examine the breach and the stolen data circulating online, the pressure on 3Commas continues to escalate. With its reputation severely damaged and a trail of unauthorized trades left in the wake of the API leak, the platform now faces an uphill battle to rebuild trust with its user base—a battle that many traders argue must begin with financial compensation for the victims of the security lapse.

