Quote from: Peanutbutterpolka on July 01, 2017, 05:21:21 AM

At the end of may there was a polo ddos attack, the official story was too many new users. That is the time my account was hacked.

I really feel that the attacker got a list of non 2fa accounts and just started going alphabetical. This other user had the exact same thing happen, A full fucking month later. Coincidence that both accounts started with an A?

Doubt it.

Polo was and is still compromised.

Quote from: Peanutbutterpolka on June 30, 2017, 05:33:20 PM

My working theory is that the attackers hacked polo, got a list of non 2fa, then went manually through them alphabetical.

The hacker has been able to do this for atleast a month and a half.

The hacker drained my account nearly exactly like yours by setting counter trades.

Yes polo should be able to track this, have they made any effort to call in authorities? I doubt it.

Hence, I believe they should be opened to a lawsuit.

Quote from: arsat14 on June 29, 2017, 08:37:16 AM

Quote from: Peanutbutterpolka on June 28, 2017, 08:08:07 PM

In my case ,at the end of May, I booted fresh from a livelinux CD and used a new email address. The only thing I did different was I had to contact their help desk.
So I'm not sure how my account was compromised then.

Also my compromised account started with an A, so I assume hacker got access to polo database an went alphabetical.

Op did you previously contact the polo help desk for anything.
Also what letter did your account begin with?

My Account started with A as well (we may be on to something here)!! but not, I did not contact their help desk at all before that,
Did you see any unauthorized activity on your account?

Pretty sure that the hackers got the lists of both accounts with 2fa or non 2fa but just can't access the 2fa enabled accounts so the hackers just went through the unenabled ones.
Big chances the hackers themselves have the access to the database because phishing account especially an exchanger ones is kinda difficult.