Bitaddress.org bug?? private key mismatch

[ArpFlush]

Hi all,

When using the paper wallet via bitaddress.org, I advice you to check the public address first in blockchain.info.

Reason: I created a new paper wallet, then checked the pub address and there is 1 BTC on it! Strangely enough, the corresponding private key didn't match!! This means that you better always  double check the private key before sending funds to your paper wallet.

[DannyHamilton]

Although it might be possible that there is a bug in bitaddress.org, it is far more likely that you have malware on your computer that changed the bitcoin address. Or that you simply made a mistake and that the address that bitaddress.org generated is not the address that you looked up.

[ArpFlush]

Although it might be possible that there is a bug in bitaddress.org, it is far more likely that you have malware on your computer that changed the bitcoin address. Or that you simply made a mistake and that the address that bitaddress.org generated is not the address that you looked up.

No, I checked it multiple times. I also extracted the public key from the private key (via Armory) and it results in a different public address. Malware, well, in these days of APT's you never know but normally my machine should be clean.

[KIRAZ]

Wow, that's really strange i made one last month from their. Why don't you report this bug/issue to them - maybe they dig deep in it
and tell ya what's the mess up is about.

[ArpFlush]

Wow, that's really strange i made one last month from their. Why don't you report this bug/issue to them - maybe they dig deep in it
and tell ya what's the mess up is about.

I'm on it 

[yayayo]

If true this could be devastating, because Bitaddress is used to such a great extent. It also may have gone unnoticed for a long time, because the main use of this service is cold storage.

I'm no JavaScript expert. But could it be caused by a malicious script injection?

(Posting here to remind me.)

ya.ya.yo!

[cr1776]

If you want more insight, it would be useful to post both the keys you are discussing AFTER, and only AFTER, you have moved any coins, had a good number of confirmations and made sure you aren't sending any coins there.

[tzortz]

Nice thread.

Thanks to know all these.

[Cryptopher]

Further to DannyHamilton's response, I too wonder if it is a case of an isolated incident.

Have you tried to create more paper wallets since? Did you observe the same problem?

Could you not share any details on the keys seeing as you will presumably not be using it?

The change log doesn't show any updates since April, so if there is a bug then it will have been around for a while. I would have expected to hear more reports into this.

Good job that you checked though - think that it is good practice to check things and then check again before going ahead with it when it comes to crypto.

[ArpFlush]

Well, here's an update.

I scanned both QR's with my phone. The left one (public key) doesn't match the written BTC address below the QR. The private key QR was correct.

In other words: the left part of the page (Bitcoin address) > QR code doesn't match BTC address below the QR. As I used my desktop machine I copy/pasted the btc address in blockchain.info > result: 1BTC on this address (felt like I won the lottery)

Conclusion: Both QR codes match each other, both keys printed in clear text don't match. Check before using you must 
Luckily I didn't send BTC to this address!

[twister]

If this bug is real it can make people lose a lot of bitcoin. People make paper wallets and send moeny to them and never check if the key matches the address or not. How do one check the key offline?

[DaveF]

If this bug is real it can make people lose a lot of bitcoin. People make paper wallets and send moeny to them and never check if the key matches the address or not. How do one check the key offline?

Download Electrum on a machine that has never had it installed before & unplug machine from internet.
Run Electrum and then Wallet --> Private keys --> Import [type in the private key and make sure it brings up the correct address.]
Then delete all the info from the proper locations on your PC to be sure that there is no record of the private key.

-Dave

[yayayo]

Well, here's an update.

I scanned both QR's with my phone. The left one (public key) doesn't match the written BTC address below the QR. The private key QR was correct.

In other words: the left part of the page (Bitcoin address) > QR code doesn't match BTC address below the QR. As I used my desktop machine I copy/pasted the btc address in blockchain.info > result: 1BTC on this address (felt like I won the lottery)

Conclusion: Both QR codes match each other, both keys printed in clear text don't match. Check before using you must 
Luckily I didn't send BTC to this address!

Well then it's serious. What browser do you use?

Any response from the bitaddress team?

They should take down the site until they have identified and solved the error.

ya.ya.yo!

[twister]

If this bug is real it can make people lose a lot of bitcoin. People make paper wallets and send moeny to them and never check if the key matches the address or not. How do one check the key offline?

Download Electrum on a machine that has never had it installed before & unplug machine from internet.
Run Electrum and then Wallet --> Private keys --> Import [type in the private key and make sure it brings up the correct address.]
Then delete all the info from the proper locations on your PC to be sure that there is no record of the private key.

-Dave

Gr8 idea! I will do this prior to sending any amount to any paper wallet. Thx for this. +1

[lontivero]

Folks, I tested it by myself and keys are okay.

[TheButterZone]

Open issue: https://github.com/pointbiz/bitaddress.org/issues/90

[lontivero]

@ArpFlush could you post an image with the key pair? It is not useful for you, isn't it? I would like to see it by myself.

[TheButterZone]

I wouldn't reveal anything publicly yet. First, import both the uncompressed and compressed private keys that Bitaddress generated. Each type of private key corresponds to a different address.

[lontivero]

Please take a look at the Bitaddress' IP address that you get because someone could modify your local DNS, proxy or any other record in the LAN. If that is posible then you could be accessing to a fake Bitaddress.org site.  

[ArpFlush]

@ArpFlush could you post an image with the key pair? It is not useful for you, isn't it? I would like to see it by myself.

Sure: (sorry for the upside/down)