My account got hacked after BATTLE.NET

#0 - Oct. 30, 2009, 11:15 p.m.
Blizzard Post
Ok, so I've been reading all the horror stories and what not about people getting hacked after converting to battle.net. I've been doing nothing but saying that it's the users fault for nothing securing themselves well enough. Well what a reality slap to the face. I'm a security analyst for a local company and I know how to secure my network and machine. Something is not right here...I've never had any threats to my machine and all of a sudden I convert to battle.net and 48 hours later my account gets hacked? NO TRACE OF ANY malicious software on my network. NOTHING...And I use symantec endpoint and server software. I have probably 5 seperate layers of defense on my network. From hardware to software. Something is not right. And save yourself some time, I know the standard procedures for checking for crap on my machine. Hell, I'll go a step forward and have PACKET logs for specific types of requests.


EDIT, sorry I meant to post on my main (which I reply with further down)
#58 - Oct. 31, 2009, 12:51 a.m.
Blizzard Post
Q u o t e:
a copy a paste script? LOLORZCOPTORS he made a funny!

Actually, do be quite frank, a simple copy and paste script would probably do the same thing considering that if a key logger were to try to log it, it would pick up only [CTRL] P when you paste it...But nah...


No. I'm not in a position to judge your professional credentials, so I won't. I will simply allow for the possibility that you (like any of us) do not know everything, as the above quote avidly illustrates.

Moving forward, it appears that you've posted on two separate accounts, and yet these accounts are not registered to the same email address and real name. Nor indeed, the same state.

Neither of these accounts appears to have been compromised.

May I ask for the name and realm of a character that is on an account that actually has been compromised?
#61 - Oct. 31, 2009, 12:58 a.m.
Blizzard Post
Q u o t e:
Yes, although I don't want to simply reply to you the information...How else can I send it to you?


You can post the name and realm of any character on the account (it need not be a main) and edit the information out of the post immediately - I'll still be able to see it.

Alternatively, you could send it to me via email at [email protected] with ATTN: Malkorix in the title.
#64 - Oct. 31, 2009, 1:17 a.m.
Blizzard Post
Q u o t e:
nt

Cool, well thanks for the BLUE attention.


You're welcome.

I can see that you've logged in from a few different locations since you merged your account into Battle.net. It might be wise to consider the possibility that not all of those systems was absolutely pristine at the time you made use of it =(. The possibility always exists of a cunningly constructed phishing attempt as well. It would not be the first time someone both smart and savvy was taken in by an elaborate scam.

Regardless, fault is unimportant. I want to reassure you that Battle.net is secure - or it would literally be impossible to secure an account =/.

What is important is that you ensure that the system you play from is secure and that your account name and password remain absolutely secure and confidential. One of the benefits of Battle.net is that you can change certain pieces of crucial information to help prevent a potential compromiser from regaining access.

I'm pleased to see that you've submitted an in-game petition to report this compromise situation, and our staff will be happy to do all they can to assist as soon as possible.

For more information on how the account recovery process works, you might find the following thread informative:

** Account Compromise Info Center **
http://forums.worldofwarcraft.com/thread.html?topicId=14318909866&sid=1

An Authenticator can go a very long way toward helping to keep your account secure as well:

Blizzard Authenticator
http://us.blizzard.com/support/article.xml?articleId=24660
http://us.blizzard.com/store/search.xml?q=authenticator

Mobile Authenticator
http://us.blizzard.com/support/article.xml?articleId=26109
#68 - Oct. 31, 2009, 2:12 a.m.
Blizzard Post
Q u o t e:


Let it rest, we already determined that wasn't the case.


Actually, on that note, I'm going to go ahead and lock up this thread. I think everything that needs to be said has been said on the subject.