Quote from: kmahesh on January 02, 2014, 07:46:10 AM

undeadbitcoiner: Let me clarify..

1. I had 2FA enabled on my bitstamp account
2. I did not receive any trade confirmation email...the thief was an insider (bitstamp)...look at my original post, the thief logged in...placed a limit order AND THEN changed password

nefron: My guess is as good as yours...the thief perhaps knew there was money deposited in my account & quickly decamped with bitcoins.

Yes Microsoft does provide IP's and I have asked for details including mails received/ deleted.

Quote from: undeadbitcoiner on January 02, 2014, 01:35:30 AM

Quote

2013-12-27 17:26:07 96.47.226.22 Logged in
2013-12-27 10:32:48 122.172.192.2 Logged in

Quote

If seed in server database got compromised, then every ones account in Bitstamp is also compromised, not only his account & so far no one complained except him.

That is what the proof of his account was either not secured (2FA Enabled but not was Activated) and his Email also was either in control of others or 2FA was not enabled.
We doing trade of just 100$ we use to activate 2FA and till now everything is well and every time we are been notified how could he invest 1500$ and just leave it its just like you have a Diamond Necklace you keep in your room, you are staying in your leaving room so windows of your room are open so anyone could hookup and take it out so latter in night you cant say that I was in my house but still my Necklace lost.
When you have 1500$ worth necklace in you room do you leave you window open? of course not. In such case you would be blamed not that thief.

Bitstamp uses Google Authenticator for 2F via SMS. That means you need to register your cell phone. When you try to login, you will receive a 6 digit code on your phone. Without entering this code, you cannot login.

While I can understand you are upset, there is no point in blaming Bitstamp. It's clear your email was compromised, and you did not have 2F enabled.

Bitstamp has a very good reputation, and you sound more and more unreasonable when you blame Bitstamp.