Topic: What really happened to Mt Gox ... (Read 862 times)
Seems like there was SQL injection...that's how all the hehehe accounts were entered I imagine. Auditor story is a crock.
Well, the answers posted by Mtgox are not sufficient. They still haven't answered how come 500.000 were stored by one single holder; which is very hard to believe. Either many accounts have been exploited, or more likely, it was mtgox's own account that stored this amount.
I think that most likely someone inside/outside mtgox hacked the site and has done away with far more bitcoins than mtgox is willing to acknowledge. Mtgox is furthemore palying for time by pushing forward opening time, as it does yet not know the full extent/full extent of the monetary value/or solutions to the lost bitcoins.
Probably more likely that someone hacked from the outside, as if it were an inside job it could have been done much smother without crashing the system. However, Kevin is more than very likely to be innocent as who in their right mind would be involved in a crime and then instead of just keeping quiet, announce that they have traded etc.
I think that most likely someone inside/outside mtgox hacked the site and has done away with far more bitcoins than mtgox is willing to acknowledge. Mtgox is furthemore palying for time by pushing forward opening time, as it does yet not know the full extent/full extent of the monetary value/or solutions to the lost bitcoins.
Probably more likely that someone hacked from the outside, as if it were an inside job it could have been done much smother without crashing the system. However, Kevin is more than very likely to be innocent as who in their right mind would be involved in a crime and then instead of just keeping quiet, announce that they have traded etc.
What really happened is that wordpress autoblogs have more security than the biggest Bitcoin Exchange... That's what happened 
It's on mtgox.com
An account got compromised so the database was leaked. SQL Injection or other exploits were not a factor.
An account got compromised so the database was leaked. SQL Injection or other exploits were not a factor.
From what i can tell i think that the following happened;
Most probable;
- there was never an auditor involved, the security breach was most likely through injection, bad coding
- since bc was traded at high prices, no one in his right mind will place an order of 0.01 especially not right around the time of attack
- kevin and this "hacker" (= kevin ?) knows alot more than playing innocent
Most probable;
- there was never an auditor involved, the security breach was most likely through injection, bad coding
- since bc was traded at high prices, no one in his right mind will place an order of 0.01 especially not right around the time of attack
- kevin and this "hacker" (= kevin ?) knows alot more than playing innocent
Jump to: