The internet has just endured the toughest 48 hours in cybersecurity history. Between October 20 and 21, four incidents occurred, each of which would have been the headline event in a normal year. The month has already been dubbed "Black October."
The crypto industry found itself at the epicenter of this wave: the threats overlapped and hit the infrastructure that exchanges, wallets, and payment services depend on.
Four Strikes in Two Days
The first — PHP2Shell. That is the name given to two critical vulnerabilities in PHP — the language that powers roughly 70% of websites worldwide. They allow arbitrary code to be executed on a server without a login or password. The problem was announced on October 20, and an emergency update was released on the 21st. Many websites, including government sites in Europe, were taken offline in the meantime. The coding errors had existed for decades, but turning them into a working attack only became possible with the help of AI.
The second — the failure of the Indian center eMudhra. Such centers issue certificates that confirm a website's authenticity. Eight eMudhra certificates were protected with keys so weak that they could be cracked in under a second. By October 20, the certificates had been blocked by Chrome, Apple, and Microsoft. eMudhra revoked them and estimated that around 30,000 client certificates would need to be replaced.
The third — the breach of the cloud platform Railway, where developers host their applications. On October 21, the company discovered that an outsider had gained access to client project settings. The attacker decrypted some of the data — it contained keys to external services and database passwords. Railway shut down the platform and asked all clients to change their keys and passwords.
The fourth — Node.js, the platform on which the servers of many applications run. On October 21, updates were released for versions 22, 24, and 26. The most dangerous flaw was in the data unpacking module: if a server received a specially crafted file, an attacker could execute their own code on it.
Consequences for the Crypto Industry
No exchange and no wallet reported a breach. But security chiefs at major companies raised the alarm. Kraken's Chief Security Officer Nick Percoco urged everyone to urgently update all servers running PHP, and if that is impossible — to disconnect them from the internet or shield them behind a firewall. After updating, he advises checking servers for unauthorized administrator accounts and hidden remote-access programs.
Patching a vulnerability does not expel anyone who has already managed to get inside. A separate risk is routers, network-attached storage, and control panels with built-in PHP. Updates for these are released by the manufacturer, and some devices may never receive them.
Charles Guillemet, CTO of hardware wallet maker Ledger, drew attention to the fact that the threats overlapped. Node.js runs on the servers that connect crypto applications to blockchains. And the eMudhra certificates were responsible for verifying the authenticity of the connections through which exchanges and custodians communicate with external services.
Cloudflare found no traces of attacks via these certificates, but advises everyone to update the trusted certificate lists on their servers. The Railway incident strikes a different spot: among the stolen data were keys to AI services, and the platform is actively used by crypto projects.
Cryptalist analysis: A cascade of four independent incidents in two days exposes a systemic vulnerability in crypto infrastructure — its dependence on the shared web stack, where a failure in one link is instantly transmitted to exchanges and custodians. The market has not yet reacted with panic, but institutional players should reconsider their priorities: the speed of patching and the auditing of third-party services are becoming a risk factor no less important than the volatility of the assets themselves.