In a swift early-morning incident on October 26, 2026, an attacker emptied 48 Solana wallets linked to the Bloom Telegram trading bot, removing 9,408 SOL valued at roughly $953,000 in just 94 seconds.
Blockchain analysis firm Bitquery traced the activity, which affected wallets belonging to only nine traders.
The operation began shortly before 1 a.m. UTC with failed attempts and small test transfers from one wallet per trader to a fresh collecting address.
It then systematically drained each trader’s wallets, starting with the largest balances, completing the bulk of the transfers in under a minute after the initial tests.
Every transfer was a straightforward SOL movement signed by the wallet’s own private key, with no token approvals, smart contracts, or additional signers involved.
The script used identical network fees and left minimal residual SOL in each account.
Notably, the attacker focused exclusively on SOL, leaving approximately $57,000 in USDC untouched—though an attempt to claim a large USDC balance from one wallet was thwarted when the owner moved the funds first.
Nearly all the stolen SOL remained in a single attacker-controlled holding wallet for hours before a secondary transfer, with no further movement observed at the time of reporting.
Half of the affected wallets had not traded via Bloom in the prior month, and five had been inactive since the first half of 2025, indicating the compromised keys persisted long after use ceased.
Bloom, which generates and holds private keys for user wallets to enable rapid automated trading inside Telegram, responded by confirming full reimbursement of the losses directly to new wallets designated by the nine affected users.
The company attributed the breach to a complex remote code execution vulnerability in a third-party software module, stating that no private keys were accessed or compromised and that broader user exposure had been ruled out.
As a precaution, Bloom took all systems offline, requiring users to re-authenticate upon restoration.
Trading fee activity on the platform dropped sharply after the incident.
Such events highlight ongoing risks with custodial trading bots that store keys server-side for convenience, a model that has previously led to losses in other Telegram bots through key leaks or contract exploits.
Separately, Telegram has addressed a serious flaw in its Android application that could have allowed attackers to execute code on a user’s device simply by having a voice call answered.
Security researchers at NebuSec disclosed the issue on October 29, 2026, noting it affected Telegram for Android versions from 8.6.2 (March 2022) through 12.10.3 (September 2026).
The vulnerability stemmed from improper handling of MediaState signaling messages during calls, which could lead to incorrect memory access.
While the bug alone was insufficient for full device control and required chaining with additional exploits, NebuSec demonstrated its potential in testing on ARM64 Android devices.
Telegram patched the issue in version 12.10.4, released in late September 2026, and no real-world attacks have been confirmed.
Users are advised to update immediately, as the version appears at the bottom of the app’s Settings page.
Parallel fixes appeared earlier in shared call libraries for other platforms, though exploitability there remains unverified. These incidents underscore the persistent security challenges facing both crypto trading tools and popular messaging apps.
