Incident Overview
On April 28, 2025, a social engineering attack led to the theft of 3,520 BTC (~$330.7M) from an individual user.
The attacker used social engineering to deceive an elderly U.S. victim into transferring 3,520 BTC to the address bc1qcrypchnrdx87jnal5e5m849fw460t4gk7vz55g. Soon after the theft, the funds began moving through over six instant exchanges and were rapidly converted into Monero (XMR), contributing to a 50% spike in XMR’s price.
This laundering tactic was likely chosen for its privacy features, making tracking difficult. The event has been confirmed as a non-smart-contract exploit, and instead a high-value personal compromise—highlighting ongoing risks from social engineering in crypto.
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Phishing, these are the critical security checks that could have prevented this incident (April 2025).
- Verify all logic paths related to Phishing 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
- 01
Learn to Prevent the Next Phishing
The Phishing 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.