CoinStats Hack

TOTAL LOST $2.0M
Medium Phishing

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #647 By amount stolen
Protocol Type Exploit/Phishing Target category

Incident Overview

Jun-22-2024 CoinStats portfolio tracker was hacked and after using a phishing link users have lost about 2M USD.

Cryptocurrency portfolio manager CoinStats was hacked on Friday, resulting in the theft of over $2 million from 1,590 wallets. The platform shut down its application to mitigate the attack. Wallets created within CoinStats were affected, while connected wallets and CEXes remained secure.

Some impacted users received phishing messages that directed them to a malicious website. CoinStats CEO Narek Gevorgyan confirmed $800,000 was stolen from two wallets that imported their seed phrases to CoinStats Wallet. Evidence suggests the North Korean Lazarus Group was behind the attack.

CoinStats resumed operations on Monday with limited functionalities. Users with affected wallets were advised to move their funds immediately. The platform emphasized that only read-only access is required for connected wallets, ensuring their funds are not at risk.

Example of tx:

https://etherscan.io/tx/0x8d036063…745e57

Incident Report

Protocol / Project CoinStats
Date of Incident
Attack Technique Phishing
Classification Other

Protocol Information

Protocol Type Exploit/Phishing
Official Website coinstats.app/
Protocol Twitter/X @CoinStats
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 phishing 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 CoinStats's contract logic - root cause: other
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 Phishing audit checklist and test coverage

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

  • 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 Trial

Related Attack Classes

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

See all Phishing Attacks examples →

Sources & References

Learn to Prevent the Next CoinStats

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