LIST OF BIGGEST BITCOIN SCAMS AND HEISTS

List of Bitcoin Heists
Following is the result of research on prior Bitcoin-related thefts. I have provided dates and times as I know them. The list is designed to be as accurate and informative as possible, and most of it is well-referenced. For disputed thefts, I have applied best judgement and included the ones that were most publicly accepted.

Because of the volatile nature of Bitcoin's exchange price, I have denominated heist estimates in 
BTC. Although not heists per se, major permanent bitcoin-denominated losses are also included in this list. If I missed any major thefts, heists, or losses, or if you have any other information to contribute to one of these events, please leave a reply in this thread.

Additionally, I would be grateful if contributors write commentary for each theft. Ideally, the theft descriptions should be as detailed as possible. Much of the present commentary is inadequate.

Table of Contents
·      Table of Contents
·      Licence
·      Factual inaccuracies
·      Donation
·      Qualification
General
·      Instructions
ZigGap
·      Thefts not included
·      On watch
·      References
·      Credits

Licence
This entire document is licenced under the public domain. If that is not permissible in your jurisdiction, it can then be licenced under any permissible licence of your choosing.

The author of this list believes all information contained thereof to be factual; however, the author takes no responsibility for any losses associated with factual inaccuracies in the list.

Factual inaccuracies
Although I make every attempt to ensure information in the list is well-cited and factual, there is always the possibility of error (whether on my part or on my source's part). If you find a factual inaccuracy, please report it. You will be credited appropriately for such reports.

Donation
Donations are appreciated and are accepted at 
1MLSW1nmYkHqaHWNNkHSAHct6exd8fYYLX. Alternatively, consider a donation to a charitable cause. Many victims of these thefts accept donations, and they likely need the donations more than I.

Qualification
Without properly-defined bounds, this list could not possibly be complete. Consequently, several clauses below limit the scope of the list.

General
Generally, a major heist, theft, hack, scam, or loss must cause damage greater than or equal to 1000 
BTC, in BTC damage only, to qualify for inclusion in this list. Thefts related to Bitcoin but with most damage in another currency do not qualify, unless customers were damaged in BTC. Borderline thefts may qualify if reasonable estimates are over or equal to 1000 BTC. Thefts that do not strictly qualify but are of significant importance are listed in thethefts not included section.

Managing Bitcoin prices
It is well-known that Bitcoin prices are volatile. Before 2011, the value of a single 
BTC was extremely low. Consequently, this list ignores most events that occurred before 2011. If a theft, hack, scam, or loss caused damage greater than or equal to 5000 BTC before 2011 (i.e., in 2009 or 2010), it is not listed on the severity charts. If a theft, hack, scam, or loss caused damage less than 5000 BTC before 2011, it is not listed on this list at all.

This list also employs USD cutoff values. Thefts with USD damages below the given cutoff for the year will still be included, but will be excluded from or unranked in severity lists.

Cutoff values so far are below:
Year
Cutoff Value
Severity list cutoff
2009
5000 BTC*
N/A
2010
5000 BTC*
N/A
2011
1000 BTC
12000 $
2012
1000 BTC
12000 $
2013
1000 BTC
12000 $
* These thefts are not listed in the BTC-denominated severity chart.

Included borderline thefts
Finally, another clause is provided to allow important thefts not meeting the cutoff to remain included. Borderline thefts, which have less than 1000 
BTC in total damages, may still be included if their total damage when measured in June 2013 BTC exceeds 500 BTC. This measurement is based on Mt. Gox price data prior to 2013-06-09, Bitstamp price data after 2013-06-10, and US CPI data published by the United States Bureau of Labor Statistics.

Instructions
For ease of navigation, I have assigned each theft a name. Note that this name is neither official nor permanent and is used solely for ease of navigation. To search for the heading that details the actual theft, simply use your browser's Find function and search for the name. This will either bring you to the theft itself, or a link to the theft. If the latter, simply click the link to be directed to the theft.

Some links will appear in commentary and in lists. These can be clicked; their destination is set to the beginning of the linked incident's section.

List of events by severity
NB: This section is under construction.
In this section, each theft is listed alongside the value stolen when converted to a June 2013 
BTC equivalent. This represents the true value stolen and is generally the best list in that regard. No incidents need be left out of this list, thanks to its method of ranking based on true severity.

List of events by 
BTC value stolen
In this section, each theft is listed along with its rank, severity, and time, ordered by the highest m
BTC value stolen from most severe to least. To navigate to a theft, simply click on the link.
Critical (≥10 kBTC)
Rank
Name
Time
Severity
1
2011–2012
est. 263024 BTC
2
October 2013
171955.09292687BTC
3
July 2011
78739.58205388BTC
4
March 2012
l.b. 46653.46630495BTC
5
July 2012
40000.00000000BTC
6*
May 2012
Unresolved as of December 2012
18547.66867623BTC
39000 
BTC total impact
7
June 2011
25000.01000000BTC
8
April 2012
est. 30000 BTC
9
September 2012
u.b. 24086.17219307BTC
10
August 2011
est. 17000 BTC
11
October 2011
est. 11000 BTC u.b. 15000 BTC
* Rank includes pass-through impact

Major (≥1 k
BTC)
Rank
Name
Time
Severity
12
September 2012
9222.21195900BTC
13
June 2011
est. 7000 BTC
14
July 2012
est. 4500 BTC
15
October 2013
est. 4100 BTC
16
June 2011
4019.42939378BTC
17
September 2011
est. 4000 BTC
18
Unknown
est. 4000 BTC
19
2011–2013
est. 4000 BTC
20
September through November 2012
3500 BTC a. 3457 BTC
21
April 2012
3171.50195016BTC
22
June 2011
l.b. 2643.27BTC
*
October 2011
2609.36304319BTC
*
February 2012
l.b. 2211.07786728BTC
23
February 2013
est. 2000 BTC
24
July 2012
1852.61553553BTC
25
2012
a. 1708.65967460BTC
26
July 2013
a. 1300 BTC
27
March 2013
a. 1254 BTC
28
October 2012
1173.51659074BTC
*
2011
a. 1138.98BTC
*
2012
est. 1000 BTC
* Unranked because USD value at time does not meet cutoff.

Borderline (<1 kBTC)
Rank
Name
Time
Severity
29
March 2013
960.09645667BTC
30
April 2013
922.99063322BTC

List of events by USD equivalent of m
BTC at time of theft
NB: This section is outdated.
This section houses a list of thefts, from most severe to least, by the USD equivalent of m
BTC at that time. Note that USD values stolen, if any, are not included, only the mBTC value.
1. Bitcoin Savings & Trust (1834303 $)
2. MyBitcoin Theft (1110544 $)
3. Allinvain Theft (502750.20 $)
4. July 2012 Bitcoinica Theft (305200 $)
5. Bitfloor Theft (248088 $)
6. Linode Hacks (230468 $)
7. Bitomat.pl Loss (236000 $)
8. Tony Silk Road Scam (150000 $)
9. Stefan Thomas Loss (128000 $)
10. Just-Dice.com Incident (121000 $)
11. Cdecker Theft (113894 $)
12. May 2012 Bitcoinica Hack (91306.46 $)
13. XBTGuild Incident (58737 $)
14. Bit LC Theft (51000 $)
15. Bitcoin7 Hack (50000 $)
16. June 2011 Mt. Gox Incident (46970.91 $)
17. BTC-E Hack (42000 $)
18. 2012 Trojan (38000 $)
19. Mooncoin Theft (24000 $)
20. Betcoin Theft (15509 $)
21. Bitcoin Syndicate Theft (12134.61 $)
U. Ubitex Scam (11668.70 $)
U. Andrew Nollan Scam (10978 $)
U. October 2011 Mt. Gox Loss (8115.12 $)
U. Bitscalper Scam (5000 $)

List of events in rough chronological order
Stone Man Loss
Type: Loss
Time: August 09, 2010, 11:35:00 PM ± 600 s
Victim: Stone Man @BitcoinTalk
Status: Coins lost, effectively destroyed
Amount: Exactly 8999
.00000000BTC
Equivalent in June 2013 
BTC5.73BTC
Transaction of interest: eb5b761c7380ed4c6adf688f9e5ab94953dcabeda47d9eeabd77261902fccccf
Due to not keeping proper wallet backups, 8999 BTC sent as change were effectively destroyed when the private key controlling them was lost. Because this theft is from 2010, it is not included in severity lists.

Ubitex Scam
Time: April 2011 to July 2011
Victim: Investors on GLBSE of Ubitex
Status: Ubitex founder known, but nothing returned
Amount: About 1138
.98BTC (amount “invested” into Ubitex)
Equivalent USD: 11668.70 $ (wt. avg)
Equivalent in June 2013 
BTC155 BTC
Ubitex was the first company to be listed on the now-defunct GLBSE “stock exchange”, which has been criticised for its illegal operations.[1] The company was run by a minor, but this fact was not initially known.

Around 1000 
BTC of the missing investments are said to have been “spent”, many of which were further scammed, or converted into USD without follow-up.

The Ubitex scam would not have been possible today. Bitcoin users at the time were enjoying their newly-acquired wealth thanks to significant appreciation. Most “investors” at the time were extremely naïve.


Stefan Thomas Loss
Type: Loss
Time: June 2011
Victim: Stefan Thomas
Status: Coins destroyed (no thief)
Amount: Estimate 7000 
BTC[2]
Equivalent USD: 128000 $ (wt. avg, rounded to nearest thousand)
Equivalent in June 2013 
BTC1250 BTC
Stefan Thomas, an early adopter (and eventually developer) of Bitcoin, uses this loss to teach other Bitcoiners the importance of backups—many of them. He had three copies of his wallet, and yet lost all of them.

Allinvain Theft
Time: June 13, 2011, 05:52:00 PM ± 600 s [satoshi estimated block transmission time]
Victim: Bitcointalk.org user “allinvain”
Status: Thief uncaught
Amount: Exactly 25000
.01000000BTC[3]
Equivalent USD: 502750.20 $
Equivalent in June 2013 
BTC4480 BTC
Chief transaction of interest: 4885ddf124a0f97b5a3775a12de0274d342d12842ebe59520359f976721ac8c3
A polarizing theft, its authenticity has undergone much dispute. Some believe that it was set up as a ploy for donations. However, these critics often lack evidence to back up their claims. Indeed, the victim was an early adopter who mined many coins at a low cost, so there is little reason for him to sabotage Bitcoin's image.

Although the hack attracted great attention in its day, said fame has mostly subsided. Even today, however, the hack still affects Bitcoiners. A common debate among Bitcoin users is that of “tainting” coins, and this hack is often used as an example for why “tainting” coins is futile. In just a few years, coins stolen in this hack are now present in nearly every user's wallet. This rapid redistribution is often cited as a reason that a tainted coin system would certainly fail.


June 2011 Mt. Gox Incident
Time: June 19, 2011, 06:00:00 PM ± 1 h (theft), days ensuing (hacks & withdrawals)
Victim: Mt. Gox (some claim also customers)
Status: Thief uncaught
Amount:
Stolen by thief: 2000 
BTC[4]
Additional withdrawn from Mt. Gox: 643
.27BTC[5] (lower bound)
Total: Lower bound 2643
.27BTC
Equivalent USD: 46970.91 $ (trades on Mt. Gox not reliable at the time)
Equivalent in June 2013 
BTC473 BTC
Transactions: none released officially
Mt. Gox, then the leading BTC/USD exchange service, suffered a severe breach as a consequence of an ownership change. The sale conditions involved a share of revenue to be remitted to the seller. To audit this revenue, the seller was permitted an account with administrator access.[4]

The seller's administrator account was hacked by an unknown process. The priveleges were then abused to generate humungous quantities of 
BTC. None of the BTC, however, was backed by Mt. Gox. The attackers sold the BTC generated, driving Mt. Gox BTC prices down to cents. They then purchased the cheap BTC with their own accounts and withdrew the money. Some additional money was stolen by non-attacking traders capitalizing on the dropping price and withdrawing in time, including toasty, a member of BitcoinTalk.

Mt. Gox resolved the hack by reverting trades to a previous version. Many customers claim they have lost money from this reversion, but Mt. Gox claims it has reimbursed all customers fully for this theft. After the incident, Mt. Gox shut down for several days.
[6]

The event's scale was widely disputed; some report a theft of almost 500000 
BTC due to related account hacking. However, these reports are sparse and disreputable. Closer inspection puts the losses at closer to 2500 BTC.

Aside from the direct damages of the theft, the hack involved a database leak. Some weaker passwords were used to conduct the relatively more severe 
Mass MyBitcoin Thefts.

Mass MyBitcoin Thefts
NB: Not to be confused with the far more severe MyBitcoin Theft.
Time: 2011-06-20 through 2011-06-21
Victim: MyBitcoin users with weak account passwords
Amount: Exactly 4019
.42939378BTC
Equivalent in June 2013 
BTC712 BTC
Transactions: all to 1MAazCWMydsQB5ynYXqSGQDjNQMN3HFmEu
[7]
Users with weak passwords on MyBitcoin who used the same password on Mt. Gox were in for a surprise after the June 2011 Mt. Gox Incident allowed weakly-salted hashes of all Mt. Gox user passwords to be leaked. These passwords were then hacked on MyBitcoin and a significant amount of money lost.[8]

MyBitcoin estimates indicate 1% of MyBitcoin users were affected.
[8] Users that were not affected would be later stolen from anyways, due to the subsequent MyBitcoin Theft.

MyBitcoin Theft
Time: Unknown time in July 2011 (claimed it was a process)
Victim: MyBitcoin & customers
Status: Thief unknown, planned shutdown suspected (disputed theft)
Suspects: “Tom Williams”, likely pseudonym (founder of MyBitcoin)
Amount: Exactly 78739
.58205388BTC
Equivalent USD: 1110544 $ (wt. avg, definitely >$1M, rounded to nearest $)
Equivalent in June 2013 
BTC10600 BTC
Transaction information: none
Little information was released about the MyBitcoin theft, however, many argue that Tom Williams ran it as a scam (and was not a theft per se). In terms of both dollars and bitcoins, this was by far the largest theft, however, it is possible it was simply a scam. Although MyBitcoin offered to release its code as a gift to the community, it failed to follow through on that promise. In the months ensuing, some evidence has been uncovered supporting mortgage broker Bruce Wagner; however, any evidence is inconclusive.

The theft resulted in the closure of MyBitcoin, which was once a successful Bitcoin company in Bitcoin's early days.


Bitomat.pl Loss
Type: Loss
Time: 2011-07-26
Victim: Bitomat.pl
Status: Coins destroyed (no thief)
Amount: Estimate 17000 
BTC (likely estimate/lower bound, no tx due to technical reason)
Equivalent USD: 236000 $ (rounded to nearest thousand)
Equivalent in June 2013 
BTC2290 BTC
Bitomat.pl, during a server restart, had its remote Amazon service that housed the wallet wiped. No backups were kept. Mt. Gox later bailed bitomat.pl out, and neither customers nor original owners suffered any loss from the incident.

Mooncoin Theft
Time: 2011-09-11
Victim: Mr. Moon, Mooncoin, & Customers
Status: Unknown (Federal intervention suspected)
Amount: Estimate 4000 
BTC (conservative estimate based on SC values)
Equivalent USD: 24000 $ (rounded to nearest thousand)
Equivalent in June 2013 
BTC219 BTC
Transactions: numerous
Moonco.in's hack has been compared to the MyBitcoin of SolidCoin, back when it remained a powerful cryptocurrency. Over 800000 SC have been removed from circulation, only to have been put back through SolidCoin 2.0. The effects on Bitcoin were also substantial, and the effect on Namecoin was not negligible. In total, this may have been the worst cross-currency hack in cryptocurrency history.

Bitcoin7 Hack
Time: 2011-10-05 (UTC)
Victim: Bitcoin7 & Customers
Status: Hacker unknown (officially from Eastern Europe or Russia), scam suspected, some returned
Amount: Estimate 11000 
BTC*
·      Based on size of order books at that time, ~15000.
·      A quarter supposedly not stolen (3 of 4 wallets compromised).
·      Rounded to 11000 BTC
* Bitcoin7 may have disappeared with more (u.b. 15000 BTC).
Equivalent USD: 50000 $ (rounded to nearest ten thousand)
Equivalent in June 2013 
BTC346 BTC
Bitcoin7 later shut down because of this hack. The magnitude served as a reminder to the Bitcoin community to stop trusting new exchanges without identification.

October 2011 Mt. Gox Loss
Type: Loss
Time: 2011-10-28T21:11 (UTC) [blockchain time, off by up to three hours]
Victim: Mt. Gox
Status: Coins destroyed (no thief)
Amount: Exactly 2609.36304319 
BTC
Equivalent USD: 8115.12 $ (wt. avg price)
Equivalent in June 2013 
BTC82.0BTC
Transactions:
·      111291fcf8ab84803d42ec59cb4eaceadd661185242a1e8f4b7e49b79ecbe5f3
·      81f591582b436c5b129f347fe7e681afd6811417973c4a4f83b18e92a9d130fd
·      ddddf9f04b4c1d4e1185cacf5cf302f3d11dee5d74f71721d741fbb507062e9e
·      305fbc2ec7f7f2bc5a21d2dfb01a5fc52ab5d064a7278e2ecbab0d2a27b8c392
·      f0137a6b31947cf7ab367ae23942a263272c41f36252fcd3460ee8b6e94a84c1
·      633acf266c913523ab5ed9fcc4632bae18d2a7efc1744fd43dd669e5f2869ce5
·      5bd88ab32b50e4a691dcfd1fff9396f512e003d7275bb5c1b816ab071beca5ba
·      64c01fedd5cf6d306ca18d85e842f068e19488126c411741e089be8f4052df09
·      3be0ac3dc1c3b7fa7fbe34f4678037ed733a14e801abe6d3da42bc643a651401
·      9edab6e7fadf1d6006315ff9394c08a7bf42e19cf61502200a1f73994f8da94b
·      835d4dcc52e160c23173658de0b747082f1937d1184e8e1838e9394bc62c0392
·      aebe39a99114f1b46fc5a67289545e54cbfec92d08fc8ffc92dc9df4a15ea05a
·      aa62bdd690de061a6fbbd88420f7a7aa574ba86da4fe82edc27e2263f8743988
·      6a86e6a5e8d5f9e9492114dafe5056c5618222f5042408ad867d3c1888855a31
·      7ad47a19b201ce052f98161de1b1457bacaca2e698f542e196d4c7f8f45899ab
·      0ca7f7299dc8d87c26c82badf9a303049098af050698c694fbec35c4b08fc3df
·      3ab5f53978850413a273920bfc86f4278d9c418272accddade736990d60bdd53
·      03acfae47d1e0b7674f1193237099d1553d3d8a93ecc85c18c4bec37544fe386
·      15ad0894ab42a46eb04108fb8bd66786566a74356d2103f077710733e0516c3a
·      2d00ef4895f20904d7d4c0bada17a8e9d47d6c049cd2e5002f8914bfa7f1d27b
·      6d39eeb2ae7f9d42b0569cf1009de4c9f031450873bf2ec84ce795837482e7a6
·      07d33c8c74e945c50e45d3eaf4add7553534154503a478cf6d48e1c617b3f9f3
·      6d5088c138e2fbf4ea7a8c2cb1b57a76c4b0a5fab5f4c188696aad807a5ba6d8
Mt. Gox fully reimbursed customers after this incident.

Bitscalper Scam
Time: January 2012 to March/April 2012
Suspects:
·      Alberto Armandi
bitdaytrade @BitcoinTalk
bitscalper @BitcoinTalk
jjfarren @BitcoinTalk
Victim: Users of Bitscalper
Status: MiningBuddy (bitcointalk.org user) attempted to reorganize bitscalper, but failed. No coins have been returned at all.
Amount: Estimate 1000 
BTC (official estimate)
Equivalent USD: 5000 $ (wt. avg, rounded to nearest thousand)
Equivalent in June 2013 
BTC47.9BTC
Bitscalper was founded as an “arbitrage engine”, and users were invited to deposit money. It was promising extremely high and unrealistic returns. As a result, it was suspected of being a scam from the beginning, fears that were compounded due to a shady and anonymous management. After Bitscalper shut down without returning user funds, BitcoinTalk user MiningBuddy attempted to reform Bitscalper using the remnants of the engine. However, no success was found and the coins could not be returned.

Bitcoin Savings and Trust
Time: 2011–2012
Victim: Creditors of First Pirate Savings and Trust, later Bitcoin Savings and Trust
Status: Trendon Shavers (Perpetrator) caught by SEC
[9]
Amount: Lower bounds 150649 
BTC[9]193319 BTC[10]200000 BTC[11]Estimate 263024 BTC[12]Upper bound >700467 BTC[13]
Equivalent USD: 1834303 $
Equivalent in June 2013 
BTC26800 BTC
More information on Trendon Shavers default.

Andrew Nollan Scam
Time: February 2012
Victim: Investors of Shades Minoco, creditors of bitcointalk.org user “shakaru”, investors of BitArb
Status: Andrew Nollan (a.k.a. shakaru
[14]) (thief) known but disappeared, repaid some (not included in amount)
Amount: Lower bound 2211.07786728 
BTC, possibly more [15]
Equivalent USD: 10978 $ (wt. avg price, rounded to nearest $)
Equivalent in June 2013 
BTC106 BTC

Linode Hacks
Time: Late 2012-03-01, Early 2012-03-02
Victim: Bitcoinica, Bitcoin.cz mining pool (Marek Palatinus), Bitcoin Faucet, possible others
Status: Thief unknown, not caught. Linode employee suspected.
Amount:
·      Bitcoinica: 43554.02005417BTC[16]
·      Bitcoin.cx: 3094.45825078BTC[17]
·      Bitcoin faucet[18]: 4.98800000BTC[19]
Total: About 46653.46630495BTC
Equivalent USD: 230468 $ (rounded to nearest $)
Equivalent in June 2013 
BTC2140 BTC
Transactions of interest:
·      5a09f4ef0e91bc7bc044365cd27236fe4ac3c02088ac21ab51c93c8a11d33d4b
·      7b45c1742ca9f544cccd92d319ef8a5e19b7dcb8742990724c6a9c2f569ae732
·      901dbcef30a541b8b55fae8f7ad9917ef0754bda5b643705f3773e590785c4d3
·      a57132e2cbc580ac262aa3f7bac1e441d6573f9633118bc48009618585a0967e
·      a82ad85286c68f37a2feda1f5e8a4efa9db1e642b4ef53cb9fd86170169e5e68
·      ff04763e3e8c93e43799dbbca833e183faad7e2611f20f136f47c2f1049481ae
·      0268b7285b95444808753969099f7ae43fb4193d442e3e0deebb10e2bb1764d0
·      34b84108a142ad7b6c36f0f3549a3e83dcdbb60e0ba0df96cd48f852da0b1acb
·      14350f6f2bda8f4220f5b5e11022ab126a4b178e5c4fca38c6e0deb242c40c5f[18]
In early March 2012, the New Jersey-based web and cloud hosting company Linode was suspected of robbing many popular Bitcoin services. A vulnerability in the customer support system was used to obtain administrator access to the servers. Once the Linode servers were compromised, eight accounts dealing with bitcoins were targeted.[20] The hardest hit was the bitcoin trading platform, Bitcoinica. This resulted in the unauthorized transfer of BTC from the “hot wallets”, a term used to describe operational withdrawal wallets, of the services affected. A severe bitcoin-denominated theft, the Linode theft also affected Tradehill, but no coins were stolen from them; instead, Tradehill had a short downtime because of the incident. In the aftermath of this theft, all the services migrated to other platforms. To this day, Bitcoin users fear Linode and usually refrain from using its services.

Betcoin Theft
Time:
Event
Time
Theft Commences
Transaction: #1, #2
2012-04-11T10:55:54
Theft Continues
Transaction: #3
2012-04-11T12:15:49
Theft Culminates
Transaction: #4
2012-04-11T12:43:14
All times are blockchain time, and have possible error of up to 3 hours.
Victims: Betco.in, creditors
Status: Hacker not known. Some of creditors' deposits were repaid, around 2900 
BTC outstanding.[21]
Amount: Exactly 3171
.50195016BTC[22]
Equivalent USD: 15509 $ (rounded to nearest $)
Equivalent in June 2013 
BTC148 BTC
Transactions of interest:
[23]
·      266e4682abdf4932c4c271872ca9ba6bfdbe75941eb9ba4c4d81e4d3c7364e4b
·      40fc8f6b2f222fb2871a38a245132ed1eada9ff6aec8d46ebe74b29c64fd82a7
·      bf70ac1d2b702dbe0e14fbefb3a0cb2ff5ee5aa425cfe4249f16d6ede7b3ff14
·      92968a2331a02a3128460a64ba16fbf8d3a2fc79ebc8882300015d3ca0e4fb17
Similar to the Mooncoin Theft a year ago, and just as devastating, a gambling website's customers lost a large amount of money. This time, the owner took just as large a hit: all the deposits, plus non-live storage, were stolen. 2900 BTC remains to be refunded to creditors today.[21]

Tony Silk Road Scam
Time: 2012-04-20
Victim: Buyers on Silk Road
Status: Scammer known to be Silk Road user “Tony76”
Amount: Estimate 30000 
BTC[24]
Equivalent USD: 150000 $ (wt. avg price, rounded to nearest thousand)
Equivalent in June 2013 
BTC1400 BTC
Users of Silk Road, an underground drug market using Bitcoin as the default currency, bought significant quantities of illicit drugs from trusted vendor “Tony76”. Although Silk Road has an escrow system, trusted vendors are allowed to bypass the system and request that the buyers pay first. On April 20, which is a popular day for drug sales in American culture, Tony76 offered drugs at a significant discount. However, none of the products made it to the customers, revealing the sale as an elaborate sham.

May 2012 Bitcoinica Hack
Time: May 12, 2012, 11:19:00 AM [blockchain time, off by up to three hours]
Victim: Bitcoinica, LLC
Status:
·      Hacker unknown, minimal coins were returned.
·      Venture capital group Wendon Group threatened legal action against Bitcoinica Consultancy.
·      Receivership in New Zealand ongoing.
Amount:
·      Bitcoinica: Exactly 18547.66867623 BTC
·      Creditors of Bitcoinica: Pending liquidation
BitMarket.Eu: About 19980 BTC
Total impact: At least 38527 BTC
Equivalent USD: 91306.46 $ (last Mt. Gox price)
Equivalent in June 2013 
BTC1830 BTC
Chief transaction of interest: 7a22917744aa9ed740faf3068a2f895424ed816ed1a04012b47df7a493f056e8
Zhou Tong, former founder of Bitcoinica, discovered an entry into Bitcoinica's Rackspace server through an excessively privileged compromised email address. This caused the theft of the entire “hot wallet”, funds stored on-site, as well as the loss of the main database. No backups were kept. Bitcoinica shut down because of this incident. The claims process is still ongoing; however, Bitcoinica is now entering receivership.

On December 21, 2012, it was discovered that BitMarket.eu lost a large portion of customer funds which were stored on Bitcoinica.
[25] These customers were reportedly unaware that their funds were stored on Bitcoinica. Return of a portion of these funds is still possible, pending the outcome of liquidation.

Bitcoin Syndicate Theft
Time: July 04, 2012, 02:34:19 PM (Mt. Gox time)
Victims:
·      Bitcoin Syndicate
Paul Mumby
Shareholders on GLBSE
Suspect: IP 130.83.54.115
Status: Pending
Amount: Exactly 1852.61553553 
BTC
Equivalent USD: 12134.61 $
Equivalent in June 2013 
BTC140 BTC
Medium of theft: Mt. Gox
Transactions of interest: On Mt. Gox. Withdrawal transaction was 4c61d3639f010e30ad305b294cd128f381f58fc161d0badda1f39807dc2f12f7.
A hacker infiltrated the Mt. Gox account used by Bitcoin Syndicate, sold off the USD owned, and withdrew all balances.

July 2012 Bitcoinica Theft
Time: 2012-07-13 (UTC)
Victims:
·      Bitcoinica, LLC
·      Creditors of Bitcoinica (former users of Bitcoinica)
Suspects:
Suspect
Accused by
Defended by
Additional evidence
Zhou Tong
AurumXChange
Mt. Gox
Tihan Seale
Selling bitcoins after event
Chen Jinghai
Zhou Tong


Status: All funds returned
Amount: Exactly 40000.00000000 
BTC (Mt. Gox Daily Limit)
Equivalent USD: 305200 $ (wt. avg, rounded to nearest $)
Equivalent in June 2013 
BTC3030 BTC
Medium of theft: On MtGox.
On July 13, 2012, a thief compromised the Bitcoinica Mt. Gox account. The thief made off with around 30% of Bitcoinica's bitcoin assets, which are likely to cost claimants of Bitcoinica debt. Additionally, 40000 USD was also reported to be stolen. The thief is still unknown at this point, but the theft has supposedly been entirely returned. This theft further complicated the [#=may_2012_bitcoinica_hack]May 2012 Bitcoinica Hack[/iurl].

BTC-E Hack
Time:
Event
Time
Commencing
2012-07-31 00:07 (UTC)
Action taken
2012-07-31 06:30 (UTC)
Victim: btc-e.com
Suspects:
·      BTC-E chat user MrWubbles*, known as:
Bitcoin-related
§ FelicityWubwell @BitcoinTalk
§ SupaDupaJenkins @BitcoinTalk†
§ SupaDupaJenkins @bitcoin-otc
Social networking
§ SupaDupaTweetz @Twitter
§ SupaDupaDotBit @YouTube
* Person has denied committing theft after initially pretending to do it. Evidence supports the faked theft admission as mere trolling.
† Account used at the time of the theft, no longer active.
·      BTC-E (accusation of inside job): Little evidence has been provided; as BTC-E reimbursed its customers, the only thing it could gain from faking the theft was PR—and faking poor security is usually not considered useful PR.
Status: Pending
Amount: Estimate 4500 
BTC (Official estimate)
Equivalent USD: 42000 $ (rounded to nearest thousand)
Equivalent in June 2013 
BTC340 BTC
Medium of theft: On BTC-E.
On July 31, 2012, the BTC-E Liberty Reserve API secret key was broken. This key was shorter than it needed to be at only 16 characters long. The attacker initiated many Liberty Reserve deposits and injected large amounts of USD into the system, which were quickly sold for BTC. Not all BTC was withdrawn; official estimates state that the scope was limited to 4500 BTC. Similar to the June 2011 Mt. Gox Incident, the BTC-E market was disturbed during the duration of the hack. The handling of this hack was widely applauded after BTC-E revealed they would cover the losses and revert to a backup made just before the hack.

Bitfloor Theft
Time:
Event
Time
Theft Commences
Transaction: #1
2012-09-04T03:07:39
Theft Continues
Transaction: #2, #3
2012-09-04T03:12:52
Theft Culminates
Transaction: #4, #5
2012-09-04T03:43:33
All times are blockchain time, and have possible error of up to 3 hours.
Victims: Bitfloor, creditors
Status: Hacker not known, but IP is 178.176.218.157. Some coins repayed to creditors.
Amount: Upper Bound 24086
.17219307BTC
Equivalent USD: 248088 $ (rounded to nearest)
Equivalent in June 2013 
BTC2570 BTC
Transactions of interest:
[26]
·      83f3c30dc4fa25afe57b85651b9bbc372e8789d81b08d6966ea81f524e0a02be
·      d5d23a05858236c379d2aa30886b97600506933bc46c6f2aab2e05da85e61ad2
·      358c873892016649ace8e9db4c59f98a6ca8165287ac80e80c52e621f5a26e46
·      f9d55dc4b8af65e15f856496335a29e2be40f128a7374c75b75529e864579f93
·      42ea472060118ee5aee801cdedbc4a3403f3708a87340660f766e2669f0afeb0
Although the keys to the hot wallet of Bitfloor was secured, an unencrypted backup was mistakenly stored on some of the servers. After a hacker gained entry, most of not only the hot wallet but also the cold wallet was stolen. To this date, none of the coins have been returned by the hacker to Bitfloor. Although Bitfloor briefly shut down after the incident, it has since restarted and has committed to repaying its creditors.[27] Unfortunately, Bitfloor's banks shut down the exchange's operation before all coins could be recouped.

Cdecker Theft
Time: September 28, 2012, 07:21:14 PM
Victim: Cdecker
Status: Thief IP may be 178.140.220.181
[28]
Amount: Exactly 9222.21195900 
BTC
Equivalent USD: 113894 $ (rounded to nearest)
Equivalent in June 2013 
BTC984 BTC
Transactions of interest:
·      6f85951bcecbe64999ad192275af087c5be2922ee13937693992c1ddf9ae8ce6
·      8e6a2d0b8132d3d9edc1fcffe1b3079de59c10c67522e2abc51c1d84b260fdac
A supposedly long-time user of Bitcoin found his personal wallet emptied of a significant amount in late September 2012. Because far more severe personal thefts had occurred in the past, the theft went by without much incident.

2012 50BTC Theft
Date: 2012-10-13
Victim: 50BTC Mining Pool
Status: Unresolved.
Transactions of interest:
[29]
·      9dfdb24667657365c469ff20568fcc820f6f028a125d9c22dc521ae44dcf7c5e
·      bd2ad7b49c22d12cf2f8f12ef601952aed2a96907af4df732156fd90165b5ef5
·      d0035ad189634e90239cca82eb53f78e08c0179620b2bd24e2cb291478c7d57a
·      a2b642bafea45bc128d81314ef33542bc807811ba066329eaa1306bd62bec075
Amount: 1173.51659074BTC
Equivalent in June 2013 
BTC: 127 BTC
The 50BTC mining pool suffered a hack of the billing software in late 2012. They were unable to identify the vulnerability. After the incident, 50BTC completely rewrote the billing software.[29]

2012 Trojan
Time:
Event
Time
Theft Commences
Transaction: #1
2012-10-18 22:56:56
Theft Continues
Transaction: #2, #3, #4, #5, #6, #7, #8, #9, #10
September, October and November 2012
Mralbi@BitcoinTalktheft
Transaction: #11
2012-11-16 03:30:13
Theft Culminates
Transaction: #12, #13
2012-11-16 03:30:13
Victim: Various, incl. Mralbi @BitcoinTalk
Status: Thief IP may be:
·      97.106.160.84
·      178.177.115.229
Amount:
·      Through blockchain: Exactly 3257.00000000 BTC +0.02450000 BTC tx fees
·      Through Mt. Gox: Lower Bound 200 BTC
Total: About 3457 BTC
Equivalent USD: 38000 $ (rounded to nearest thousand)
Equivalent in June 2013 
BTC372 BTC
Transactions of interest:
·      04e378f81eb620f21927639cd4cda00e0473ca958f4d21f2255f37554b5440fa
·      065e7ff6b1503fc023876ffe930dcd9866531812e40bbda72835f232c2f23910
·      0723b67631588b6d5a4a406a9ef8d431c0d5282c6f1cb308fef57c7503d83158
·      0ae924c33555b294a3f0b256da6a02ab996d30be00eaf184d53281009a3a50d6
·      3f938408deb6d20a74f6256d3ba0217df266450d4c00c40d94df7b840f66db05
·      9766b624e004ad1a9369b1b461d33f57e7dddabb43942d34ac10e912cd9ce36b
·      2db76ebd4b5eecf008334d1bdc1f63f764ca3fb9275557a2a82d52ebf52eea9f
·      c041a74fd565c3eb247ff4b1fb6eb0ab9299c3e7d58e5172c28cbe9540858d5a
·      82719bedd0730511385faf68d88b9a03e269a40e3fa5f269efe4a9fc3a821f7f
·      2bc69aa29f56d7051f9cb19bf923c5e2a81879b4f6a3bc849f4166f56d417c2a
·      8d6602b0e8e4479d79e5dab0c35bdb4f7545513cb426411348ec1502413a8f80
·      3a66ebef43041f230e799f1efd3a93e41f875c718da683e236632e13a70cf898
·      0197692748ba894697a0a48fdfdb3e72f3275b079005efad8be062de38b65edf
A trojan horse stole thousands of BTC between September and November of 2012. BitcoinTalk user “mralbi” was a major victim, losing almost 2600 BTC.[30] The same hacker also stole 200 BTC from Mt. Gox accounts, supposedly with the same trojan which doubled as a keylogger.

Bit LC Theft
Time: Discovered February 13, 2013
Victim: Bit LC Inc. and miners
Status: Suspected theft by “Erick”, could be misunderstanding.
Amount: Estimate 2000 
BTC[31]
Equivalent USD: 51000 $ (rounded to nearest thousand)
Equivalent in June 2013 
BTC481 BTC
Transactions of interest:
This alleged theft was unique in that coins held in the hot wallet were safe, but coins held in a cold wallet compromised. The thief is not expected to have access to the coins regardless, so there was little financial gain from this theft. Erick, allegedly the only one with physical access to Bit LC Inc.'s cold wallet, has failed to communicate and withdraw coins. Bit LC Inc. therefore was required to declare bankruptcy. There is no proof that Erick intentionally stole the coins; indeed, some evidence asserts that he or she may simply have disappeared in some manner.

BTCGuild Incident
Time: March 10, 2013
Victim: BTCGuild mining pool
Status: 16 thieves, one has returned 47 
BTC
Amount: About 1254 
BTC[32]
Equivalent USD: 58737 $ (rounded to nearest)
Equivalent in June 2013 
BTC675 BTC
When BTCGuild was upgrading the Bitcoind client to 0.8, the mining pool used its original upgrade plan. However, 0.8 is unique in that it reindexes the blockchain. This prompted a temporary state in which the pool was paying out for difficulty-1 shares, as that was the extent of the blockchain parsed. Sixteen separate thieves subsequently emptied the hot wallet. 47 BTC have been returned to the pool. The pool would on the following day lose even more money thanks to a bug causing its recent upgrade to 0.8 to differ from nodes running 0.7 or lower.

2013 Fork
Time: 2013-03-11
Victims: OKPay, many mining pools including slush, BTCGuild, etc.
Status: OKPay double-spend attack resolved.
Amount: Exactly 960
.09645667BTC[33]
Equivalent in June 2013 
BTC517 BTC
A major blockchain fork occurred due to a bug in Bitcoin-Qt clients which had not upgraded to the new 0.8 version. Unfortuantely, those clients formed the majority of Bitcoin users at the time. The resulting fork split mining pools; those that had upgraded lost block revenue. Some mining pools took the hit, whereas others passed the cost on to miners.

The fork also made possible isolated double-spending attack. Only one such attack was conducted, costing OKPay significantly. Luckily, the thief has since returned the money.


Bitcoin Rain
Date: 2011-10-03 to 2013-03-28
Victims: Investors in Bitcoin Rain, account holders on Mercado Bitcoin.
Perpetrator: Leandro César
Amount: Estimate 4000 
BTC[34]
Equivalent in June 2013 
BTC2150 BTC
A suspected long-running con likened to the infamous Bitcoin Savings and Trust, Bitcoin Rain finally defaulted on March 28, 2013. Leandro César claimed there was a security breach on his exchange website Mercado Bitcoin.[35] As Bitcoin Rain's funds were stored there, investors in Bitcoin Rain as well as account holders on Mercado Bitcoin lost money. Some money was reportedly paid back, but the vast majority is still outstanding.

ZigGap
Date: February to April 2013
Victim: Investors and creditors of ZigGap
Amount: About 1708
.65967460BTC[36]
Equivalent in June 2013 
BTC: 919 BTC
User aethero, who was originally a reputable Bitcoiner, founded ZigGap after two previously succesful ventures, including BitPantry. Purporting to offer easy ways to purchase BTC, ZigGap saw little business. The founder seems to have also suffered mental illness in the latter stages of business operation.[37]

Ozcoin Theft
Time: 2013-04-19
Victim: Ozcoin mining pool
Status: Thief, a user of Strongcoin, known but not disclosed. Strongcoin seized funds and returned 568
.94BTC to the mining pool operator.[38]
Amount: Exactly 922
.99063322BTC[39]
Equivalent in June 2013 
BTC983 BTC
A hacker managed to infilterate Ozcoin's payout script, such that all money was paid out to the hacker's address. Luckily, a day later Strongcoin seized most of the stolen funds and promptly returned them to Ozcoin.

Just Dice Incident
Time: 2013-07-15
Victim: Just-Dice investors, Dooglus
Suspect: Just-Dice.com user “celeste”, who claims he was hacked.
Status: Bets rolled back.
Amount: About 1300 
BTC[40]
Equivalent USD: About 121000 $
Equivalent in June 2013 
BTC1000 BTC
A player on Just-Dice.com with an especially large balance asked to withdraw 1300 BTC. Because the hot wallet did not contain that much money, Just-Dice.com operator “dooglus” manually processed the transaction from the cold wallet. However, “dooglus” forgot to remove the balance in Just-Dice.com's database. The Just-Dice.com user then proceeded to bet the fake balance on the gambling website and subsequently lost it all. Because of the manner Just-Dice.com is structured, the website lost money even though the malicious user did not earn any money from the theft.

To recoup losses, the operator rolled back the gambling losses and corrected the wrong balance. This resulted in losses for all “investors” of Just-Dice.com; however, the operator explains that nobody actually lost money because the bet should never have happened. In conclusion, it seems that odd decisions on the malicious user's part and probability ensured no actual loss from the incident, even though 1300 
BTC was stolen. The amount was simply lost back to Just-Dice.com thanks to luck in the website's favour.

Silk Road Seizure
Dates:
·      2013-10-02: First seizure (Silk Road user funds)
·      2013-10-25: Second seizure (Ross Ulbricht's personal coins)
Victim: Silk Road, Ross Ulbricht, Silk Road users
Perpetrator: FBI seizure
Amount:
·      First seizure: 27618.69843217BTC[41]
·      Second seizure: 144336.39449470BTC[42]
Total: Exactly 171955.09292687BTC
Equivalent in June 2013 
BTCTBD
Silk Road was a former underground marketplace that dealt primarily in Bitcoin. Run by Ross Ulbricht, it was once widely known for frequent narcotic sales.[43] Although it operated under the jurisdiction of the United States, it made little attempt to comply with US law.[44] However, clever use of the Tor technology allowed Silk Road to escape the authorities for years.

Finally, in October 2013, the FBI was able to produce conclusive evidence of Ross Ulbrict's culpability. Ulbricht was found in San Francisco and arrested.
[45] In the days ensuing, it seized a large portion of Ulbricht's personal wealth in addition to stored balances by Silk Road users.[46] However, the FBI has yet to successfully seize an estimated remaining 400000 BTC in Ulbricht's personal wallet.[47].

The first seizure came right as Silk Road's domain was seized, and included funds belonging to Silk Road users. The second seizure came several weeks later, seizing coins belonging to Ross Ulbricht himself.

This seizure is notable in that it is the first major legally authorized seizure. At the moment, Ulbricht is awaiting trial in New York.
[48]

Inputs.io Hack
Date: 2013-10-26
[49] (disputed)
Victim: Inputs.io, passed on to creditors.
Perpetrator: Accusations of inside job.
Transaction of interest: 9536feebe3a50b94f85ca27d56e669a7209bd4188385d55c5b97227c95cf7f74
[50]
Amount: Estimate 4100 
BTC[51]
Inputs.io, a web wallet service run by BitcoinTalk user TradeFortress, was supposedly “hacked” in October 2013 and was unable to repay user balances in full. There are many accusations of the hack being an inside job. TradeFortress had a contentious reputation and had supposedly scammed two separate people before this incident.[52]HYPERLINK "https://bitcointalk.org/index.php?topic=83794.0" \l "post_ref_52" [53] When the theft was announced in November 2013, TradeFortress began offering partial refunds; however, 4100 BTC was not paid back as that was the shortfall from the supposed “hack”.

Thefts without known chronology
Kronos Hack
Time: ?
Suspects:
·      Alberto Armandi
bitdaytrade @BitcoinTalk
bitscalper @BitcoinTalk
jjfarren @BitcoinTalk
Victim: Kronos.io
Status: Legal action possibly pending
Amount: Estimate 4000 
BTC (official estimate)
Amount in June 2013 
BTC400 BTC[54]
A serial scammer, Alberto Armandi reportedly hacked into a website he himself coded. The vulnerability was in the withdrawal script that Alberto coded, reportedly intentionally as a backdoor. Information about Kronos is highly uncertain, due to a lack of communication. Jonathon Ryan Owens was not responsive to demands for information.

Thefts not included
Some thefts in Bitcoin's history, although severe and damaging to Bitcoin users, did not involve the theft of over one thousand bitcoins.
These thefts are listed below.
·      World Bitcoin Exchange, due to fraudulent activity, stole over 5000 BTC worth at the time in AUD. The total amount stolen was 25779.49 AUD. More information: https://bitcointalk.org/index.php?topic=65867.msg923845#msg923845
·      Tradehill was repeatedly hassled by Dwolla, and eventually dropped support after being scammed off 17000 USD. Later fraudulent transactions ended up costing the exchange even more, and after the March 2012 Linode Hacks they shut down, citing 100000 USD stolen or scammed through fraud.

Minor but notable thefts
Other thefts are minor, but are unique in some manner (for example, interesting methods or a first of its kind).
·      First recorded physical theft of bitcoins: https://bitcointalk.org/index.php?topic=52206.0
·      Coordinated hacking of BitcoinTalk accounts allowed theft of many “loaned” bitcoins: https://bitcointalk.org/index.php?topic=61500.0
·      Bitcointalk.org user “Goat” lost 400 BTC through sending to a wrong address. These bitcoins were later recovered:https://bitcointalk.org/index.php?topic=82600.0


References
·          [3]Allinvain's personal account.
·          [4]Mt. Gox official press release.
·          [6]Daily Tech, recap of the incident.
·          [7]Blockchain.info.
·          [10]: Calculation based on 700467 BTC raised and 507148 BTC paid out.
·          [12]Daphne P. Downes of SEC, civil action.
·          [13]SEC litigation.
·          [14]Shakaru's DeviantArt account.
·          [15]Google Docs document.
·          [16]Bitcoinica's official statement.
·          [17]Marek Palatinus's account.
·          [18]Gavin Andresen's account.
·          [19]Blockchain.info transaction.
·          [20]Linode official statement.
·          [21]Official post-mortem report.
·          [22]Blockchain.info address listing.
·          [24]Account of a Silk Road user.
·          [25]Official statement by BitMarket.eu.
·          [26]Bitfloor analysis.
·          [27]Bitfloor official announcement.
·          [28]Personal account by victim.
·          [29]50BTC Official Statement.
·          [30]User mralbi's personal report.
·          [32]IRC conversation.
·          [33]: Mining cost of 748.18715667BTC and OKPay double spend of 211.90930000BTC.
·          [37]Selected example of paranoia on Reddit.
·          [38]Vitalik Buterin, Bitcoin Magazine.
·          [39]Address 16cDeEFn6sraUEJrDCt2Yg3r7j2oazSYEd
·          [40]Coindesk article.
·          [41]: Total sent to 1F1tAaz5x1HUXrCNLbtMDqcw6o5GNn4xqX, excluding dust sent ex post facto as blockchain graffiti.
·          [42]: Total sent to 1FfmbHfnpaZjKFvyi1okTjJJusN455paPH, excluding dust sent ex post facto as blockchain graffiti.
·          [43]Adrian Chen, kotaku.com.
·          [44]United States' criminal complaint.
·          [45]Emily Flitter, Reuters.
·          [46]James Ball, The Guardian.
·          [47]Alex Hern, The Guardian.
·          [48]Associated Press.
·          [49]Statement by TradeFortress.
·          [50]Statement by TradeFortress.
·          [51]Official statement.
·          [52]Accusation by BitcoinTalk user “webr3”.
[54]: Obviously, it is impossible to arrive at an exact value without knowing the time Kronos.io's hack happened. This estimate assumes Bitcoin price was just over 10 USD at the time, which is reasonable given the approximate timeframe.