This can't be serious..

Q u o t e:

i'm not being obtuse <removed>, the billing gm was literally logging into my account over and over because i had to merge accounts to get my real name changed on my account

unless the gm is <removed>, there is no reason why i COULD be hacked while on the phone with a billing representative

red text: i'm going to bump this thread when i'm done waiting 47 hours on hold again so you can recognize blizzard made a mistake and i wasn't hacked - but since you work for blizz that's np you already know that

Woah, hang on a second.

Let's everyone please slow down, so we can figure out what was occurring here. You were solely calling in to request assistance merging Battle.net accounts, is that correct? Was there ever any mention of Authenticators during your conversation with our staff member?

Q u o t e:
All we have to go on, Sup, is what you have provided us. From what you have told us, this is the only conclusion. Seeing as Malkorix is here, he might be able to shed some light on things.

It does seem possible that something more unusual could be occurring here. Let's all please take a breath, and then we'll try to get to the bottom of what might have occurred. While we do our best to provide top quality service, our staff are only human and it is possible that some kind of error occurred.

I'd like to figure out what happened so that the right steps can be taken going forward. There's no need for hostility.

Please don't derail the thread. If the Battle.net account was merged, then our staff made the necessary verifications.

Q u o t e:
I was calling because my FIRST AND LAST name on the Account were not mine. The account I merged with (also my first and last name; I wanted the ability to transfer between accounts) had an authenticator previously that is no longer active - i still even have the core hound pup pet

i received no emails on either of the two accounts, one of them my last email was "welcome to the arena tournament" - so I literally couldn't have been hacked.. i only see this as a mistake on billings part, which I know it will be (none of my toons have since logged in, been transferred, and I changed my password just for <removed> and giggles) the only sad thing is the combined 4 hours i'm going to have to wait to speak to them twice.

Thanks for the information. Do you believe that the Authenticator was accidentally activated on your Battle.net account during the merging process? If so, do you have access to that physical token?

Q u o t e:
He's asking if you have the actual authenticator that you mentioned used to be associated with a BNet account you used.

Yar.

Q u o t e:
What Mal is asking is do you think that, in the process of merging these accounts, that somehow the Authenticator was reactivated. And if so, do you have the keyfob. I'm assuming he is going to want the serial number off of it, or recommend calling Billing with that serial number.


Edit: Beat by everyone else...including blue. *shakesfist*

Or, use it to manually disable the Authenticator. I am actually assuming that the actual Authenticator itself isn't available, but I thought it appropriate to at least ask before we moved on to other options.

If the actual Authenticator isn't available, is the serial number for that device available?

Q u o t e:
nope, sorry, blizzard even recognizes it was human error

I recognized that it is possible that human error could play a role, not that it is necessarily what occurred in this case. It's not at all become clear what has occurred in this case yet, actually.

Q u o t e:
also: awesome job on billing, chick tells me she's going to email me and that if i find the cd keys to email her back.. but the positive side? SHE NEVER EMAILS ME LOL YES WAITING 2 HOURS IN QUEUE AGAIN

The mail in question was indeed sent - I'm looking at a duplicate of it right now. You may need to check the junk mail folder of the registered email address in question. Also, it should be possible to handle this situation via email by filling out a Terms of Use form and confirming your identity.

Here's a link:

Battle.net Terms of Use Form
http://us.blizzard.com/support/article.xml?locale=en_US&articleId=26361

You may not like Supz posting style, but I would like to ask, again, that everyone step back, take a breath and allow the thread to continue without conflict.

To paraphrase, "If you haven't got anything nice to say, don't say nothin' at all."

Q u o t e:
it was a mistake on blizzard's part.. they admitted it

Actually, we just hammered out what happened.

This is the same Authenticator - both accounts were protected by the same device. You did indeed remove it from one account back in May. It was never removed from the account that was merged into your Battle.net account though - when that occurred, it effectively began applying to the account again. So, in the future, it's probably a good idea to ensure that you keep track of which accounts are or are not Authenticator protected.

At this point, however, it's still necessary to take the necessary steps to verify your identity and ensure that it is removed appropriately, as I listed earlier.

As this thread has attracted some negative attention, I'm going to lock it up now. I wish you luck on a swift resolution.