Sperax USD Hack

TOTAL LOST $250K
Low Other

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1212 By amount stolen
Auditors 2 Prior security audits

Incident Overview

On Feb. 4, 2023 Sperax USD (USDs) token rebase mechanism was exploited, losing $250,000.

On February 4th, an attacker exploited the SperaxUSD protocol on Arbitrum, allowing them to increase their token balance to 9.7 billion tokens without providing matching collateral. The attacker was able to liquidate around $300k USDs before being stopped by joint actions of the Sperax team and Arbitrum ecosystem partners. The team identified the attacker's accounts on CEXs and took action against them.

All USDs transactions and the smart contract were blocked. The liquidated amount will be recapitalized by the Sperax team before relaunching the protocol. The governance token $SPA was not affected by the exploit, and USDs maintained its peg with slight fluctuations between 0.97 and 1.02 USDs/USD.

The issue has been resolved with a smart contract upgrade and recapitalization, with transactions set to restart soon.

Exploiter:

https://arbiscan.io/address/0x4AfcD19b…df1181

Incident Report

Protocol / Project Sperax USD
Date of Incident
Attack Technique Other
Classification Stablecoin

Protocol Information

Protocol Type Yield Aggregator
Affected Token USDs
Official Website sperax.io/
Protocol Twitter/X @SperaxUSD
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Stablecoin

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 Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Sperax USD's contract logic - root cause: stablecoin
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? Likely — with a thorough Other audit checklist and test coverage
Audited by Certik, SlowMist — still lost $250K. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Sperax USD, these are the critical security checks that could have prevented this incident (February 2023).

  • 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 Sperax USD

The Sperax USD 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