Scammed by 0xE6bA5554741B23199B54Cfc06b1AbC871b6A127D

Quickseller

copper member

Activity: 2996

Merit: 2374

Quote from: harper86 on May 27, 2018, 11:55:27 PM

he or she managed to compromise my email account and dropbox.

As a general rule, it is not a good idea to keep unencrypted backups of your private keys in your email nor in a cloud service.

Hopefully this is not a lot of money to you, and you can let this be a lesson learned.

I don't really like the idea of keeping private keys in a cloud account, but if you insist on doing this, they should be encrypted, preferably with GPG, the private key of which is not in that cloud account. A safe deposit box is probably a better solution for an offsite backup.

harper86

jr. member

Activity: 87

Merit: 3

Quote from: timerland on May 30, 2018, 03:29:38 PM

It'll be extremely hard to track these coins down. Even if you did get in touch with Binance's support, it's relatively unlikely that they are able to identify the particular user account for you. Firstly, because it could have been anyone's binance deposit address, not just the scammer's. Secondly, because of their privacy obligations that most likely mean that they can't share sensitive info about their customers. And of course, you can't really prove that you are hacked simply by showing a tx.

I tried to search up both addresses, and came up with nothing of value.

The chances of tracking down these stolen coins are extremely slim, imo. You could continue to do it if you have the time, but I would personally invest it into securing my wallet for future storage.

Yes, you are quite right. Despite knowing this, I was just trying my luck. Will have to resign to the fact that whats lost is lost.

timerland

hero member

Activity: 1526

Merit: 596

It'll be extremely hard to track these coins down. Even if you did get in touch with Binance's support, it's relatively unlikely that they are able to identify the particular user account for you. Firstly, because it could have been anyone's binance deposit address, not just the scammer's. Secondly, because of their privacy obligations that most likely mean that they can't share sensitive info about their customers. And of course, you can't really prove that you are hacked simply by showing a tx.

I tried to search up both addresses, and came up with nothing of value.

The chances of tracking down these stolen coins are extremely slim, imo. You could continue to do it if you have the time, but I would personally invest it into securing my wallet for future storage.

harper86

jr. member

Activity: 87

Merit: 3

Nope.

stunvn

full member

Activity: 266

Merit: 100

Is that you? https://bitcointalksearch.org/topic/m.38931432

harper86

jr. member

Activity: 87

Merit: 3

My LTC and ETH were stolen, I am pretty much to blame due to lax security on both of these wallets (poor security measures where wallet.dat was left unsecured and seed and keys were saved in a txt file).
I am not entirely sure how the attacker gained access to my funds, although he or she managed to compromise my email account and dropbox. I have since then taken necessary measures to fix those breaches. I understand pretty much that the funds are not recoverable, however I would be grateful if anybody can help me find where the attacker is from or if any of the addresses look familiar.

Summary:
LTC Stolen: 8.5
Address stolen from: Lg6LuzWYb76ELFLDUA17MEtfF6gQ4r1Eou
Address txed to: LRNpXp63TcKJEMVvbbXqG9UCwm6hNpf8H4
The LTC has been spent since

ETH Stolen: 2.78
Address stolen from: 0xacB24150E65526F465DcE2189ab7fAB915F2B7be
Address txed to: 0xE6bA5554741B23199B54Cfc06b1AbC871b6A127D
The ETH has been txed to Binance since

The ETH account txed to receives active payments from nanopool.

Although an extremely long shot, I have gotten in touch with binance. I am pretty sure they would turn my request down. But I would be grateful if anybody on the forum who might have some idea or information on that particular ETH address would help me out here.

Thank you

Topic: Scammed by 0xE6bA5554741B23199B54Cfc06b1AbC871b6A127D (Read 212 times)