Rain Hack

TOTAL LOST $14.8M
High Other bitcoin ethereum solana xrp

Summarize with AI

Affected Chain bitcoin 4 chains affected
Recovered - No recovery reported
All-Time Rank #265 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Rain exchange experienced an exploit resulting in the loss of ~$14m

On April 29, 2024, the crypto exchange Rain was likely exploited, resulting in the loss of $14.8 million. Suspicious outflows from Rain's BTC, ETH, SOL, and XRP wallets were quickly transferred to instant exchanges and swapped for BTC and ETH. The stolen funds currently consist of 137.9 BTC and 1881 ETH.

Incident Report

Protocol / Project Rain
Date of Incident
Affected Chain(s) bitcoin ethereum solana xrp
Attack Technique Other
Classification Infrastructure / CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type Prediction Market
Official Website rain.com/?ga_ad=tw
Protocol Twitter/X @rain
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Arbitrum Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of other and Rust/Anchor program internals and the Solana account model
Capital Required Seed capital to cover Solana network fees and initial position setup
On-Chain Access Ability to interact with bitcoin, ethereum, solana, xrp Solana programs and deploy a custom exploit program or signer account
Protocol Analysis Identification of the exploitable vulnerability in Rain's program logic - root cause: infrastructure / cefi
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single Solana transaction (atomic across instructions)
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Other audit checklist and test coverage
Audited by Audit Report 1 — still lost $14.8M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Rain, these are the critical security checks that could have prevented this incident (April 2024).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Sources & References

Learn to Prevent the Next Rain

The Rain hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial