Bloom pledges refunds after $953,000 crypto wallet drain
Nine traders lost about $953,000 across 48 wallets linked to the Bloom trading bot, according to reported findings, as the platform promised reimbursement and disputed that private keys had been compromised.
Bloom has pledged to reimburse nine traders after approximately $953,000 was drained from 48 wallets associated with its cryptocurrency trading bot, according to Cointelegraph’s supplied report. The platform said no private keys were accessed or compromised, but separate blockchain analysis raises questions about how the transfers were authorized.
Blockchain data provider Bitquery traced about 9,408 SOL taken from wallets used with Bloom, a trading service accessed through Telegram. Its investigation said the main drain unfolded in 94 seconds, underscoring how quickly an automated operation can move funds across multiple accounts before their owners can respond.
According to Bitquery, the operation tested wallets before draining balances in groups associated with individual traders, generally targeting larger balances first. The researcher linked the 48 wallets to nine traders using transaction patterns, trading-fee activity and subsequent movements of remaining funds, rather than treating each address as a separate victim.
The wallet total is not consistent across published accounts. The Crypto Times reported that Bloom identified 49 affected addresses belonging to nine users, while Bitquery traced losses from 48 wallets. Those counts should not be treated as interchangeable, although both accounts describe losses concentrated among a small number of traders operating multiple wallets.
The central unresolved issue is the method of access. While the supplied Cointelegraph report attributes a denial of private-key compromise to Bloom, Bitquery said the drain transactions were signed by the wallets’ own keys, without a separate contract or additional signer. That analysis challenges the platform’s account but does not establish where or how access was obtained.
Bitquery said possible explanations included exposure through infrastructure holding wallet keys or compromise affecting the traders themselves. It did not confirm either explanation, and transaction records alone cannot identify the attacker or conclusively establish the original point of failure. Bloom’s denial therefore remains a company statement, not an independently established technical finding.
Bloom paused certain services as a precaution and directed affected users to open support tickets through Discord, The Crypto Times reported. The publication also said the company recommended moving remaining assets to newly generated wallets and was examining possible third-party involvement as part of its investigation.
The incident highlights the security questions surrounding services that automate wallet transactions. Their ability to execute trades quickly makes the systems authorizing those transactions particularly important. In this case, the distinction between a compromised key, compromised infrastructure and another route to transaction authorization will matter to any credible explanation of the losses.
Bloom’s reimbursement commitment would address the traders’ financial losses, but it would not by itself resolve the security questions. According to The Crypto Times, the platform had not disclosed a repayment timetable or a schedule for restoring paused services. The next substantive developments will be confirmation of repayments and a technical account reconciling the competing explanations.
Primary source: CoinTelegraph. Newzly rewrites and structures source reporting for clarity; verify critical details at the original.