Purse Hack

TOTAL LOST $2.5M
Medium Access Control

Summarize with AI

Affected Chain 2015 Incident surface
Recovered $2.5M 100.0% returned
All-Time Rank #578 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Purse.io users were the target of hackers who may have gained access and compromised a third-party email service provider used by the company.

The first signs of the theft came to light after a user took to Reddit to report unauthorized withdrawals from the user’s Purse.io wallet:

https://www.reddit.com/r/Bitcoin/comments/3o9ju8/my_purseio_account_was_compromised/

The attack flow:

- users received an email asking for their account passwords to be changed

- soon after, the targeted users also received a withdrawal request (after the compromise of the password)

- moments later, a withdrawal confirmation came along, confirming the theft.

The company stated that 11 users were affected and 10.235 bitcoins were withdrawn without users’ consent. Purse.io confirmed that the compromised users have been reimbursed, and their accounts have since been secured.

Incident Report

Protocol / Project Purse
Date of Incident
Attack Technique Access Control
Classification Other

Protocol Information

Protocol Type Exploit/Access control
Official Website purse.io/
Protocol Twitter/X @purseIO
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Mineable

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Purse's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Access Control audit checklist and test coverage

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

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

Funds Recovery

100.0%

Recovered

$2.5M

Net Loss

0

Related Attack Classes

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

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Purse

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