This is an example of how risky Bitcoin could be if you stored them in a an exchanger or probably also known as bank. You can’t trust your bank on the early days to keep your money. Same thing here, you can’t trust business such as this to keep your Bitcoin, it’s still new. Better to save it on your local computer with multiple backup, back up to the CD or DVD physical drive also just in case, it’s the only guarantee way to recover your loss coins due to data failure. However stolen would not be recoverable, stolen is a different story. Think of stolen as someone reach into your wallet and take the cash, leave no trace, gone forever. No different than in real life, just a convenient with Bitcoin.
—–BEGIN PGP SIGNED MESSAGE—–
Two hacks totalling about 4100 BTC have left Inputs.io unable to pay all user balances. The attacker compromised the hosting account through compromising email accounts (some very old, and without phone numbers attached, so it was easy to reset). The attacker was able to bypass 2FA due to a flaw on the server host side.
Database access was also obtained, however passwords are securely stored and are hashed on the client. Bitcoin backend code were transferred to 10;15Hd@mastersearching.com:email@example.com (most likely another compromised server).
What about my coins there? If you stored more than 1 BTC, send an email to firstname.lastname@example.org with a Bitcoin address (preferably, an offline, open source light/SPV wallet like Multibit or Electrum). Use the same email you’re using on Inputs. Please don’t store Bitcoins on an internet connected device, regardless of it is your own or a service’s.
I know this doesn’t mean much, but I’m sorry, and saying that I’m very sad that this happened is an understatement.
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.11 (GNU/Linux)
—–END PGP SIGNATURE—–
Access inputs.io if you want to verify your balance, look up your transactions, etc. Don’t add coins.
[tubepress mode=’tag’, tagValue=’inputs.io hacked’, resultsPerPage=’10’]