Bitcoin Forum

Not sure if any of you have seen this or not, but here it is:

https://www.nanaimogold.com/microlionsec.txt

If you haven't changed your passwords yet...do it.

If you wanted to see whether or not your password was safe, feel free to check if it was cracked here.

Well, that password is done. I was ignorant to think that would suffice.

Hmm, I was not cracked. Some of the cracked passwords look pretty secure. Like

1036 ... ccFy7KpgN

How did that get cracked? Was that one of the unsalted ones?

1938 ... BESys*t3M

This seems like it should be secure, even though it is leetspeak.

1955 ... RYL4McGT

Again, unsalted? How was this cracked?

13434 ... djcnbimil99332k

I think this was is too far down to be unsalted, and it is too long for rainbow tables. Is it following a pattern I don't see?

13449 ... n833bgva

This looks secure enough to me. How are these getting cracked? How much time does it take?

Mine isn't on there (phew), but it is interesting to see what is.

I've certainly got more industrious in terms of making 20-character 4-type (upper case, lower case, symbol, number) passwords for important uses now. So I am glad this happened, despite the temporary annoyance at having that username and email address broadly published.

Numbers are easy.

Not cracked on both accounts (made one and forgot I had made it!)

Saweet!

Some that stick out that should be relatively strong:
j3n0VA$@
Nephi7187$$$
K7mmI8lAsn1o0q
c0urche$ne
7XiBKeJe5ochSqVW
n0k!@N900
yT#g1Srm123

I'm also curious how these were broken assuming these are salted.

Even if they aren't salted, the longest rainbow table I know of is only 10 characters, alphanumeric only. Most of those don't fit.

I don't think they spent a lot of time cracking them. My password isn't there but should have been fairly easy to crack with some standard multi-word rules.

I wonder if the difficult passwords were reused and had been previously cracked. A lot of people feed lists of publicly cracked passwords as one of their dictionaries.

I was surprised I wasn't on that list. I had a rather weakish (I thought at least) 14 length password with a few capitals and numbers in it.

Remember, even if you aren't cracked now, you might be in the future. Don't count on those passwords.

My password is in that list, but my account is not.

My version has upper/lower case.

By my calculations, a random 9 character password, like this BESys*t3M should take a 5770 about 2/3 of a year to crack. But there it is on the list. How much hashing power did they throw at this?

The fact that a password is in this list doesn't imply that it was cracked. As finack said, the complex passwords were probably stolen by some other means - e.g. phishing - and happened to be reused.

Hmm, so someone who uses the password "7XiBKeJe5ochSqVW" has been phished?

But they didn't crack all the random 9 character passwords. Mine was only 7 characters total, five lower-case letters then two numbers, and it's not on the list.

Paul

That seems like an easy crack compared to some of them. That should only take about 8 minutes on a 5770. Maybe less.

Just because a password is complex doesn't mean the user is not susceptible to phishing, viruses, etc. They could have used the password on an unsecured wireless network - something people do all the time.

An extremely complex password can also lead to a false sense of security, inadvertently making people more susceptible to other forms of attack. It's better to use sufficiently complex *different* passwords with every account, than to use the same extremely complex password on all accounts.

There are just too many complex ones for that to be the answer. But then again, mine is simple compared to some of these and it isn't on the list. So perhaps you are right.

I looked that dude up on Facebook. He's an older guy whose activities include singing, sailing, barefoot hiking, etc. No evidence of computer expertise. The complex password was a false sense of security, and he was phished, in all likelihood.

A 5870 can do 3.8 Billion password combinations a second.

If you have 3 of them in your system like most miners do, thats 11.4 Billion per second

684 Billion per Minute
41 Trillion per Hour
984 Trillion per day (24 hours)
6.8 Quadrillion per week
210 Quadrillion per Month  :o

I think the days of "passwords" you type with a keyboard are over.

Interesting and creepy... <quietly goes off and changes facebook email>

Opps, its actually "just" 3.6 billion per second.

http://i55.tinypic.com/20tjgqg.jpg

What's creepier is that people are fine with publishing so much personal information for the public to see.

Wait, what is this? Is this the MtGox database?

Yes

Even with those numbers, it would take on average a week to crack a purely random 8-character combination of alphanumeric/special characters. If that number is raised to 10, it's 21 years, according to this spreadsheet calculator (http://www.mandylionlabs.com/documents/BFTCalc.xls).

A random selection of some of the more secure looking passwords:

60x8760b6k328vc3v24kw8y1
Y!m4g6s3j*
Ev3rL@NRDX11090821
b1Ackb0x3!1
8W3G7Pds9712++
c65b5DF488
mgq$jc)kw3
w@chtw00rdLanimret!
acy7zkprddv2k3iFd&
VeryStrongPassword

I doubt that these and the many more that are on there 1) got phished and 2)wound up on this particular list at the same time. Well, except for the last guy. Though I do suppose that is an upgrade to using 'password' for a password :P

I also doubt that all of these were phished. But if they weren't, a network about 1% as large as the bitcoin network must have been pointed at cracking them.

Yes but this spreadsheet assumes only 17 billion per hour not 41 Trillion.
And thats just 3 cards, if somebody really wanted to go all out and have 30 cards then who knows.
Might open up a black hole in you PC  LOL
 

Deepbit could crack a 10 char password every three seconds.

The thing is that plenty of people here have reported having weak-ish passwords (including myself) that they didn't crack, so a large cracking network or optimized algs don't explain them.

Has anyone actually checked one of the hashes for one of the strong passwords and confirmed it's correct? Could just be someone fucking around.

If they are legit, they have to have come from another source than just cracking. Either they were pre-cracked or phished or the publisher had access to the passwords some other way.

I wonder if people who aren't cracked, but are reporting that they have easy-ish passwords are people who had very little in their account. Is there any information about whether our account balances were available?

It'd take 4 months to crack a 10-char alphanumeric password.  I don't think the days of "passwords" you type with a keyboard are over.

That said, how did so many of these passwords get cracked so quickly, if it should take centuries to crack some of them based on length?  Were that many people really idiots enough to visit the phishing sites sent in the spam emails?

EDIT:  Also, mine was not cracked.

The throwaway password I used on a throwaway mtgox account is not in the list. It was only 7 characters long with uppercase letters and numbers.

Well, aside from *MAGIC*, by what other method do you believe those passwords were determined?

No you dolt! I took their number for total combinations, and divided it by your password test rate, to determine the amount of time necessary. You could have seen this yourself by actually looking at the numbers, rather than just seeing something that didn't make sense and assuming that was the explanation.

Yep.  This is definetly a wordlist crack from both mangled words and leaked or phished passwords from other sites.  I can say that with 100% certainty because my own password isn't on the list.  My old Mt.Gox password was set for testing the new exchange at a time when a bitcoin was worth a few cents.  I used it on BBSes in the eighties, and it is very far from secure to modern standards.  Not even the nineties standard, I'd say.

ditto

i had no money in it, never have had

i think it's weird though if they managed to make a list of active users.  what does that imply?

I can verify that 7XiBKeJe5ochSqVW is in fact the correct password, he was unsalted, and using "simple" md5. I cannot verify the salted passwords, they seem to be a different type of md5 then I am using. Why are there two different types of md5, and what do I call the second one?

Some of these people with complex passwords could have fallen for the fake mtgox emails

they got mine too..  wonder what percentage of this list even realize that their passwords are floating around on the internet for everyone to see..  thats a lot of passwords.

I set my password to my bitcoin address. What could be more secure than that?! ;D

Now that you've publicly stated this, it should be trivial to get a tool up that searches the block chain for bitcoin addresses and attempts to crack your password with each of them. ;)

http://www.insidepro.com/hashes.php?lang=eng

MD5(unix)

Edit: And the salted passwords match, too, at least the 3 I've checked:
60x8760b6k328vc3v24kw8y1
acy7zkprddv2k3iFd&
8W3G7Pds9712++

Curioser and curioser

Yeah, but look how many characters it has - there's just NO WAY any cracking program could guess this: 1GryC1TD9bXdwrV1YbDX3RnJrS2Ak87Vbw. It's perfect! :D

how could saab9000aeroskodafabiavrs or 7XiBKeJe5ochSqVW be cracked in such a short amount of time?  Even unsalted...

And the uncracked password list that was released had the salts along with each password, so being 'salted' or 'unsalted' shouldn't matter...

I guess i dont understand how password cracking works.  I don't understand how they get multiple chances figuring out a password.  

 

Yes, it matters.  A lot.  Salted means you have to crack each password individually.  You have to run through the entire list of candidates (until a match) for each and every salted password (given unique salts).  With unsalted passwords you can run through the wordlist once, and get all matching passwords with a single MD5 run for each word in your wordlist.  It doesn't matter for one single password, but for 60000 salting means 60000 times more work.  And salting renders rainbow tables useless, because you'd have to build one rainbow table for each possible salt.

I'm surprised I'm not on the list.

What is the possibility of the hash collision? There is no such need those long characters number combination to be the true user password, as far as those hash match the users true hash, then the server will consider them to be the same. Though I would expect the collision password should be much uglier than the one shown in the file.

As written in wikipedia, there is already methods to generate collision 5 years before with some requirements, so it is not surprise that there is a generic method to find collision particular for the password.

My password is not on the list.  It was 'password1'.  I read somewhere that 'password1' is the most common password so I figured it must be good.

Could somebody find the source of this list.  I would really like to know how this was done.  Is it really possible?  I suspect this list is at least partially fake.  My real password should have been easy to crack but is not on the list.

Sam

Thanks for this explanation.  For implementation purposes, how would a website use a unique salt?  For example, when the username types in a password it must be joined to the salt and then an MD5 algorithm ran over the product to compare with the database stored hash.

Somewhere then the salt must be stored, right?

Random, and yes, it is stored.

If the hash started with $, it follows this format:  $<scheme, always 1 here>$<salt>$<hash>.  Scheme 1 means about 1001 rounds of MD5 with complex combinations of the previous round, the password, and the salt.

Other schemes are available for SHA, blowfish, and (try not to laugh) NT.

If it doesn't start with $, it is just a simple unsalted MD5 hash of the input.

I can think of three possibilities:
Password reuse
Malware
Hash collisions

Oh certainly, there are other methods (though password reuse alone doesn't cause this). I was just making the point that the *least likely* method was brute force cracking.

Mine wasn't on this list, but anybody here would be foolish indeed to assume that this means their password wasn't cracked.  If you use the same password in multiple locations, and a security breach occurs in one location, you need to change the password at every location that you used it.

Hash collision seems really unlikely to me. The odds should be microscopically small.

It's microscopically small for SHA hashes but MD5 has been considered broken (or nearly so) for a few years now.

My password wasn't on there, so I'll just throw it out there.  My old mtgox password was 5kGrv3cM5-W_VKc9d6Zc.  And no, I don't use it for anything else....

Edit:  I've also started using 30 character passwords now too.  All this talk about cracking 10 characters in 3 seconds has me paranoid!

I use the same password, what a coincidence.

That's the stupidest combination I've ever heard in my life! The kind of thing an idiot would have on his luggage!

Spaceballs!

26533: hackthis123191

haha! i'm using the internet!!!1

http://t2.gstatic.com/images?q=tbn:ANd9GcTOfMLEoHtsZjy7k0M8jyS7I4X3Vae_wNnSfZFxs7UO7gLJ44wO&t=1

There are about 3000 passwords there out of about 60,000 accounts, or about 5% of the total.

So if it was brute force why only crack 5% of them? They must have used additional info from somewhere.

This plays into my theory that everything will be public for the world to see in the future. Part of the NWO, Apocolypse, and Utopia theory's. Depending on your "views" of it.

[conspiracy]
this list was generated while the Mt.Gox account recovery phase.
[/conspiracy]

Maybe he didn't clean the server completely? what if there was some kind of backdoor? yo rembember that you had to enter your old password on the recovery form. as soon as the inital hackers knew about the recovery procedure, they manipulated the scripts so that the input is stored plaintext or send somewhere. then it just get matched to username/email and voila.


This can be checked so:

Anyone who did NOT recovered his MtGox account AND has a safe password found himself on the list?

I get the feeling that this list isn't any of the bruteforced passwords - only the people that feel for the phishing attacks.

So, I'm not cracked.  Yet ?

Nice.  Makes me feel all warm inside.

I'm not there. My password was 10 chars long.

But the salts are given.  Correct me if I'm wrong, I'm new to understanding this: a password hash here is given as salt*md5*password sort of setup.  If it was just md5*password, you can solve the md5 and then just run that through the list of hashes to get all the passwords?  But if the salts are given then password crackers aren't trying to figure out the [salt] part of the equation, so you can effectively remove that and it just becomes md5*password again.  Right?

like if you have:
[salt1]*md5*[password1]
[salt2]*md5*[password2]
etc... its really hard to solve because you have crack each individual salt - BUT you don't have to crack each individual md5.  If the salts are listed right there on the table (and on MtGox that's what happened) then you're not cracking salts, just the md5 again.  That's how they get all these super-complex passwords - right?  They solved one simple md5 pass, and then used the given salts to get any password instantly.  Or am I not understanding how this works....

