Save Hack

TOTAL LOST $1.3M
Medium Price Oracle Attack solana

Summarize with AI

Affected Chain solana Incident surface
Recovered - No recovery reported
All-Time Rank #786 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Save (formerly Solend) is an algorithmic, decentralized protocol for lending and borrowing on Solana. Lending and borrowing has proven itself as being key in a DeFi ecosystem. However, current products are slow and expensive.

On Solana, Solend can scale to being 100x faster and 100x cheaper. Solend aims to be the easiest to use and most secure solution on Solana.

Incident Report

Protocol / Project Save
Date of Incident
Affected Chain(s) solana
Attack Technique Price Oracle Attack
Classification Ecosystem
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Smart Contract Language Rust
Official Website www.save.finance/
Protocol Twitter/X @save_finance

Market Context at Time of Hack

Token Categories
Solana 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 price oracle attack 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 solana Solana programs and deploy a custom exploit program or signer account
Protocol Analysis Identification of the exploitable vulnerability in Save's program logic - root cause: ecosystem
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? Yes — skilled auditors routinely flag Price Oracle Attack vulnerabilities in code review
Audited by Audit Report 1 — still lost $1.3M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Price Oracle Attack are guarded by proper access controls and input validation - see the Oracle Manipulation & Price Manipulation attack class for patterns
  • Audit oracle price feeds for manipulation risks - ensure time-weighted average prices (TWAPs) or multi-source aggregators are used, not spot prices
  • 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

Related Attack Classes

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

See all Oracle Manipulation & Price Manipulation examples →

Sources & References

Learn to Prevent the Next Save

The Save 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