The Bloom platform has experienced a security incident that resulted in the compromise of 49 addresses belonging to nine users. Total damages are estimated at approximately 9408 SOL, equivalent to $947,000 at current market rates.

As a result of an internal investigation, the team identified the attack vector: the breach occurred through a third-party module with a remote code execution (RCE) vulnerability. This class of vulnerability remains one of the most dangerous in the infrastructure of Web3 services, as it allows an attacker to execute arbitrary code on the server side without direct access to private keys.

The key finding of the investigation: users' private keys were not compromised, and the wallets of the platform's other clients were unaffected. This points to the targeted nature of the attack and a limited scope of damage — which significantly reduces reputational and systemic risks for Bloom as a whole.

The company has made a full commitment to reimburse the losses: funds will be transferred to secure addresses specified by the affected users. In parallel, the team is monitoring the movement of the stolen assets and taking steps to identify the attacker.

Market Context

The incident once again highlights a critical supply chain problem in the crypto industry: even with robust protection of the platform core, third-party integrations and modules become an entry point for attackers. For the Solana ecosystem, which is actively expanding its wallet and DeFi service infrastructure, the auditing of external dependencies is coming to the forefront.

Bloom's willingness to fully cover the losses at its own expense is a strong signal to the market, demonstrating maturity in its approach to incident management. However, the very fact that an RCE vulnerability was exploited through a third-party component underscores the need for stricter control over the entire chain of integrations.

Cryptalist Analysis: Full reimbursement of funds without key compromise limits the reputational damage for Bloom and preserves user trust. At the same time, the incident reinforces market demand for third-party module audits and isolated wallet architecture — a trend that will shape the security standards of Solana services in the coming quarters.