Blizzard Sued over Battle.net Authentication


Recommended Posts

Dumb. #1 It's optional and not mandatory.

It is mandatory. Blizzard security is not first class. In fact this is probably one of the less secure online service around.

I got my battle.net account hacked even if i was using a perfectly secure password 10 random digits (numbers and letters with a cap and a special) that was unique. I did not have any keyloggers on my system and did not fall for any scam or phishing. All the addons was clean addons millions of people use like dbm and i downloaded them using my 2nd PC. Never bought money i farm my own things. The PC was clean as it is also my work PC and i never use it to browse sites that are not offcial or forums (like neowin) or to check hotmail or gmail. This is my work PC and it is used to work only (check my work emails, browse msdn and such) and also play games since it is a good machine. I use my 2nd less powerful PC to browse the web and do not so much secure things. I'm 100% sure the breach came from Blizzard side.

I never got hacked ever. Not before not after. Hotmail never hacked. Gmail never hacked. Guild Wars 1 and 2 never hacked. Live never hacked. I think most people using battle.net without an auth got hacked at least once.

I will honestly not shed a tear for Activision Blizzard after faction change. They got greedy and i would call this karma. Well deserved class action lawsuit.

i was forced to use one by blizzard after my account was comprimised or they wouldnt reinstate my account, and hell it was thier fault my account was comprimised not mine

I can't wait to hear your explanation as to how its Blizzard's fault your account was compromised.

I never got hacked ever. Not before not after. Hotmail never hacked. Gmail never hacked. Guild Wars 1 and 2 never hacked. Live never hacked. I think most people using battle.net without an auth got hacked at least once.

Yeah, not even close.

Since Blizzard doesn't even make passwords case sensitive, it opens everyone's accounts up to being hacked rather easily. Doesn't take long for people to brute force a password, especially when you don't have to do capital letters anywhere.

Blizzard has posted time and time agian, if you don't have an Authenticator, you are compromising your account. That if you do get hacked, it will be harder to get anything back because you "Didn't take ALL the avenues to secure it."

Due to blizzard basically saying in the past that an Authenticator is needed to keep your account secure, they have opened themselves up for this.

Doesn't matter what you think, because the law doesn't work that way. There is merit to this suit, although in reality, it is stupid.

capitals doesn't necessarily make your password safer.

password_strength.png

Sure it does. It adds an extra layer of protection. You could have horseapplestaplebattery, or you could have HorseaPPlestaPLEbatterY, which would make it even more complex. It doesn't make sense to leave an option out that only helps strengthen something.

Not sure the lawsuit makes sense, unless the guy wants restitution for the $4 or so it costs to get the authenticator. For those almighty people here saying that the hacking is "Your fault!" not Blizzards, you may want to research the issue and see how many people with and without authenticators have been hacked. I myself was hacked, and had a very very good password for the account as well as an authenticator; now, before you say "well, it had to be your computer!", i give you some info about my pc and me. I am an IT manager who has worked for companies such as Symantec IT internal department, MessageLabs IT internal department and now a private Chemical plant, again internal IT deparment....so with all that in mind, i have made sure that my PC IS as secure and clean as possible, not only for a stupid game, but also to make sure information on my pc is not compromised.

I also ran wow clean, without addons etc, and any updates were all downloaded using the client....so when my account got hacked, i made sure to do before calling blizzard a full forensic analysis of my machine, including firewall logs, av scans, spyware scans, etc, etc, etc......what i found was that my computer was clean, and my account was hacked either directly from Blizzard or my isp had some issues with man in the middle attacks, and blizzards traffic encryption had or has been compromised (do not know which).

So, going back to the suit.....smart? maybe, depends what the person wants, if he wants restitution for the authenticator then sure, have blizzard refund his $4 or so...anything else is a joke, although having blizzard change some of their warnings or making them give out warnings when something does happen like getting hacked would be nice.

While many times it's the user's fault for being hacked, there are times when they truly did nothing wrong.

I have 2 WoW accounts for example, both with strong unique passwords not used anywhere else. My main one has an authenticator on it, and was never hacked. My old one however, despite not being in use anymore, didn't have an authenticator. 2 years of having not logged into that account, I receive an email that the account has been suspended. Not exactly sure what the hell they did to break into the account, as my password was strong, unique, and hadn't even been used for 2 years...

Same thing happened to a friend of mine with his Guild Wars account.

So yeah, I'm quite under the belief that if you don't have an authenticator, you will likely be hacked eventually. Doesn't matter if hasn't happened thus far, it's still possible, even if your account isn't in use.

---

Anyway, I'm definitely no fan of Blizzard these days. Still, I think this case is just straight baloney. :sleep2:

While many times it's the user's fault for being hacked, there are times when they truly did nothing wrong.

I have 2 WoW accounts for example, both with strong unique passwords not used anywhere else. My main one has an authenticator on it, and was never hacked. My old one however, despite not being in use anymore, didn't have an authenticator. 2 years of having not logged into that account, I receive an email that the account has been suspended. Not exactly sure what the hell they did to break into the account, as my password was strong, unique, and hadn't even been used for 2 years...

Same thing happened to a friend of mine with his Guild Wars account.

So yeah, I'm quite under the belief that if you don't have an authenticator, you will likely be hacked eventually. Doesn't matter if hasn't happened thus far, it's still possible, even if your account isn't in use.

---

Anyway, I'm definitely no fan of Blizzard these days. Still, I think this case is just straight baloney. :sleep2:

Are you sure those weren't phishing emails like the ones every gets regardless of if they even play the game?

Are you sure those weren't phishing emails like the ones every gets regardless of if they even play the game?

No, but I do get those as well. I never open them, and they're properly placed in the spam section of Gmail. I worked with Blizzard to have the account restored, simply for the fact that it was my account and I didn't want anyone using it for whatever malicious purposes. Also slapped the iOS authenticator on it for (free) added safety.

Sure it does. It adds an extra layer of protection. You could have horseapplestaplebattery, or you could have HorseaPPlestaPLEbatterY, which would make it even more complex. It doesn't make sense to leave an option out that only helps strengthen something.

But it only makes it more complex to remember.

Are you sure those weren't phishing emails like the ones every gets regardless of if they even play the game?

I know in my case it wasn't. I know which ones are real/fake but even then, for ANY link dealing with accounts, I always check to see if the link is actually valid. I've never had anything hacked before.

This is pretty common with WoW. Lots of people I've known that practice good computer security stopped playing WoW and then had their accounts hacked (they didn't have authenticators). Authenticators are pretty much a requirement now or you're guaranteed to get hacked...

Not by much. And the added security can only help.

Not really, there's a level where security peaks and there's not really a point in adding further security anyway, and it does make it significantly harder to remember when random stuff in the password is upper cased.

Personally my password isn't technically nearly as complex as the base password there. but in reality it's more secure and shorter and doesn't rely on any special cases, and I don't get hacked.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!