Google Slashes Quantum Resource Requirements for Breaking Cryptocurrency Encryption
Source SecurityWeek
Description
Google researchers have shown that breaking the encryption of Bitcoin and Ethereum requires 20x fewer qubits. The post Google Slashes Quantum Resource Requirements for Breaking Cryptocurrency Encryption appeared first on SecurityWeek .
Impact
If exploited, this threat could have profound impacts on the confidentiality, integrity, and availability of cryptocurrency assets globally. Attackers with sufficiently powerful quantum computers could derive private keys from public keys, enabling unauthorized access to wallets and the ability to forge or reverse transactions. This would undermine the trust model of blockchain networks, potentially causing massive financial losses, market instability, and erosion of confidence in decentralized finance systems. Organizations managing cryptocurrency exchanges, custodial wallets, and blockchain-based financial services would face severe operational and reputational risks. The threat also extends to any systems relying on similar elliptic curve cryptography, potentially affecting broader digital identity and secure communication infrastructures. However, the current lack of practical quantum computers capable of such attacks means the immediate impact is low, but the medium- to long-term risk is significant as quantum technology matures.
Defensive guidance
Organizations should begin transitioning to quantum-resistant cryptographic algorithms, such as lattice-based, hash-based, or multivariate polynomial cryptography, as standardized by bodies like NIST. Cryptocurrency projects should accelerate research and implementation of post-quantum signature schemes and key exchange protocols. Wallet providers and exchanges must implement robust key management practices, including minimizing public key exposure and encouraging users to generate new addresses frequently to reduce quantum attack surfaces. Monitoring advancements in quantum computing and participating in industry-wide efforts to develop quantum-safe blockchain protocols is critical. Additionally, contingency planning for potential quantum attacks, including insurance and incident response strategies, should be developed. Collaboration with cryptographic experts and adherence to emerging post-quantum cryptography standards will be essential to future-proof blockchain security.
Summary
Recent research by Google has revealed that the quantum computational resources required to break the cryptographic algorithms underpinning Bitcoin and Ethereum have been reduced by approximately 20 times. Specifically, the number of qubits needed to run Shor's algorithm or similar quantum algorithms capable of factoring large integers or solving discrete logarithms—core to the security of elliptic curve cryptography used in these cryptocurrencies—has been significantly lowered. This breakthrough implies that the timeline for quantum computers to threaten blockchain security is shorter than previously anticipated. While current quantum computers lack the scale and stability to exploit this vulnerability, the rapid advancement in quantum hardware development means that this threat is becoming more realistic. The vulnerability affects the fundamental cryptographic primitives that ensure transaction authenticity and wallet security, potentially allowing attackers to derive private keys from public keys, forge transactions, or double-spend coins. No patches or immediate fixes exist because this is a cryptographic threat tied to the underlying algorithms rather than software bugs. The research underscores the critical need for the cryptocurrency community to adopt quantum-resistant cryptographic schemes and prepare for a post-quantum security landscape. This threat is not an immediate exploit but a strategic concern that could undermine trust in blockchain systems if unaddressed.
References
Community reviews
Related threats
- Fresh WordPress Vulnerability in Attackers’ CrosshairsHighVulnerability
- php2shell one week later: Why one exploit doesn’t work everywhereHighVulnerability
- ZDI-26-839: MLflow PickleEvaluationArtifact Deserialization of Untrusted Data Remote Code Execution VulnerabilityHighVulnerability
- ZDI-26-843: MLflow SHAP load_explainer Deserialization of Untrusted Data Remote Code Execution VulnerabilityHighVulnerability
- ZDI-26-845: MLflow Statsmodels _load_model Deserialization of Untrusted Data Remote Code Execution VulnerabilityHighVulnerability