▶

Bitcoin Magazine

Bitcoin Security Expert Jameson Lopp: Cyberattacks on “Exponential” Path

Bitcoin Core just changed its security policy because AI can find bugs with a simple prompt. Jameson Lopp explains the bigger trend behind it: two and a half months of exponential growth in vulnerability discovery, attackers adopting uncensored AI models first, and security researchers who “have not been able to get a lot of rest.” He breaks down the PHP remote code execution flaw, why the fallout was smaller than expected, and why security now has to be real time and built into the development pipeline instead of a once-a-year audit.

Chapters:
0:00 Bitcoin Core Changes Its Security Policy: AI Finds Bugs With a Simple Prompt
1:04 Google’s 500,000-Qubit Estimate: Physical vs. Logical Qubits
2:00 The Quantum Timeline: “If We Have Less Than a Decade, We’re Behind”
2:57 Why We Don’t Have a Quantum Computer With More Than a Few Hundred Usable Qubits
4:26 30% of Addresses Have Exposed Keys: Who Attackers Would Target First
6:27 Why a Quantum Upgrade Will Take Years: Taproot, Consensus and Untested Cryptography
7:54 The PHP Remote Code Execution Flaw Explained
9:41 The Real Trend: Exponential AI Vulnerability Discovery and Exhausted Defenders
10:54 Security Must Be Real Time: From Annual Audits to the Development Pipeline
13:19 Hardware That Can’t Be Patched, and Why Wrench Attacks Have Topped 700

DISCLAIMER: The views and opinions expressed in this show are those of the participants and do not necessarily reflect the official policy or position of BTC Inc., Bitcoin Magazine, or any affiliated entities. This content is provided for informational and educational purposes only and should not be construed as investment, legal, tax, or accounting advice. Nothing contained in this show constitutes a solicitation, recommendation, endorsement, or offer to buy or sell any securities or financial instruments. Viewers should consult their own advisors before making financial or business decisions.

This post Bitcoin Security Expert Jameson Lopp: Cyberattacks on “Exponential” Path first appeared on Bitcoin Magazine and is written by Patrick Green.

▶

Bitcoin Magazine

PHP Hack: How Bitcoin Will Respond to the “Cyber Pandemic”

Government websites in France and Finland and hospital sites in the Netherlands are offline, Cloudflare is seeing attack traffic, and Britain’s National Cyber Security Centre is telling organizations to pull systems if they can’t patch fast. Bitcoin Magazine technical editor Shinobi joins Grace Remington and Sean Hagan to explain what broke in PHP, why memory management mistakes are the most common security flaw, and why AI finding the exploit in hours changes the pace of hacking but not its nature. He also answers the question every Bitcoiner is asking: is Bitcoin exposed?

Chapters:
0:00 The PHP Exploit Takes Government and Hospital Websites Offline
0:54 AI Found the Flaw in Hours: The “Cyber Pandemic” Warning
1:45 What Actually Broke: Memory Management Mistakes Explained
3:06 Why PHP Was Never Secure and Why This One Is Different in Scale
3:47 Is the AI Hacking Story Sensationalized? AI Does 95% of the Work
5:08 The Rough Adjustment Period and Why Shinobi Is Confident About the Other Side
6:41 No Serious Software Will Ship Without an AI Security Audit
7:23 Is Bitcoin Exposed? libsecp256k1, Bitcoin Core and Why Slow Development Was Right
9:30 Take Your Lightning Node Offline and Keep Your Coins in Cold Storage
12:09 Multisig and Sparrow Setup Checks, and Where to Follow Security Engineers

DISCLAIMER: The views and opinions expressed in this show are those of the participants and do not necessarily reflect the official policy or position of BTC Inc., Bitcoin Magazine, or any affiliated entities. This content is provided for informational and educational purposes only and should not be construed as investment, legal, tax, or accounting advice. Nothing contained in this show constitutes a solicitation, recommendation, endorsement, or offer to buy or sell any securities or financial instruments. Viewers should consult their own advisors before making financial or business decisions.

This post PHP Hack: How Bitcoin Will Respond to the “Cyber Pandemic” first appeared on Bitcoin Magazine and is written by Patrick Green.

TL;DR: PHP released fixes for two critical flaws on October 21 and urged immediate updates. Crypto businesses using PHP-based web infrastructure should check that layer of their systems; the advisory does not announce a breach of Bitcoin or BTCPay Server itself.

Security work for a crypto business does not end at its wallet. A critical PHP update has put ordinary web-server software back on the operational agenda.

The PHP project’s October 21 advisory identifies two vulnerabilities that can allow unauthenticated remote code execution. Fixed upstream releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The project strongly encourages affected users to update immediately.

It says installations serving web requests are at risk and highlights the Apache mod_php configuration as particularly exposed. Distribution vendors may provide patched packages, so the applicable fix depends on how the software is supplied and maintained.

A Payment Stack Contains More Than Its Payment Processor

The connection to crypto commerce is practical. BTCPay Server’s official documentation explains how merchants can connect its payment system to WooCommerce, including arrangements involving an existing store or a deployed store environment.

A merchant using that combination has several components to maintain. The checkout website, its plugins, the hosting environment and the payment service have distinct responsibilities. Updating one component does not establish that every other part of the stack has been patched.

The PHP advisory is about the runtime handling web requests. It is not evidence that Bitcoin’s protocol has been compromised, and it does not by itself identify a flaw in BTCPay Server’s core software.

It does provide a reason for administrators and hosting providers to check whether any connected storefront or service uses an affected PHP installation. The relevant confirmation is that the running environment contains the fix, rather than simply that an application plugin was updated.

Follow The Maintainer’s Remediation

The PHP team’s guidance is the authoritative starting point for remediation and version-specific details. Unsupported installations need particular attention to vendor support or migration to a maintained release.

No claim about stolen customer funds or a specific crypto company’s compromise is established by the advisory. The immediate news is the release of critical fixes for infrastructure that can sit underneath a crypto payment experience.

Related Reading

• BTCPay Server Patches Critical LND Credential Bug After Lightning Wallet Drain
• Coldcard Security Notice Puts Bitcoin Wallet Entropy Risk Back In Focus
• EIP-7702 Wallet Delegation Faces Scrutiny After Phishing Research

This article was written by the News Desk and edited by Samuel Rae.