no one mentioned rootkits and keyloggers?  :o

Salts prevent people from pre-computing large amounts of hashes and then just simply comparing the hashes to see what the password is. These large lists of pre-computed hashes are called rainbow tables.

Let's imagine you and I both have the same password. If you use an unsalted hash, the resulting hash of the password will always be the same.

user:hashed_password

me:54yg7(momlk32
you:54yg7(momlk32

if I had a rainbow table for that type of hash, it might have an entry like:

54yg7(momlk32:password1

And I'd just have to search for it, not have to do any hashing and I'd find both our passwords out.

On the otherhand, if I use salts with the hash, the result would look more like this:

user:$salt$hash

me:$yg$sdf87dsfgbh^%$szdfds
you:$7z$powiuer9asd3ee343z^%

Practically this prevents me from computing a bunch of hashes beforehand and simply comparing the results to the stored hashes. You and I both still have the same weak password, but since a salt was used they have to be cracked independently.

It's not a big hurdle, but it's something.

There are probably some kind of pattern in all the difficult looking passwords that the cracker happens to find through cleaver combinations of dictionary attacks, leet speek decoding, common combinations and brute forcing. For instance Ev3rL@NRDX11090821 = Everland (a place) RDX (an explosive) and a number. w@chtw00rdLanimret! = Watch word Lanimret!

I would also have thought some of these were safe, though.

I'm on the list, but I figured I would be - it was medium-strength password at best. Of course I *never* kept a balance for any longer than it took to buy or sell, then I transferred immediately to my wallet or Dwolla where I did *not* use a medium-strength password.  ;D

I'm really wondering how they got some of the passwords now because my brothers account is in the list but mine is not. We used the same password....

Sweet! I'm not there! I used an 8-character long password with uppercase, lowercase, and numbers. Foolishly, I set other bitcoin-related passwords to the same one. As soon as I saw the news, I changed every site to a different 15-character long password with uppercase, lowercase, numbers, and symbols. Now I should apply this to RL...

Since it is extremely unlikely that all 60000 passwords were the same, you still have to brute force the rest.

If you assume a more reasonable 3000 passwords that are either identical or the same as the mail address for example, the difference between everything salted or not is only 60/57=5% more work.

Salting only (significantly) helps against rainbow tables.

Luckily mine wasn't cracked. Password WAS iamdana1qaz0p;/

Actually, "wachtwoord" means password in Dutch.

You do not understand it at all.  Read kjj's post for a more detailed explanation of how the salting works.

Mine was ridiculously easy to crack, yet isn't on the list.  I had just signed up to test the site right before the crack happened...  My password WAS literally a short dictionary word.  The difficulty of the password is obviously not the deciding factor here.

As someone said, this is just 3001 of 61017 accounts. About 1700 of all accounts were unsalted.

It is very obvious, if you do the maths, that this cannot have been brute-forced.
A 15 character mix has a pretty good length advantage, purely on the number of combinations. And since there seems to be quite a few of that kind and above, I'll base calculations on that.
The most basic mix of characters would be numbers and lowercase letters, for a total of 36 different possibilities. That gives a 15 char long password a total of 36^15 or 2.21*10^23 combinations.
Since the bitcoin network is a very good indicator of hashing power, if we translate the current capacity (12.571 Thash/s) to only 5870 cards, that gives 31292 @ 400 Mhash/s.
The best numbers my cards would give was 3.9 billion combinations/s each, which gives the bitcoin network a total power of 122567 billion hashes each second, or ~1.23*10^14.

Simple mathematics then gives: 2.21*10^23 comb. / 1.23*10^14 comb./s = 1.80*10^9 seconds, or 57.2 years.
To get anything realistic for brute-forcing, they would need 21.4 million 5870 cars, which brings it down to one month for a single 15 char length password with only numbers and lowercase letters.
One of the passwords was 24 letters like that, which would take longer than the calculated age of the universe using the bitcoin network!

Conclusion, this is either malware/virus, some form phishing attack or, though unlikely, hash collision.

Huh?
I don't think you got it.

Hashing a billion password candidates once with MD5 is no problem for today's computers.  To brute force 60000 unsalted passwords, you would just need one run through the candidates, making one hash for each candidate.  After one billion runs, you have cracked all passwords in your list of candidates.

To brute force 60000 salted passwords with unique salts, you need to run a more complex MD5 algorithm on all the salt + candidate combinations.  Even if you assume the same time for each test, it will take 60000 times longer to check all candidates against all hashes.  If the password is found for a candidate hash, you don't have to try the rest of the candidates for it, but you will probably not find as many passwords as you think.

Yes, a few people use their username or mail address as password.  Those would be cracked in seconds on anything with the computing power of a digital watch, no matter how they were hashed.  Don't worry about those.  Most of the passwords will likely not be among your candidates at all.

Anything under 20-30 characters is fair game. Use phrases with punctuation and special characters 20+ long or it will be cracked in this lifetime.

hmmm... wow, okay.

SO, I've learnt a valuable lesson on what to consider a secure password!

So evidently, even when salted, 8 characters containing letters, numbers and symbols is no-where near secure enough, even when it bares no relation to my username or email address...  in retrospect, something approaching 'leet speak' with perhaps obvious character replacement isn't the wisest choice.

SO you think its probably down to either malware or phising?

I'm not ruling it out but I'd be surprised if it was either.
I consider myself fairly savvy and know I haven't responded to any email phishing (I've certainly binned a few attempts) and have been super wary about watching URL's regarding anything to do with bitcoin. Also I'm not aware of any mac malware, but if anyone knows of any other than the Mac Defender thing I'd like to be enlightened...

Really keen to know exactly how this was done... even if its just to educate me on what to look for!

http://xkcd.com/792/ (http://xkcd.com/792/)

I don't think anyone is saying none of the entries could have come from cracking. Your mentioned 8 character password could easily have been the result of cracking, especially if it had any dictionary word as part of it.

The two things we can say for (pretty darn) sure:

 - Whatever cracking was done wasn't applied equally, perhaps they only focused on some entries

 - Some of the results are very, very unlikely to have come from cracking

For the ones that fit in the latter category, malware and phishing aren't the only possible answers, though they are probably the most likely. Other possibilities could be password reuse: if the person who published the cracked list ran another bitcoin site that he had set up to log all the passwords in the clear, he could have tried all of them against the hashes to start out. Or, the publisher could be the mt. gox hacker or another person who gained more access to mt. gox than we've been lead to believe - there are a number of ways you could capture the password before it's hashed as someone logged in. Either by changing the site software, modifying the dns/stealing the site certificate, or simply just pulling off a XSS attack that presented a bogus idled out/login page.

There are surely more possibilities than that, they just become even less likely. The only thing you can be (pretty) sure of is it's not hash cracking.

Only if the algorithm also includes stretching, which salting by itself does not necessarily do. If that is the case then you're right of course (I haven't downloaded the file to look at what format they use).

These are all relatively short.  I recommend passwords at least 45 characters long with no character being the same.
At least a sextillion years to get half way through cracking something like that.

Overkill anyone?  Paranoia is for those that survive.

How many minutes to search the room where you use the computer to find the place where you've written it down?

holey maloney!!
again ?!?!?

i'm running out of keyboard acrobatics

21390ßqweiop

Luckily I don't use MtGox  ;D

And is still fucking tell you, the most probable is that MtGox's recovery thingy was compromised too!

Any idea if using Unicode would help? As in starting your password with a Chinese character for example?

I know this list isn't all of the passwords that were cracked. My username/password are not on this list, and I had my account, and one of my bank accounts compromised (I keep under $3 in the balance, so I don't care about it).

