Quote from: vodic62 on April 26, 2014, 07:15:38 PM

Quote from: Alexiandar on April 26, 2014, 06:11:16 PM

Quote from: vodic62 on April 26, 2014, 04:52:24 PM

Quote from: MrTeal on April 26, 2014, 03:23:53 PM

Pool users should check their connections to Slush. I noticed with two miners that I hadn't submitted a share in the last ten minutes. My miners were showing that they were still connected to pool 0, but 46.28.205.80 instead of the normal address. There is talk on Eligius about a malicious player doing a man in the middle attack, it's worth reading up on.

I had this problem about 3 times in last few days. 15 minutes ago my both antminers were submitting work and nothing looked different, but for about one hour they were sending results somewhere else, because slush pool was reporting 0 shares. After reconnection everything is ok again... I really hate how many thieves are attracted around bitcoin.

It might be that the password is left to default, so it's the same password to all ants if it wasn't changed. I guess the 'thief' needs to find the IP and then log into that ant's account using the well known default password. Or maybe the other 2 pools weren't changed, so if Slush is down, it switches to the other default pool which was preset by Bitmain. Just a thought.

No it's not my case. I don't have default passwords and antminer was showing that he is submitting work to Slush pool. And my only failover pool in ant configuration is my bitcoin wallet a it wasn't used.

Following this as i was affected. It does not appear to be hardware specific. Im Running BFL hardware.