keamanancrypto

The exchange called it a “false alarm” — three days later, it admitted it had lost $16 million.

The facts: CoinDCX, India’s largest crypto exchange, confirmed on Oct. 25–26 (CoinDesk, TokenPost) that 15.99 million USDT had been lost from a retired wallet. An automated sweeping system that was supposed to move customer deposits failed, leaving funds to pile up in an old address that had been breached in July 2025 — where an attacker took them. CEO Sumit Gupta had called the initial reports a “false alarm” on Oct. 22. CoinDCX says it will fully cover the loss and that customer funds remain safe in separate cold wallets.

My take: The worrying part isn’t the amount — $16 million is relatively small for an exchange of that size — but the pattern: a retired wallet still receiving deposits, followed by an initial denial that turned out to be wrong. This is about the discipline of decommissioning old infrastructure, not the security of active wallets. And it’s the second incident after the $44 million hack in July 2025.

What I’m watching: whether there’s an independent audit of this incident, and whether Tether managed to freeze more than the $2.2 million it has reportedly already frozen.

How much do you trust an exchange’s “funds are safe” statement after its initial denial turns out to be wrong?

This is my analysis, not financial advice — always DYOR.

#KeamananCrypto #BursaCrypto $USDT

Malicious servers can steal BTC via the fee-bump button — and there are already victims.

Fact: CoinDesk (Oct 26) reported that Electrum released 4.8.3 on Oct 24 to close this loophole: a malicious server replaces a user’s transaction with a fake one, then when the user bumps the fee via Replace-by-Fee, they end up signing the fake transaction instead. There were 2 reports in October: one user realized it before losing funds, and one lost money. All versions before 4.8.3 are vulnerable.

My opinion: This isn’t about Bitcoin being weak, but about verification. Attackers use addresses with the same last 4 characters as the original target, so check the full address — and don’t rush to bump the fee if your transaction seems stuck for no clear reason.

What I’m watching: Additional victim reports after the patch and whether that malicious server is still actively attacking users on older versions.

Have you updated to 4.8.3, or are you still using an older version?

This is my analysis, not financial advice — always DYOR.

#Bitcoin #KeamananCrypto $BTC