Solareum Hack

TOTAL LOST $1.4M
Medium Private Key Compromised (Social Engineering) solana

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain solana Incident surface
Recovered - No recovery reported
All-Time Rank #750 By amount stolen
Protocol Type Dexs Target category

Incident Overview

Solarbeam is a decentralized exchange, providing liquidity and enabling peer-to-peer transactions on the Moonriver Network.

This is classified as a Phishing Attacks . Compare similar hacks →

Incident Report

Protocol / Project Solareum
Date of Incident
Affected Chain(s) solana
Attack Technique Private Key Compromised (Social Engineering)
Classification Infrastructure

Protocol Information

Protocol Type Dexs
Smart Contract Language Move
Official Website app.solarbeam.io/exchange/swap
Protocol Twitter/X @Solarbeamio

Market Context at Time of Hack

Token Categories
Solana Ecosystem
Protocol Links
GitHub

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover Solana network fees while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised stake accounts and treasury wallets, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Solareum's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

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

  • Verify all logic paths related to Private Key Compromised (Social Engineering) are guarded by proper access controls and input validation - see the Phishing Attacks attack class for patterns
  • 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

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Phishing Attacks examples →

Phishing Attacks
Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

Ronin Bridge $624M
Private Key Compromised (Social Engineering)

Learn to Prevent the Next Solareum

The Solareum 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial