← Security & incidents

BTC-E

Hack Jul 31, 2012 · API key compromise

Taken i
4,500 BTC

No dollar figure was reported, so we do not rank it by size.

At a glance
Date
Jul 31, 2012
Severity
—
Way in
Keys and infrastructure
How
API key compromise
Chain
—
Recovered
None reported

What happened i

BTC-E lost 4,500 BTC on July 31, 2012, after an attacker compromised its API key for a payment processor and created fake deposits to trade for bitcoin.

Funds after the attack i

Nothing recovered, returned or frozen has been reported so far. Funds often come back days or weeks after a theft; this updates when the record does.

Timeline i

  1. Jul 31, 2012 The attack · 4,500 BTC
  2. Added to our incident archive

BlockBoard stories i

We have no story about this incident yet. Smaller incidents are often not covered by the newsrooms we read.

Similar past incidents i

WhenWhoHowTaken
Nov 12, 2026 MapleStory Universe Server intrusion —
Nov 10, 2026 Initia Private key leak $615.0k
Nov 6, 2026 Unocoin Infrastructure compromise —
Nov 2, 2026 Solana MEV Bot King Hot wallet key compromise $856.0k
Oct 29, 2026 Binance DevOps Engineer’s laptop compromised $6.3B
Oct 27, 2026 Predict.fun Private key leak $397.7k

Earlier incidents at BTC-E i

WhenHowTaken
Jul 25, 2017 — $91.0M

Source: BlockBoard. Information only, not advice.