We checked this claim: is it true that

Bloom Trading experienced a system breach that resulted in 9,408 Solana tokens being taken from client accounts?

Confirmed

Bloom Trading confirmed that an outside software flaw let intruders take 9,408 Solana tokens across 49 accounts and promised to repay the victims

Crypto
  • ClaraAuthorComing December 1
  • JolinaMarketingComing December 1

Bloom Trading loses $947,000 to software breach

Automated trading service Bloom Trading said an outside software flaw exposed client wallets and drained 9,408 Solana tokens.

Published
Quantum Otter — crypto markets and AI trading bots

In a nutshell

Bloom Trading confirmed that an outside software vulnerability allowed attackers to drain 9,408 Solana tokens worth about $947,000 from 49 client accounts, prompting the platform to isolate its services and pledge full financial restitution to the nine affected traders while leaving key transaction records undisclosed.

Highlights

  • Intruders stole 9,408 Solana tokens worth roughly $947,000 from Bloom Trading clients.
  • The exploit hit 49 digital trading accounts owned by nine individual platform users.
  • Operators attributed the unauthorized withdrawals to a remote command flaw in a third-party software component.
  • Platform managers quarantined internal systems to halt further unauthorized token transfers.
  • Bloom Trading committed to reimbursing the nine affected account holders in full.

From the Editor’s Diary

Automated financial platforms remain only as resilient as their least-vetted third-party components, turning shared software dependencies into immediate single points of failure.

Who's involved

  • Bloom Trading

    Automated trading service that buys and sells digital assets on the Solana network

    goal → Quarantine the vulnerability, stop further token withdrawals, and retain client confidence

  • Unidentified Attackers

    Outside perpetrators who ran illicit commands through the third-party defect

    goal → Funnel stolen cryptocurrency tokens into external digital accounts

  • Affected Traders

    Nine customers whose connected digital wallets were targeted in the attack

    goal → Recover lost cryptocurrency assets and obtain complete promised compensation

In short

Automated cryptocurrency services face fresh counterparty scrutiny after an outside software module exposed client deposits to theft, putting user funds directly at the mercy of untested vendor code. The incident makes comprehensive restitution payments and stricter code reviews the most pressing test for automated decentralized finance platforms seeking to retain client trust. Full recovery remains uncertain because operators have yet to release public transaction records or trace the stolen funds to specific destination wallets.

Bloom Trading, an automated service that executes cryptocurrency trades on the Solana high-speed network, confirmed an intruder exploited a remote code execution flaw—a critical software defect allowing outsiders to run unauthorised commands from afar—embedded inside a third-party software component. The breach enabled attackers to drain 9,408 Solana tokens, worth roughly $947,000, across 49 trading wallets belonging to nine customers. Platform managers moved quickly to quarantine internal systems, halting any broader infection, and pledged full financial compensation to the affected account holders.

How it unfolded

01

Bloom Trading Discloses Account Drain

2026-10-26 – 2026-10-26

The incident became public when Bloom Trading released an incident summary acknowledging that unauthorised withdrawals had emptied client accounts through an underlying software flaw.

1 source
02

Containment and Client Restitution

2026-10-26 – 2026-10-27

Following its initial disclosure, Bloom Trading moved to define the boundaries of the intrusion, isolating internal infrastructure while pledging to keep affected customers whole as technicians review the compromised software component.

1 source

Where things stand

Bloom Trading has verified the loss of 9,408 Solana tokens belonging to nine customers and attributed the intrusion to an outside code execution defect.

Key details remain unresolved, including the release of verifiable on-chain tracking codes, the identification of receiving addresses used by the thieves, and independent confirmation that reimbursement transfers have reached all targeted clients.

Sources