# Bitquery Puts 48-Wallet Solana Drain at $953,000; Bloom Reports 49 Addresses

Published 2026-10-27 · Crypto.world Team · Crypto.world

> Bitquery traced a 9,408-SOL drain across 48 Bloom-linked wallets in 94 seconds and valued the loss at about $953,000. Bloom’s public statement reported 49 affected wallet addresses and approximately $947,000, and the company said it would reimburse affected users.

A script drained 9,408 SOL from Bloom-linked wallets in a 94-second run early on October 26, according to Bitquery’s on-chain investigation. Bitquery valued the stolen SOL at about $953,000 and counted 48 drained wallets belonging to nine traders. Bloom’s public statement reported 49 affected wallet addresses and approximately $947,000, a separate count and valuation. Bloom pledged to repay affected users while investigating how the attacker gained access.

Source [news.hodlfm.io](https://news.hodlfm.io/solana/bloom-hack/)

## One test, then a 94-second sweep

The attacker began shortly before 1 a.m. UTC with two failed attempts against the largest wallet in the group. It then sent small test transfers from wallets linked to each of the nine traders before beginning the main sweep. Bitquery traced the transfers to a new collection address and found that the script took wallets in descending balance order, trader by trader.

The sequence offered clues to how the wallets were grouped. Bitquery compared the drain order with Bloom fee payments and where owners moved leftover funds afterward. It concluded that the 48 wallets belonged to nine traders; it described the grouping as firm for seven traders and less certain for two, where drain order was the main evidence. Bloom’s statement, by contrast, counted 49 affected wallet addresses. It also gave a different estimated loss: approximately $947,000, compared with Bitquery’s roughly $953,000 valuation for the 48 wallets in its on-chain analysis.

The largest single loss was 1,636 SOL, valued at roughly $166,000. Six wallets held 61% of the SOL taken, while the smallest total loss among the nine traders was 650 SOL. Bitquery valued SOL minute by minute during the attack, at about $101.30 per coin.

## The wallet key signed each transfer

Bitquery’s review of the transactions found that each drain was signed by the affected wallet’s own key, with no token approval or smart-contract interaction. That establishes how the transfers were authorized on-chain, but not how the attacker obtained the ability to initiate them. The investigation says the public ledger does not reveal who controlled the attacker’s wallets or how the relevant keys were accessed.

Bloom later attributed the incident to remote code execution through a third-party software module and said private keys were not accessed or compromised. That is the company’s account of the cause; Bitquery’s transaction analysis documents the on-chain signatures, not the software exploit. Bloom’s public update did not identify the module or provider.

The attack also reached wallets that had gone unused on Bloom for months. Five of the drained wallets had not traded through the bot since the first half of 2025, according to Bitquery. The finding shows that stopping use of a bot does not empty or replace a wallet whose key remains associated with its software.

## Bloom promises repayment as trading stops

Bloom said it would reimburse affected users by sending funds to new wallets chosen by their owners. In a reply to a user asking about a relief fund, Bloom wrote:

> “There won't be any need for a relief fund. Bloom will fully reimburse all funds lost by the 9 affected wallets, directly to new, secure wallets designated by their respective owners.”

The reply refers to “9 affected wallets,” while Bloom’s public incident statement reports 49 affected wallet addresses. Bloom also said it was investigating the incident and temporarily disabled services. Bitquery’s fee-wallet data showed Bloom trading activity falling away after the drain; the last fee payment it recorded came at 04:05 UTC on October 26. The reimbursement was a promise, not evidence that funds had already reached users.

By Bitquery’s last transaction check at 07:34 UTC on October 26, nearly all 9,408 SOL sat in a single holding wallet. The investigation found no exchange, bridge or mixer had touched either attacker wallet by that cutoff.

## Sources

1. Original source · Press release [HODL FM News](https://news.hodlfm.io/solana/bloom-hack/) news.hodlfm.io

Other pages read

2. [Bitquery](https://www.bitquery.io/investigations/bloom-trading-bot-hack) bitquery.io
3. [Bloom on X](https://x.com/BloomTrading/status/2114646392010359238) x.com

## Related stories

- [Zilliqa CEO Alexander Zahnd Steps Down as X-Bridge Stays Shut](https://crypto.world/news/zilliqa-ceo-zahnd-steps-down-x-bridge-suspended)
- [Kava plans vote to disable new lending on HARD Lend after exploit](https://crypto.world/news/kava-plans-hard-lend-retirement-after-drain)
- [Lighter says it recovered about $5 million after API-key attack](https://crypto.world/news/lighter-recovers-5-million-api-key-attack)
- [Shaw Rebuilds daos.fun’s Solana Program Byte for Byte, Reports a Critical Flaw](https://crypto.world/news/shaw-daos-fun-solana-program-critical-flaw)
- [Bitquery Measures Solana Blocks at 0.21 Seconds](https://crypto.world/news/bitquery-solana-block-time-021-seconds)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/bloom-users-lose-953000-solana-drain
