Security

TeleSwap's Silent Hack: When a Bitcoin Bridge Loses $735K and Says Nothing

2026-07-25

On Monday, blockchain investigator ZachXBT revealed that TeleSwap, a self-styled "Bitcoin DeFi hub," had been exploited on July 15. By the time the news came out, nobody at TeleSwap had bothered to tell anyone what happened.

ZachXBT tracked suspicious outflows of over $735,000 and found that TeleSwap's Bitcoin hot wallet stopped processing transactions shortly afterward. The timing gets worse. At the time of writing, TeleSwap had still not disclosed the loss on its official X account. Five days of silence after a six-figure bridge hack is either contempt for users or contempt for basic security protocol—probably both.

The attacker moved fast. Attackers exploited TeleSwap on July 15, draining approximately $735,000 before laundering the stolen funds through Tornado Cash, a cryptocurrency mixing service frequently used to obscure transaction histories. That's the playbook: drain, burn the trail, vanish.

The broader picture is grim but not surprising. The projects Allswap, Across Protocol, and TeleSwap lost $1.65 million, $3.35 million and $735,000, respectively in a single week of bridge hacks. This isn't a freak incident. The recurring thread across many of these incidents is not a clever protocol exploit but the compromise of hot wallets and executor keys, the always-online infrastructure that projects use to move funds and validate cross-chain transfers. Hot wallets are low-hanging fruit because they have to stay online to function.

Cross-chain bridges have repeatedly emerged as one of the most attractive targets for hackers. These platforms enable users to transfer assets between different blockchain networks by locking tokens on one chain while issuing equivalent assets on another. Lock up value somewhere and announce it to the world, and someone will figure out how to take it. The only surprise is how often these platforms act shocked when it happens.

What makes TeleSwap's silence notable is that it breaks the bare minimum of incident response etiquette. When you get hacked, you announce it fast, you explain what happened, and you outline what's next. You don't pretend it didn't occur while a blockchain investigator does your job for you. On-chain trackers have described the recent stretch as one of the most hack-intensive in crypto's history, with the industry's 2026 losses already well past $750 million by mid-year. At that rate, silence from a protocol that just lost three-quarters of a million dollars looks less like operational caution and more like operational failure.

Source & further reading:

Sources