Ledger stated that it could not confirm the number of people affected by the tampered device incidents or the total amount lost.

Overview Debates Related claims Topics Sources

ViaBTC chief analyst Jeff Ko stated that spot bitcoin ETF holders have no direct exposure to Binance because underlying bitcoin assets are held with regulated custodians

DeFiLlama data showed that blockchain projects lost a cumulative $16.69 billion to hacks and exploits as of June 2026, with roughly 40% attributed to private-key compromises.

Google Multi-Party Compute splits private cryptographic key fragments across separate environments, allowing financial institutions to distribute key shares across on-premises hardware, Google Cloud, and competing cloud providers.

In June 2026, attackers compromised private keys belonging to a Humanity Protocol foundation member, draining more than $32 million from at least 17 wallets.

Google Cloud states that key shares are held in encrypted form and that Google cannot access customers' key material in unencrypted form on its infrastructure.

Google Multi-Party Compute allows financial institutions to set threshold signing requirements, such as requiring two-of-three or five-of-seven key share holders to authorize a transaction.

Chainalysis reported that compromised private keys accounted for 43.8% of all stolen cryptocurrency in 2024, representing approximately $2.2 billion in total losses.

Google Multi-Party Compute adds MPC-based transaction signing, policy enforcement, and key recovery to Google Cloud Key Management Service and Cloud HSM infrastructure.

The Singapore Police Force requested members of the public with information on cryptocurrency hardware wallet tampering crimes to call its hotline or submit reports online.

The Singapore Police Force urged cryptocurrency holders to be wary of unsolicited messages offering wallet verification or recovery assistance.

Direct in-kind transfers shift digital asset custody responsibilities to institutional third-party custodians, reducing self-custody burdens and cybersecurity threats such as DeFi exploits for investors.

BTCPay Server relies on a decentralized architecture where each business owner hosts its software on a private server and bears independent responsibility for securing their own infrastructure

BTCPay Server patched the August 2026 Lightning Network Daemon credential vulnerability in version 2.4.2 and restricted remote Lightning access following the August 2026 exploit

BTCPay Server hot wallets automatically store seed phrases on internet-connected merchant servers to automatically sign and approve payments without separate device confirmation

BTCPay Server urged operators running older software releases to update their installations to version 2.4.7

BTCPay Server reported that attackers logged in as administrators on compromised servers, while users running version 2.4.7 received no credible reports of hot wallet drains

BTCPay Server has no centralized master switch to disable vulnerable software, requiring the project to publicly instruct individual server owners to execute the ./btcpay-down.sh command

BTCPay Server instructed server operators to keep software turned off via the ./btcpay-down.sh command while asking affected users to submit server information and logs to its security team

BTCPay Server founder Nicolas Dorier stated that reports of hot wallets being drained on its servers involved software releases older than version 2.4.2, specifically targeting instances running version 2.4.1 or earlier released July 23, 2026

In August 2026, BTCPay Server confirmed an attack that exploited a software vulnerability in releases prior to version 2.4.2 to obtain Lightning Network Daemon credentials and steal funds