The password and the salt were released.
For example.
Lets say that your password is "Dog", and the server had a salt of "Cat".
When you log in, the server takes "Dog" joins it with "Cat" and then encrypts it like this "encrypt('DogCat');"
Which returns a long string of about 42 characters. It is impossible to take these 42 characters and work backwords.
So somebody decrypting your password would have to run the encryption method until they break it.
In the security world there are 2 methods of attack.
The first method is to simply check every dictionary word, which is extremly fast.
The second menthod is to brute force it. For example
encrypt('aCat');
encrypt('bCat');
encrypt('cCat');
until they get to your password. This shows how it is important to have a complex password like: saquq56r (randomly generated here:
Security Guide for Windows - Random Password Generator).
There are 2 other methods but they are ineffective in this situation (one is to use a lookup table called a rainbow table, which is where you create all the possibilities before hand, but as everybodies salt is unique it makes it pointless). The last one is to enter (the incorrect password) but a very long string of letters to force it to cause what is called a collision.(Great if you want to hack into the users account on MiniMins, useless if you want to log into something else)
The biggest issue of course with this is not that the MiniMins password was released after all what are you going to do after you log into MiniMins? But if the password is decrypted and becomes useful, that password may be common with other online accounts elsewhere.
Pierce