I would also check https://shouldichangemypassword.com/ It correctly reports I've hade my password compromised once on June 19, 2011. I got an email from Chase about my account on June 20, so it seems pretty accurate.

Sorry, dude, you password really looks naive. I couldn't image my grandma chosing that.

Man, I seriously underestimated the power of GPU password crackers! I had an 11-character password which I thought was pretty good--b1Ackb0x3!1, and that was cracked.  I'm pretty sure I didn't succumb to any phishing attempts. Good thing I use 20+ characters for passphrases. :)

leetspeak is no good.



EDIT:
My password was also weak, but fortunately it wasn't cracked yet. (I would like to tell you what the password is like, but maybe I should not give hints.)

my password is not on the list. it was seven rather random letters/caps/numbers and I did not use it anywhere else.

my mtgox balance has been: 0 btc / 0 usd

I think I did not log on to mtgox for a while before the incident.

I have used the mtgox claim website just for the fun of it.

these salted hashes/passwords match, I checked it.

2754,$1$ul1uYRLP$OX0qFAuT9wu78ZdAApIeB.
2754,K7mmI8lAsn1o0q

10253,$1$Pdz6SDbH$X3Nz7dxhG6/bXCpcHPrlg1
10253,yT#g1Srm123

13434,$1$vWDRQAo.$kH6Rc9E6unn80S.UK0RHa/
13434,djcnbimil99332k

