October 2026 was a rough month for crypto. Binance suffered the largest reported cryptocurrency theft in history, while CoinDCX, Polymarket, and Gamdom faced separate security breaches. Since then, investigators have identified how some of these attacks happened, and the affected platforms have started covering losses. But billions in stolen assets are still tied up in recovery efforts.
How Did the Binance Hack Happen?
On October 29, hackers stole approximately $6.34 billion in digital assets from Binance, affecting multiple blockchains, including Bitcoin, Ethereum, Solana, and XRP.
According to Binance's November 3 investigation, the attack started with a fake job interview in September.
Someone posing as a recruiter contacted a Binance software engineer and eventually convinced him to download a coding assignment containing malware.
The attackers later used the compromised computer and an internal AI tool to access other employees' systems. By October 29, they had obtained the credentials needed to interfere with Binance's wallet-signing service.
This allowed them to authorize transfers outside the exchange's normal withdrawal process.
They also exploited Ethereum's EIP-7702 authorization feature, giving a malicious smart contract permission to move funds from a Binance hot wallet.
Even after Binance suspended withdrawals, some transfers continued because those permissions were already active on the blockchain. Binance had to revoke them separately.
The FBI Points to North Korea
On October 31, the FBI attributed the theft to North Korea's TraderTraitor operation.
Investigators observed stolen assets being converted primarily into Ethereum's ETH token, with further transfers potentially involving decentralized finance services.
That doesn't necessarily mean the attackers successfully cashed out. Swapping stolen crypto into another cryptocurrency is different from withdrawing it into a bank account.
The FBI published associated wallet addresses and urged exchanges and other crypto services to block transactions involving the stolen assets.
What Happened at CoinDCX, Polymarket, and Gamdom?
Three other platforms suffered separate attacks during October.
| Platform | Reported loss | What happened |
|---|---|---|
| Gamdom | $3M+ reported; $4.2M estimated | Hot-wallet server breach. |
| CoinDCX | 15.99M USDT | Old deposit wallets compromised. |
| Polymarket | About $2.7M | Malicious third-party website script. |
CoinDCX: Old Wallets Exposed New Deposits
CoinDCX's incident involved infrastructure compromised back in July 2025.
Although the exchange had retired the affected addresses, some customers continued depositing funds into them.
Normally, CoinDCX credited those deposits to customer accounts and automatically moved the underlying crypto into secure wallets.
In October, that transfer system failed, leaving accumulated deposits exposed.
According to CoinDCX's October 25 statement, the company absorbed the loss. Active trading and wallet services remained operational.
Polymarket: A Compromised Website Script
On October 29, attackers replaced a third-party monitoring script loaded by Polymarket's website with malicious code.
For some users who had the website open during the attack, the script exploited their active sessions to sell trading positions and transfer funds.
Polymarket removed the compromised script, temporarily suspended trading, and reset active sessions.
The company later confirmed the incident in its official security report.
The attack showed that even a legitimate website can expose users when software supplied by an outside company becomes compromised.
Gamdom: The Final Loss Remains Unclear
Gamdom took its platform offline on October 13 after discovering unauthorized access to an automation server connected to its hot-wallet system.
The company moved remaining funds into cold storage and reopened on October 16.
Founder Felix Römer reported a lower loss than independent blockchain investigator vxdb, whose estimate was based on on-chain transactions.
The difference between those figures has not been publicly reconciled. Nexus Mutual's October security report documented both estimates.
Who Covered the Losses, and What's Still Missing?
Binance reported approximately $2.85 billion frozen or intercepted with help from blockchain partners and asset issuers.
However, frozen funds are not necessarily recovered funds. They may remain in attacker-controlled wallets while access to them is blocked.
Binance said it had committed enough of its own resources to cover the entire loss. By October 31, it had replenished 98% of the affected token assets, with the remaining purchases taking longer because some tokens had limited liquidity.
On November 4, the exchange published an expanded Proof of Reserves snapshot covering 44 tokens.
Withdrawals also began reopening in phases. Its November 5 recovery update listed additional assets and networks returning to service.
Polymarket reported $3.9 million in total compensation, including stolen funds and payments for certain trading losses caused by the incident.
By October 30, the company said 95% of affected wallets had received full refunds. Eligible customers were identified automatically, with a review process available for disputed amounts.
CoinDCX said customer balances remained unaffected because it had already credited the deposits before the underlying funds were stolen.
Gamdom also stated that customer balances were protected, although a confirmed final recovery figure was not available in the reporting reviewed.
The remaining challenge is recovering the stolen assets themselves.
Binance's investigation is still undergoing independent review, and blockchain investigators continue tracking the movement of stolen funds.
For customers, the distinction is important. A company can restore account balances using its own money long before investigators recover the original crypto.
And for anyone still waiting to withdraw their funds, a recovered wallet balance means little until that money is actually accessible.