Posted by:
admin
14 years, 6 months ago
Symantec has a blog post about a 17GB flat file of stolen game credentials they have analyzed. The file included 44 million sets of stolen usernames and passwords for at least 18 gaming websites. The entire post is interesting and worth a read, in particular for how an attacker can use a botnet to validate the credentials and thereby increase their value.
My take-aways: At least 18 sites were targeted, but only 4 are listed. They should all be listed so users can change their passwords.
Aion, a game from NCSoft, is listed having 60,000 stolen credentials worth $150-1420. I haven't found recent numbers for the sales of Aion, but according to this article in the Korea Times, sales were at 700,000 by the end of Q3 and expected to be 1,000,000 by the end of the 2009. If they kept adding 300,000 users a quarter, they would have about 1.6 million users. This means that 3.75% of their userbase is in just this one file. They may not seem like much, but according to the company, things are bad and they are at war:
In the game industry, we have also seen an increase in attacks by third parties in an attempt to steal your account information by any means necessary, including phishing, obtaining passwords from third party sites/systems, and using account information provided by those engaged in power-leveling services and other prohibited activities. Recently, the number of these attacks has risen dramatically. As a result, our game support queues have drastically increased, with thousands of support tickets from players who have lost access to their game accounts and are suffering extended wait times for help. Our game servers, account databases, and support sites are under constant attack and being probed for any vulnerability. It’s a war that by no means is over.
So, you can estimate the real-world value of the stolen virtual identities, but only NCSoft knows their cost of using static passwords. But for the sake of argument, let's say 60,000 people call the helpdesk. At say, $20 per call (which is probably generous for a call where the user's credentials have been stolen) that would be $1,200,000 for that batch. What we don't know iswhat the 'batch' represents in annualized costs. But there is at least anecdotal evidence that account fraud can cost more. That it can cost the entire lifetime value of a customer:
They were not very helpful. I explained the situation and tendered that while I was not actually subscribing at the moment it was not as if I hadn't quit and come back before, and such a return would be far less likely if my characters had been scattered, stripped and left picked clean. The guy's major contribution was to send me an e-mail to various support articles which basically were "computer safety for dummies," as well as a webform to initiate an inquiry and request a repair of the damage. Not that he could put in that request or anything, being a blizzard employee. That 300 meg patch was still coming, so I went ahead and did that.
By the time the patch was done, "Account Management" had locked my account and scrambled my password, due to "character interaction with another account known to be in use by someone intending to exploit WoW's systems." If I wanted my account back, I could fill out yet another form and fax it to them to start the process. By this point, my supply of give-a-shit had run out. I'm content to let it just stay locked forever. It certainly seems blizzard is content as well, and with over 10 million paying junkies, it's entirely understandable (though not laudable) that they've become complacent and apathetic toward each individual subscriber. They don't need you, they have 9.999 million more just like you.
Share on Twitter Share on Facebook
Recent Posts
- Blast-RADIUS attack
- The latest WiKID version includes an SBOM
- WiKID 6 is released!
- Log4j CVE-2021-44228
- Questions about 2FA for AD admins
Archive
2024
2022
- December (1)
2021
2019
2018
2017
2016
2015
2014
- December (2)
- November (3)
- October (3)
- September (5)
- August (4)
- July (5)
- June (5)
- May (2)
- April (2)
- March (2)
- February (3)
- January (1)
2013
2012
- December (1)
- November (1)
- October (5)
- September (1)
- August (1)
- June (2)
- May (2)
- April (1)
- March (2)
- February (3)
- January (1)
2011
2010
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- June (3)
- May (3)
- April (1)
- March (1)
- February (6)
- January (3)
2009
- December (4)
- November (1)
- October (3)
- September (3)
- August (2)
- July (5)
- June (6)
- May (8)
- April (7)
- March (6)
- February (4)
- January (427)
2008
- December (1)
Categories
- PCI-DSS (2)
- Two-factor authentication (3)
Tags
- wireless-cellular-mobile-devices (7)
- Two-factor authentication (10)
- Wireless, cellular, mobile devices (6)
- NPS (1)
- Phishing and Fraud (111)
- Active Directory (1)
- pam-radius (3)
- privileged access (2)
- Cloud Security (10)
- Mutual Authentication (60)
- Web Application Authentication (1)
- Authentication Attacks (99)
- pci (50)
- Security and Economics (97)
- WiKID (133)
- pam (2)
- VPN (1)
- Installation (2)
- RADIUS Server (1)
- Open Source (64)
- Tutorial (2)
- Strong Authentication (35)
- Information Security (137)
- Transaction Authentication (13)
- Miscellaneous (100)
- Linux (2)
- transaction-authentication (6)
- Two Factor Authentication (254)