Additional data to corroborate, delineate, compare, contrast, highlight, and/or provide a pattern
source:
https://bitcointalk.org/index.php?topic=83794.0June 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.27 BTC[5] (lower bound)
Total: Lower bound 2643.27 BTC
Equivalent USD: 46970.91 $ (trades on Mt. Gox not reliable at the time)
Equivalent in June 2013 BTC: 473 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.42939378 BTC
Equivalent in June 2013 BTC: 712 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.58205388 BTC
Equivalent USD: 1110544 $ (wt. avg, definitely >$1M, rounded to nearest $)
Equivalent in June 2013 BTC: 10600 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 BTC: 2290 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.
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 BTC: 82.0 BTC
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.