it would be a waste to crack these PWs. you could make plenty of coins instead.

the hackers will laugh their asses off if they read this thread and find everyone wondering. give us a hint already!

Enough people were stupid and used weak passwords, and the same passwords in mybitcoin.

You don't make that much money with mining!

Exactly.  If I can't remember it in my head, it's a useless password.

Depends on the purpose. For an encryption passphrase it makes sense. For a login at mtgox it doesn't.

the password above is not exactly l33tsp34k as i know it and if i had to configure a password cracker
config file to attempt leetspeak cracking styles... i would not have guessed to match his style up.

it seems someone actually ran a gpu(s) password cracker for days on end.. if i had to guess.
i wonder what the time line is for that file being first noticed versus the file being in the wild for
anyone to get? Two weeks? 5 days? hmm

according to the spreadsheet and crackrate bitcoin0918 posted above it would take more than 100years to crack K7mmI8lAsn1o0q on a mining rig of 4x 5870s.

and the chances to really find an account with money in it that (still) uses that password are rather low I think.


---correction---
probably that pw is more in the 5000years range on 4x 5870.

You are right. That would be an excellent method to reduce the amount of work. But random may not really
help unless it is spitting out some very very odd characters people normally never use and probably do not
even know how to type in the USA. Do they output characters like this? (which i found on a webpage about
a histogram of a rainbow table website).

 2 times the character “ž”
 2 times the character “®”
 2 times the character “¯”
 2 times the character “»”
 2 times the character “Ø”

 ::) How long would it take for our total mining power to bruteforce that 60,000 list?

No, that's bullshit. That's the whole point I am trying to make here for weeks now. You should not assume that the attacker is stupid, if you want security.

Dictionary attack does not mean that the cracker uses the Oxford dictionary for English. They have password dictionaries, they are generated for that purpose and include much more than correctly spelled oxford words. And the tools can vary the words from the dictionary while testing by replacing letters by similar looking numbers and special chars.

Fact is: Your password was cracked within' a few days.

I would be using some of those fancy Unicode characters from some time now if I wasn't afraid that applications weren't able to handle them properly, thus locking myself out of websites. Coping with Unicode is hard.

Off the top of my head, and easily type'able with my actual keyboard setup/layout: — – « » ß þ Þ œ Œ æ Æ ø Ø …

With ASCII alone you have about 95 characters, that makes 6.5 bits of randomness per character.

If you have US international keyboard layout, you can make the following with the right ALT key:

with shift even more:

unfortunately, I was cracked, and lost 40 BTC...

quite a long time.

I calculated this one alone to take more than half a year: K7mmI8lAsn1o0q

well, a little shorter with network speed rising like crazy

(data from posts above and bitcoinwatch)

There were other 8600 passwords from the database posted on Twitter...

Link?

To crack mine in a year, if you assume lower letters only and know the two special characters (26+2), you need 161.6 THashes/sec.

After I tell you the exact set of characters, you still need 4.9 GHashes/sec for a year.




And I consider this one of my weakest passwords. :)

yes, my password was cracked but i was just testing mtgox with no intention of trading at that time, so it was very weak.

I asked it if the following passwords had been compromised and it told me they were safe.

- password
- password1
- password123
- p@ssw0rd
- P@ssw0rd
- love
- hackers
- superman

Yes, and Lanimret is terminal backwards.
Using an advanced dictionary attack that also takes in account the use of symbols and numbers as substitutes for words, passwords like that are easy to crack using multiple GPUs.

What you need to use is completely random, non-repeating ASCII characters that make zero logical sense.
Here I would agree with Vladimir; If you can remember your password then you're doing it wrong.

+1

It depends.   IIRC in the broadcast Mt. Gox mentioned that some of the older accounts were MD5 unsalted.  In which case leetspeek pass isn't very good.  Yours interestingly enough was salted.
IMHO this was simply bad luck in one of two senses:

i) Your password happened to be in some wordlist or is a simple permute of some worklist
ii) They started multiple crackers bruting specific keyspaces and yours was close to whatever the startpoint was for 11 char passwords.


By contrast I ran oclHashcat on my 6990 for my password and it seemed to say it would take 4 years to exhaust the keyspace but hey if someone here wants to divert some of their mining software to the cause they're welcome to show me the error of my ways.  That would be pretty cool too....


Interesting side issue.   If your organization uses google as a mail system and they perform password synchronization.   They are shipping unsalted hashes to the big G (either SHA1 or MD5).  I don't know how many people have access to encrypted hashes at Google but the sample seems large enough that it's only a matter of time before someone sees the money making potential there.  (Password reset function + known gmail address + big ass hashing equipment = access to your Mt. Gox account).

my very simple password (6 numbers +username) wasn't in the list, so I believe that this list comes from phishing/key logging or something like that. I changed ALL my passwords to random characters after Mt.Gox got hacked (had planned it for a long time, but never got around to it), before this I was using the about 3 passwords for everything.


In https://shouldichangemypassword.com/  you should input the e-mail, not the password BUT they seem to have blacklisted the whole list from mtgox. I tried bulks of 10 from around the list, and they are all listed as "hacked"

That's the point of that url - they combined a bunch of lists of leaked account details - if your email is associated with any of them it tells you. Technically it's "has a hash of my password from a site been released publicly" it doesn't care whether the hash has been cracked or not, and rightly so.

My password was NOT cracked.

My password consisted of 18 characters, of which only 9 alphabetical and of which 3 were capitals.
The rest consisted of 3 randomly chosen numerical characters and 6 non-alphanumerical characters.

The mtgox website wrote after 'the incident' that accounts with 'sufficiently complex passwords' would be re-instated automatically.
Well, that didn't happen. I had to reclaim my account, got a new password. And it worked for 1 day.
Now my password is invalidated and mtgox does not reply to my requests for a new password:
If I go through the "password forgotten" procedure at login, it says it has sent a new password to my email, but non ever arrived.
Now my IP is even blocked 'due to too many failed login attempts'.

There are BTCs and USDs in my account there and I am getting really pissed!

I did exactly the same, I also wanted to do it all the time.



My MtGox password was different from any other fortunately except this very forum. But it has a little similarity with my standard passwords, so I fear that people might crack those more easily.