Spartan Protocol Hack

TOTAL LOST $30.5M
High #172 All-Time Flash Loan Attack binance

Summarize with AI

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

Incident Overview

Spartan Protocol was exploited due to a flawed liquidity share calculation in the protocol, allowing the attacker to drain funds from the pool.

The attacker initiated the exploit by taking a flash loan of 10K WBNB. They then repeatedly swapped WBNB for SPARTA, inflated the asset balance in the pool, and burned pool tokens to withdraw liquidity. This process was repeated multiple times, draining substantial funds from the pool. The attacker then returned the flash loan with a fee of 260 WBNB. The stolen funds were swapped to BTCB or BETH using 1inch and Spartan, and then to Anyswap versions using Nerve. The attacker was able to withdraw part of the profit through Anyswap.

Stolen funds:

- 2,643,882.074112804607308497 SPARTA

- 21,555.69728926154636986 WBNB

The attacker's address:

https://bscscan.com/address/0x3b6e7772…b83671

The transaction behind the attack:

https://bscscan.com/tx/0xb64ae25b…b93af8

Incident Report

Protocol / Project Spartan Protocol
Date of Incident
Affected Chain(s) binance
Attack Technique Flash Loan Attack
Classification Exchange (DEX)

Protocol Information

Protocol Type CDP
Affected Token SPARTA
Official Website spartanprotocol.org/
Protocol Twitter/X @SpartanProtocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Binance Chain BNB Chain 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 flash loan attack and Solidity and EVM internals
Capital Required Flash loan capital (borrowed atomically, zero upfront cost)
On-Chain Access Ability to interact with binance smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Spartan Protocol's contract logic - root cause: exchange (dex)
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
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 Flash Loan Attack vulnerabilities in code review
Audited by Audit Report 1 — still lost $30.5M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Spartan Protocol, these are the critical security checks that could have prevented this incident (May 2021).

  • Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans 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

Security Audit History

Related Attack Classes

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

See all Flash Loans Attacks examples →

Sources & References

Learn to Prevent the Next Spartan Protocol

The Spartan Protocol 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