JPEX Scandal Pushes Hong Kong's SFC to Roll Out New Crypto Rules

Blockchain.info to Reimburse Users Lost Bitcoins: "We Admit We Are at Fault"

by Leon Pick
    Blockchain.info to Reimburse Users Lost Bitcoins: "We Admit We Are at Fault"
    Join our Crypto Telegram channel

    Blockchain

    .info has announced via Twitter that it will be reimbursing users for funds lost in a recent spate of security breaches:

    Many in the community lauded the company for taking this step, although some still expressed concern over the effectiveness of their security measures.

    A couple of weeks ago, users started reporting that their accounts had been hacked and bitcoins had been withdrawn. Apparently, hackers managed to mount successful attacks on several fronts through Phishing

    and exploiting vulnerabilities in the Tor network.

    Blockchain.info also informed its user base yesterday that during a scheduled software update, part of the software ensuring the security of private key generation was adversely affected for a 2.5-hour window. They added, "The issue was detected quickly and immediately resolved. In total, this issue affected less than 0.0002% of our user base and was limited to a few hundred addresses." Several commenters responded, claiming to have incurred losses as a result.

    Blockchain

    .info has announced via Twitter that it will be reimbursing users for funds lost in a recent spate of security breaches:

    Many in the community lauded the company for taking this step, although some still expressed concern over the effectiveness of their security measures.

    A couple of weeks ago, users started reporting that their accounts had been hacked and bitcoins had been withdrawn. Apparently, hackers managed to mount successful attacks on several fronts through Phishing

    and exploiting vulnerabilities in the Tor network.

    Blockchain.info also informed its user base yesterday that during a scheduled software update, part of the software ensuring the security of private key generation was adversely affected for a 2.5-hour window. They added, "The issue was detected quickly and immediately resolved. In total, this issue affected less than 0.0002% of our user base and was limited to a few hundred addresses." Several commenters responded, claiming to have incurred losses as a result.

    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|} !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}