Abracadabra Spell Hack

TOTAL LOST $13.0M
High Other arbitrum

Summarize with AI

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

Incident Overview

On March 25, 2025, Abracadabra.Money was exploited for $13 million (6,260 ETH) due to state tracking errors in GMX-linked cauldrons, allowing the attacker to self-liquidate positions and take bad loans without repaying them. The stolen funds were bridged from Arbitrum to Ethereum and laundered via Tornado Cash.

The attack abused GMX-based cauldrons, which track collateral states for loans. The attacker failed a GMX deposit, leaving funds stuck in the OrderAgent contract, then self-liquidated a borrowed position, causing the system to erase it without removing collateral. This allowed them to borrow again using already liquidated collateral, effectively draining $13 million from the protocol.

The funds were bridged from Arbitrum to Ethereum and washed through Tornado Cash. Despite initial confusion, GMX contracts were not directly affected, and Abracadabra has offered a 20% bounty for fund recovery.

Exploit tx:

https://arbiscan.io/tx/0xed17089a…5ef0b0

Exploiter:

https://arbiscan.io/address/0xaf9e33aa…c38649

Incident Report

Protocol / Project Abracadabra Spell
Date of Incident
Affected Chain(s) arbitrum
Attack Technique Other
Classification Protocol Logic / Exchange (DEX),Yield Aggregator
Primary Source View Post-Mortem

Protocol Information

Protocol Type CDP
Smart Contract Language Solidity
Official Website abracadabra.money/
Protocol Twitter/X @MIM_Spell
Team Anonymous
Source Code Unverified

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 arbitrum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Abracadabra Spell's contract logic - root cause: protocol logic / exchange (dex),yield aggregator
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 Audit Report 1 — still lost $13.0M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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 Abracadabra Spell

The Abracadabra Spell 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