ALL mtgox password has been compromised, change asap, everywhere you used it

[Bit_Happy]

Emails received, thanks all.

Bit_Happy, if you had an account on MtGox you could easily verify it. My account was on there.

Thanks guys for the info on the strength of the encryption.

I wasn't going to bother with Rapidshare.
Remember all the trolls a week ago. It was possible that, everyone screaming about this is phony, but now I know for certain.

[1715034775]

1715034775

[1715034775]

1715034775

[1715034775]

1715034775

[1715034775]

1715034775

[1715034775]

1715034775

[DamienBlack]

They have my username and the email I signed up with. I cannot confirm that it is my password. The hash must be salted.

[DamienBlack]

They have my username and the email I signed up with. I cannot confirm that it is my password. The hash must be salted.

[kokojie]

It's not entirely clear if the attacker got access to the Mt.Gox source code, but at the moment it's probably safer to assume the salt was compromised as well.

It's definitely NOT safe, someone just showed me a big list of cracked mtgox passwords on IRC channels. It's likely that salt has already been discovered.

[justusranvier]

Change them asap, anywhere you used it.

If anyone out there is still using the same password on more than one site then take this opportunity to stop doing that. Get some kind of password manager and use a different random password of the maximum length and complexity each web site you register on allows.

[elggawf]

Bit_Happy: PM sent. I'm 99% certain it's legit.

It's not entirely clear if the attacker got access to the Mt.Gox source code, but at the moment it's probably safer to assume the salt was compromised as well.

Exactly. When you see a DB leak for a site you're a member of, you don't sit around wondering how strong the hashing mechanism is you start changing your passwords. If you only used the password on MtGox, oh well you don't really have anything to do right now. If you reused the same password anywhere else, stop thinking about how strong the hash is and change your freakin' password - the effort required for the latter is much less than the former and then it's done... from your perspective the information that's leaked is no longer valid. Whether it takes 2 minutes or 2 years to crack your password is irrelevant if you've already changed it someplace else.

Password hashing isn't meant so that a bunch of fools can sit and think "I'm safe" - it's to buy you time between when the credentials are taken, and when they're useful... to give you a chance to make them not useful.

[Man From The Future]

It would appear that almost all the acounts are hashed with unique salts. The issue is, it is still easy to crack any of the weaker passwords with this, thanks to GPU MD5 crackers. Most bitcoin miners have soo much GPU power anyway...

Some passwords from earlier accounts appear to have NO SALT. That, or salt is derived from username. I don't know, sinc eI've not tried cracking any, and do not want to.

[kjj]

Uh, the salt is right there in the file.  Look at line 1.  Password hash is $1$E1xAsgR1$vPt0d/L3f81Ys3SxJ7rIh/

The bold part is the salt for that hash.

The italic part is md5(password + salt)

[Uzza]

I'm not that worried, my password is quite long and secure.

[carlerha]

Looks like the kind of hashes that come out of phpass.
I guess that means if the attackers managed to get hold of the salt, I'm prone to change my password.

[zerokwel]

well look at what some of the users have in there rigs and there are programs like Extreme GPU Bruteforcer out there that can do up to 700million passwords a sec on a geforce 250 and with what people here have in there rigs it would not take long at all.

Anyway change ya passwords to be safe and if you use the same password on another site change that as well (use a different password this time)

[theymos]

I'm certainly never using MtGox again. Who uses MD5 for password hashing nowadays?

[ghost]

This is why all websites should be using bcrypt for password hashing. It's an adaptive hashing function that can be made to perform slower over time as computers get faster. Authentication on websites does not require a fast hashing function for just this reason.

I use 1Password for password management. It was Mac only until recently - there is now a Windows version out there. I had to double check whether I was following my own best practices but I did use a unique password for mtgox.

[imperi]

I'm certainly never using MtGox again. Who uses MD5 for password hashing nowadays?

User #8 is quitting?? Craziness.

[gentakin]

Some passwords appear to be without a salt.

For example, check user id #156. Google for the hash shown as "password" in accounts.csv. Find the password on a forum. (The forum post that comes up on the google search might shed some light on the guy who hacked mtgox?)

So... Anyone with a plain md5 hash (no $-signs) as password in accounts.csv should be worried.

[phelix]

it would have been nice to keep emails encoded mtgox...

[LeFBI]

If the salt hasn't been compromised, then the passwords should be safe, no?

It's not entirely clear if the attacker got access to the Mt.Gox source code, but at the moment it's probably safer to assume the salt was compromised as well.

there is no >the salt< in this case it's 59231 password hashes with 59219 >different< salts. and ~1700 simple md5 hashes.

well look at what some of the users have in there rigs and there are programs like Extreme GPU Bruteforcer out there that can do up to 700million passwords a sec on a geforce 250 and with what people here have in there rigs it would not take long at all.

we're talking about md5crypt a.k.a MD5(Unix) a.k.a. FreeBSD MD5 ...not simple md5()!
with a decent gpu you'll be lucky to get ~1.5Mhash/s per gpu, not 700M. On a single HD4870 i get ~640.0k/s , that's nothing.
anything else than a wordlist attack is pretty useless on these hashes. so if you have a at least decent 8char pass, you should be fine.
if you're one of the poor guys, who's pass was encrypted with simple md5()...well good luck then. but the rest shouldn't worry too much.

however everyone still should change his password when they are back online

[DamienBlack]

Someone with a network should email everyone on the list and let them know.

[Man From The Future]

Someone with a network should email everyone on the list and let them know.

Issue is you'd probably en dup on spam blacklists.

[Durr]

If the salt hasn't been compromised, then the passwords should be safe, no?

It's not entirely clear if the attacker got access to the Mt.Gox source code, but at the moment it's probably safer to assume the salt was compromised as well.

there is no >the salt< in this case it's 59231 password hashes with 59219 >different< salts. and ~1700 simple md5 hashes.

well look at what some of the users have in there rigs and there are programs like Extreme GPU Bruteforcer out there that can do up to 700million passwords a sec on a geforce 250 and with what people here have in there rigs it would not take long at all.

we're talking about md5crypt a.k.a MD5(Unix) a.k.a. FreeBSD MD5 ...not simple md5()!
with a decent gpu you'll be lucky to get ~1.5Mhash/s per gpu, not 700M. On a single HD4870 i'll get ~640.0k/s , that's nothing.
anything else than a wordlist attack is pretty useless on these hashes. so if you have a at least decent 8char pass, you should be fine.
if you're one of the poor guys, who's pass was encrypted with simple md5()...well good luck then. but the rest shouldn't worry too much.

however everyone still should change his password when they are back online

Except that an account with 500k and other accounts were hacked and it's true. So you're opinion that it's all ok is bs.