Post
Topic
Board Service Discussion
Re: My wallet on blockchain.info hacked even by e-mail comfirmation code !!!!!!
by
byt411
on 06/08/2014, 05:00:13 UTC
More detaile ?

Are you serious ?


This is not the first time someone hacked in the site , just search google , before me there were many people .

https://bitcointalk.org/index.php?topic=188639.0
https://bitcointalk.org/index.php?topic=588644.0
https://bitcointalk.org/index.php?topic=120865.0

When they said we hacked i tought they did not keep security issues but today i reliaze they was right and something is strange !!!!!

Maybe the site itself has a keylogger !!!!!!

I'm using last update Smart security NOD32 and malewarebytes permium !!!!!!!

The stolen BTCs it's not our fault security it's about blockchain.info , i guess the site steals bitoins itself and there aren't any hacker . if there was a hacker Maybe he was very very high IQ and guess my passwrod Smiley))))))

I don't want doubt with you guys and wanna go to bed

Tommorrow this will happen for you and you will understand why the site is not Okay for your bitcoins but that day is late for understand !!!!!

Its your fault and your fault only. Antiviruses don't detect everything. You should stop downloading crap and visiting weird sites.
Also,
His blockchain.info alias matches his forum name, and it has no 2-factor authentication.  Attacker grabs the wallet and performs an offline brute force attack.  Guessing the password wasn't very good either. 

You're right, my password was lazy. Lesson learned.

Have you enabled 2FA?
Have you received some phishing emails and clicked the link?
Have you download some "strange" programs which may contain keylogger?

no,no.and no!


So you don't use 2FA?

I tried out my MtGox YubiKey on the blockchain wallet service, and I noticed the OTP's that it generates are REUSABLE. It seems Blockchain.info is only looking at the first few letters of the OTP, as they are static, you can actually change the end of the OTP and the website will still accept it.

Doesn't sound secure at all to me and is definitely something that needs to be addressed. This is not 2-factor authentication.

As you see, in all cases it was the users' own fault. This case its no different, its your own fault, stop blaming others for your ridiculous mistakes.