Town of Salem Game Forums

Multiuniverse wrote:So why don't you guys change to use a better hashing software?

Switching to a different hash algorithm retroactively is hard because BMG shouldn't and hopefully don't have access to the unencrypted passwords. Maybe new passwords.

Oh, can't they just get a different hash algorithm and require users to put new passwords/the same password and confirm this is their account via email?

Achilles wrote:

Technetium wrote:

Wikipedia article on MD5 hash wrote:The weaknesses of MD5 have been exploited in the field, most infamously by the Flame malware in 2012. The CMU Software Engineering Institute considers MD5 essentially "cryptographically broken and unsuitable for further use".

So...if the hashing isn't doing its job...why is that hashing method in use?

Because we’re terrible developers obviously

I'm sorry, but that is quite possibly the worst reply any dev could have possibly said at that moment.

I get it that the office may be stressed out over this issue and the community, aren't quite on your side, but the last thing anyone working for BMG should do is make a comment like that.

The IP and Email part are still pretty concerning..

This is probably a stupid idea, but what would prevent them from, say, using a new hash algorithm on top of the old one, re-hash all the existing passwords, and have login run the two hashes in sequence?

So currently it uses what we'll call Hash A.
When a password is input on login, it goes plaintext>Hash A and is checked against the stored password, already converted plaintext>Hash A before storing.

What I'm thinking, is, they convert all the stored passwords with another hash, we'll call it B, and have the login setup hash the passwords twice to match, so it goes plaintext>Hash A>Hash B.

Now, I figure there's very likely some reason why this wouldn't work, so if there is, could someone explain what that reason is?

Thank you for letting us know BMG. However I feel that you should increase the security of the game in general, as we recently had the bot attacks, and now we have this. I’d really suggest upgrading security for the entire game.

Do you plan on, or are looking into who did this? I would really like to know who did this so that you can bring them to court. An attack this big is probably carried out by some very vengeful people, therefore I suspect that the botters could be behind this.

Jackparrot wrote:]
Do you plan on, or are looking into who did this? I would really like to know who did this so that you can bring them to court. An attack this big is probably carried out by some very vengeful people, therefore I suspect that the botters could be behind this.

Not to ruin your dreams of an evil mastermind targeting bmg only for some absurd reason (like botters) but usually hackers scan for vulnerable websites with a large userbase through various search engines and programs. Then they compromise said servers to steal information (especially billing information or email+password). This login data can then be used on other sites that hold sensitive data and be used for either phishing (sextortion as an example) or directly stealing data from other sites with a valid login. It is a lot easier to target a small site rather than a large site and since people reuse passwords quite often then chances are the hackers can hit a jackpot by hacking a small site.

Also this attack is not that big if you believe what is written by dehashed. A rfi or lfi attack does not demand a lot to actually be successful with and it is quick to run away from since the server itself is doing the compromising by handling files to users it shouldn't give them to.

Just let BMG handle it in peace, No one knows if BMG even has control of the hashing of the passwords... It could easily have been a phpBB vulnerability since those have existed in the past... It's amazing how everyone in the ToS community is suddenly an experienced Software Engineer and is so ready to put BMG to shame.

Yeah it happened, Yeah it sucks. Yeah they could have told us sooner. But so what, they were on a 5 day holiday when most software companies take 10 days during this time of the year. Give them a break and stop crying about it. Crying about it doesn't help the situation or speed up any process.

Data breaches are a reality in this day and age. Equifax actively tried to cover up their data breach for almost 3 months. BMG was on holiday for 5 days and didn't see a couple emails, relax guys... It's no big conspiracy

For now, since everyone is so worried:
- Change your ToS password to something secure
- If you used the same password somewhere else, Change that password
- Setup 2FA on important accounts and your e-mail

It's always best, regardless, to change your password with any kind of data breach. Always play the safe card.

So much crying going on here. Dont worry, nobody is gonna steal your bad credit.

Technetium wrote:This is probably a stupid idea, but what would prevent them from, say, using a new hash algorithm on top of the old one, re-hash all the existing passwords, and have login run the two hashes in sequence?

So currently it uses what we'll call Hash A.
When a password is input on login, it goes plaintext>Hash A and is checked against the stored password, already converted plaintext>Hash A before storing.

What I'm thinking, is, they convert all the stored passwords with another hash, we'll call it B, and have the login setup hash the passwords twice to match, so it goes plaintext>Hash A>Hash B.

Now, I figure there's very likely some reason why this wouldn't work, so if there is, could someone explain what that reason is?

tl;dr is that doing a hash twice doesn't necessarily make it more secure than doing a hash once.
It's more complicated than that, like it would sort of make brute forcing a password harder, but you'd still be relying on MD5.
Like the problem isn't necessarily that somebody gets your password. The problem could very well be that somebody gets a seemingly random string of characters that just so happens to hash to the same value as your password.

I would recommend waiting until BMG fixes the issue to change your password on this site, as your new password could still be compromised until BMG fixes the vulnerability.

Deagler wrote:Just let BMG handle it in peace, No one knows if BMG even has control of the hashing of the passwords... It could easily have been a phpBB vulnerability since those have existed in the past... It's amazing how everyone in the ToS community is suddenly an experienced Software Engineer and is so ready to put BMG to shame.

Yeah it happened, Yeah it sucks. Yeah they could have told us sooner. But so what, they were on a 5 day holiday when most software companies take 10 days during this time of the year. Give them a break and stop crying about it. Crying about it doesn't help the situation or speed up any process.

Data breaches are a reality in this day and age. Equifax actively tried to cover up their data breach for almost 3 months. BMG was on holiday for 5 days and didn't see a couple emails, relax guys... It's no big conspiracy

For now, since everyone is so worried:
- Change your ToS password to something secure
- If you used the same password somewhere else, Change that password
- Setup 2FA on important accounts and your e-mail

Deagler, perhaps it would help if you read the article by dehashed (https://blog.dehashed.com/town-of-salem ... es-hacked/). They clearly state having called and received answer on December 28th. Their hashing algorithm is old and outdated, declared unsafe by various people in tech. All these things are not complicated and if you have the slightest interest in security as a hobby then you can understand it with a bit of reading. Mostly, people are unhappy with how the breach is handled, at least that is what I am, because breaches happen and sometimes in the weirdest ways. I bet if this really was a LFI or RFI attack then it was some weird form or file upload that accepted the attack. Easily forgetable and totally understandable, especially for a team of their size. However when they don't react to calls of a security site then it is a problem. No matter a vacation someone should always keep a little tab on logs and so on. Swap the duty around each day or something but just keep an eye out.

kristian818 wrote:

Deagler wrote:Just let BMG handle it in peace, No one knows if BMG even has control of the hashing of the passwords... It could easily have been a phpBB vulnerability since those have existed in the past... It's amazing how everyone in the ToS community is suddenly an experienced Software Engineer and is so ready to put BMG to shame.

Yeah it happened, Yeah it sucks. Yeah they could have told us sooner. But so what, they were on a 5 day holiday when most software companies take 10 days during this time of the year. Give them a break and stop crying about it. Crying about it doesn't help the situation or speed up any process.

Data breaches are a reality in this day and age. Equifax actively tried to cover up their data breach for almost 3 months. BMG was on holiday for 5 days and didn't see a couple emails, relax guys... It's no big conspiracy

For now, since everyone is so worried:
- Change your ToS password to something secure
- If you used the same password somewhere else, Change that password
- Setup 2FA on important accounts and your e-mail

Deagler, perhaps it would help if you read the article by dehashed (https://blog.dehashed.com/town-of-salem ... es-hacked/). They clearly state having called and received answer on December 28th. Their hashing algorithm is old and outdated, declared unsafe by various people in tech. All these things are not complicated and if you have the slightest interest in security as a hobby then you can understand it with a bit of reading. Mostly, people are unhappy with how the breach is handled, at least that is what I am, because breaches happen and sometimes in the weirdest ways. I bet if this really was a LFI or RFI attack then it was some weird form or file upload that accepted the attack. Easily forgetable and totally understandable, especially for a team of their size. However when they don't react to calls of a security site then it is a problem. No matter a vacation someone should always keep a little tab on logs and so on. Swap the duty around each day or something but just keep an eye out.

I've read the article and I actually have a professional interest in security (I work as a solutions architect&dev) so I do fully understand the implications of the breach. I don't really know why there is a mix of phpass(phpBB's newer stronger hashing algorithm) and MD5(phpBB3 fallback) hashes, but regardless the hashes found would imply that BMG didn't make a conscious decision to choose a weaker unsafe hashing algorithm and that it's controlled by phpBB. I'm sure they are well aware of the downfalls of MD5 themselves, I don't know why everyone is doubting them. Also in regards to the LFI/RFI attack, we don't even know if it's BMG's direct fault. Could just as easily be a phpBB vulnerability or a third-party plugin...

Also, Yeah they made contact and that's why I said they could have told us sooner in my previous reply. But everyone is ignoring that the first thing they did do was reach out to Rackspace to try and ensure they could fix the problem ASAP. As far as I'm concerned, BMG is doing their jobs and I'm sure they've already learnt a couple lessons from this.

Everyone just has to chill and let them handle it, No one is really helping by crying about them...

TheGarner wrote:Anyway to delete an account? Haven’t used this for years and only remembered it due to the news of the breach.

viewtopic.php?f=38&t=38940

literally the second post in the faq subforum

https://haveibeenpwned.com/

if you want to check

ChubbyMooshroom9 wrote:https://haveibeenpwned.com/

if you want to check

i am not in there, do i consider myself as safe?

Royee wrote:

ChubbyMooshroom9 wrote:https://haveibeenpwned.com/

if you want to check

i am not in there, do i consider myself as safe?

It's pretty much impossible not to be on there as the whole database was leaked.
Unless you changed your e-mail recently or you want to imply that wasn't the whole database, I guess you made an error.

Bodhrak wrote:

Royee wrote:

ChubbyMooshroom9 wrote:https://haveibeenpwned.com/

if you want to check

i am not in there, do i consider myself as safe?

It's pretty much impossible not to be on there as the whole database was leaked.
Unless you changed your e-mail recently or you want to imply that wasn't the whole database, I guess you made an error.

It is updated. I am affected. Damn i moved email address because i was leaked in 3 sites.

So what should we do about it if we have been pwned?

Chemist1422 wrote:So what should we do about it if we have been pwned?

I am joining the question too.
What do we do besides changing the password?

Royee wrote:

Chemist1422 wrote:So what should we do about it if we have been pwned?

I am joining the question too.
What do we do besides changing the password?

If you use the password elsewhere (first off don't do that), change that too. No confirmation afaik that the breach is fixed so be ready to change it again if needed. That's pretty much it.

@Achilles - any idea if the breach has in fact been fixed?

Achilles wrote:

Technetium wrote:

Wikipedia article on MD5 hash wrote:The weaknesses of MD5 have been exploited in the field, most infamously by the Flame malware in 2012. The CMU Software Engineering Institute considers MD5 essentially "cryptographically broken and unsuitable for further use".

So...if the hashing isn't doing its job...why is that hashing method in use?

Because we’re terrible developers obviously

Wow can we ban him for being toxic pls? Keep this community clean please.

Bodhrak wrote:

Royee wrote:

ChubbyMooshroom9 wrote:https://haveibeenpwned.com/

if you want to check

i am not in there, do i consider myself as safe?

It's pretty much impossible not to be on there as the whole database was leaked.
Unless you changed your e-mail recently or you want to imply that wasn't the whole database, I guess you made an error.

mfw my alts are fine but not my main

not like it matters lol the password is different

Someone tried to access my account 13 hours ago from El Limón, Aragua, Venezuela, with IP 190.38.37.97, but Google stopped them