Taken i
$4.4M
Larger than 76% of the 2,956 incidents with a figure in our archive; 426 were larger.
At a glance
- Date
- Feb 17, 2014
- Severity
- Moderate 3/5
- Way in
- Keys and infrastructure
- How
- Private key compromised
- Chain
- Bitcoin
- Recovered
- None reported
What happened i
Picostocks lost $ 4,430,000 in Bitcoin on 2014-02-17 after insiders copied and decrypted private keys.
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
- Feb 17, 2014 The attack · $4.4M taken
- Added to our incident archive
BlockBoard stories i
Similar past incidents i
| When | Who | How | Taken |
|---|---|---|---|
| Aug 1, 2020 | CWT | Ransomware | $4.5M |
| Oct 25, 2023 | LastPass | Information leakage | $4.4M |
| Nov 4, 2024 | MetaWin | Key leaked via infrastructure | $4.4M |
| Feb 21, 2026 | IoTeX’s ioTube bridge | Private key leakage | $4.4M |
| Dec 16, 2022 | Raydium | Private key leakage | $4.4M |
| Aug 1, 2022 | ZB | Wallet stolen | $4.3M |
Earlier incidents at Picostocks i
| When | How | Taken |
|---|---|---|
| Nov 29, 2013 | Compromised keys (Former Keyholder) | 5,896.230 BTC |
Source: BlockBoard. Information only, not advice.