Pages:
Author

Topic: mtgox hack confirmed - page 2. (Read 4714 times)

member
Activity: 73
Merit: 10
June 19, 2011, 02:17:31 PM
#6
well if it was rolled back then it wouldn't be at 1 cent per coin.  Probably just about 100 coins worth.

That guy who owned that many coins better get smart..
member
Activity: 115
Merit: 10
June 19, 2011, 02:17:16 PM
#5
I'm pretty sure it's extremely easy to look for all withdraws on the compromised account and talk to the processor that is handling it and get it cancelled.  This is easy peesy stuff to do.  

Mtgox is doing a great job in this situation.
aop
newbie
Activity: 34
Merit: 0
June 19, 2011, 02:16:59 PM
#4
This also confirms that someone has 500k BTC in his mtgox account and he is most likely the person behind constant price manipulation on Bitcoin market.
sr. member
Activity: 284
Merit: 250
June 19, 2011, 02:15:36 PM
#3
So he got away with $1000 worth of BTC at $0.01 per coin?  ouch
full member
Activity: 126
Merit: 100
June 19, 2011, 02:15:14 PM
#2
wow
sr. member
Activity: 364
Merit: 250
June 19, 2011, 02:11:28 PM
#1
This just in from mtgox

Huge Bitcoin sell off due to a compromised account - rollback

Mark Karpeles
posted this on Jun-20 04:07

The bitcoin will be back to around 17.5$/BTC after we rollback all trades that have happened after the huge Bitcoin sale that happened on June 20th near 3:00am (JST).

Service should be back by June 20th 10:00am (JST, 01:00am GMT) with all the trades reversed and accounts available.

One account with a lot of coins was compromised and whoever stole it (using a HK based IP to login) first sold all the coins in there, to buy those again just after, and then tried to withdraw the coins. The $1000/day withdraw limit was active for this account and the hacker could only get out with $1000 worth of coins.

Apart from this no account was compromised, and nothing was lost. Due to the large impact this had on the Bitcoin market, we will rollback every trade which happened since the big sale, and ensure this account is secure before opening access again.
Pages:
Jump to: