Valve Confirms Encrypted Credit Card Info May Have Been Swiped in Last Year's Steam Security Breach

Gabe Newell, head of Valve, has begun emailing Steam users today to let them know he and his company continue to investigate last year's security breach in which hackers vandalized Steam's forums. He also wants to give users a heads up that a backup file containing encrypted credit card details and other personal information was likely stolen.

The email in its entirety reads:
Dear Steam Users and Steam Forum Users:

We continue our investigation of last year's intrusion with the help of outside security experts. In my last note about this, I described how intruders had accessed our Steam database but we found no evidence that the intruders took information from that database. That is still the case.

Recently we learned that it is probable that the intruders obtained a copy of a backup file with information about Steam transactions between 2004 and 2008. This backup file contained user names, email addresses, encrypted billing addresses and encrypted credit card information. It did not include Steam passwords.

We do not have any evidence that the encrypted credit card numbers or billing addresses have been compromised. However as I said in November it's a good idea to watch your credit card activity and statements. And of course keeping Steam Guard on is a good idea as well.

We are still investigating and working with law enforcement authorities. Some state laws require a more formal notice of this incident so some of you will get that notice, but we wanted to update everyone with this new information now.

Gabe

When the breach occurred in November of last year, Gabe sent out a similar email saying intruders obtained access to a Steam database containing personal and financial information, but that it was all encrypted and there was no evidence any of it was taken. Now we're finding out otherwise, three months after the fact.

If you're a Steam user, be sure to continue to monitor your financial records closely.
Via:  Vavle

blog comments powered by Disqus