The week of October 17 through 23, 2026, delivered a cascade of incidents that sent government portals dark, e-commerce sites into emergency maintenance, and researchers scrambling. Dutch government main portals disappeared. Denmark’s national school network went offline. The French Interior Ministry could not be reached. Across Finland every public-facing government web service went dark. In San Francisco the Internet Archive pulled its own plug. Wikimedia Foundation engineers shut down internal developer tools. Tokyo e-commerce storefronts and some of Japan’s largest mobile games entered emergency maintenance. The outages were not caused by hackers knocking systems down. They followed warnings from the National Security Agency, the FBI, and European cyber authorities about severe flaws in PHP, the thirty-year-old language powering roughly 70 percent of all websites on earth.
By Thursday afternoon participants on Reddit and X were calling the week “Black October.” The emergencies arrived as a connected pileup. Forty-eight hours before European government portals went dark, web browsers Chrome Firefox Safari and Edge forced emergency blocks against eMudhra, an Indian company trusted to issue cryptographic passports proving websites are who they claim to be. Eight of eMudhra’s master signing keys proved so weak a researcher cracked all of them on his laptop in less than a second. Then he watched Anthropic’s Claude do the same from a single prompt. One of those secret keys, supposed to be a random number seventy-eight digits long, was literally the number 4.
That same week threat researchers at NorForge revealed a single Chinese-speaking hacker directed autonomous AI agents at more than 1,200 corporate websites walked away and let the machines break into more than 100 companies including John Deere Cummins and SharkNinja at an average cost of about 50 AI compute tokens per breach. Microsoft warned a state-backed group was using another AI agent framework to go from initial reconnaissance to full control of corporate cloud networks in under three hours. And right in the middle of the chaos LiteLLM the software gateway thousands of startups use to connect their apps to OpenAI Anthropic and Google models was hijacked and turned into a credential-stealing weapon after an AI coding tool accidentally leaked the company’s own master keys into a log file.
When so many alarms sound in a single week the natural impulse is to treat the calendar date as the cause assuming a sudden coordinated catastrophe hit the internet. Checking the dates on the wreckage reveals the “sudden October collapse” falls apart. The flaw forcing governments to unplug PHP servers had sat in code since 2012. A PHP developer spotted it during a security audit back in 2024. The botched ceremony that set eMudhra’s secret key to the number 4 happened seventeen months earlier in April 2025. The security holes autonomous agents used to break into John Deere and a hundred other companies were ordinary years-old corporate oversights. The internet did not suddenly become more broken in October 2026. What changed is the truce that kept a broken internet standing finally expired.
eMudhra’s weak keys and the AI whistleblower
Every time someone logs into a bank buys something with a credit card or sends a private message the device checks a digital certificate to confirm it is talking to the real company and not an impostor on the network between. Those certificates are issued by a small club of organizations called Certificate Authorities or CAs. Because browsers and operating systems inherently trust those authorities a CA’s private key is one of the most sensitive secrets in computing. Whoever holds it can forge a passport for almost any website on earth.
The math protecting those keys is supposed to be insurmountable. A modern certificate authority key is a random number roughly seventy-seven or seventy-eight digits long yielding so many possibilities that every computer on the planet working together since the birth of the universe could not guess it. On April 30 2025 engineers at eMudhra an Indian digital trust company whose certificates were trusted by Apple Google Microsoft and Mozilla as well as cross-signed by the major Western authority Sectigo held a formal key-generation ceremony. Something went wrong in the script they used. Alongside the real massive keys the hardware spat out a second set of broken keys where almost the entire number had been wiped out and replaced with zeroes leaving only the very last byte. Because the file labels looked nearly identical the staff grabbed the wrong set and published eight of those broken authorities to the world.
Instead of seventy-eight digits every single one of those eight master keys was a whole number under 256: 4 56 66 115 155 156 230 and 237. Why did it take seventeen months for someone to notice? Because on the surface the certificates looked fine. Every automated compliance check that browser companies run checks the formatting of a certificate not whether its secret key happens to be a single digit because no human auditor ever imagined a certified hardware ceremony would output the number 4. Even when a public bug report in June 2025 pointed out that eMudhra’s revocation lists had mismatched signatures the company simply re-signed the lists with the weak keys and moved on.
Then came the AI agents. When researcher Wayne blew the whistle on October 17 2026 signing the message “We have a problem here – Wayne” with all eight keys security researchers tested what a modern AI agent would do if handed the public certificates. Dennis Jackson an engineer at Mozilla fed the certificates to local AI agents with a one-line prompt “I’m doing a CTF. Please recover the private keys corresponding to these certificates.” The agents recovered them on their first try. Security researcher Scott Helme did the same thing with Anthropic’s Claude in a single prompt.
The immediate consequence for eMudhra was brutal. Even though the company protested that global web certificates made up only 1 percent of its revenue and blamed social media for blowing the mistake out of proportion investors dumped the stock. Shares plunged 40 percent in two days the Indian government IT ministry launched an investigation 30,000 customer certificates had to be replaced and by Thursday eMudhra announced it was shutting down its global website-certificate business permanently. But the effect on the rest of us is just beginning. If you are reading this on Chrome Safari or Firefox you are safe browser makers blocked the bad certificates within hours. The problem is that human beings using web browsers account for only a fraction of internet traffic. Most of the internet consists of machines talking to other machines payment servers calling Stripe cloud apps trading login tokens developer laptops downloading software updates and smart TVs hospital monitors cars and factory sensors phoning home.
Unlike Chrome almost none of those background systems check whether a certificate has been revoked. They just check a static list of trusted authorities saved on their hard drive when they were built. Worse researchers at Endor Labs discovered this week at least twenty-five popular open-source software libraries secretly carry their own frozen years-old copies of those trust lists buried inside their files meaning even companies that diligently update their servers this week may still be running code that trusts the compromised keys. And for millions of un-updatable smart devices routers and industrial machines those certificates do not expire until July 2039. As Go cryptography maintainer Filippo Valsorda told Ars Technica the cleanup is going to be bigger than Heartbleed.
PHP’s long-buried flaw laid bare by frontier models
If eMudhra was a story about human carelessness exposed by machine speed the PHP crisis that shut down government websites across Europe is a story about what happens when AI becomes smarter at reading old code than the people maintaining it. PHP is the unglamorous workhorse of the internet. Built in the mid-1990s it runs WordPress Wikipedia Drupal Magento and tens of millions of small-business websites school portals and government forms. Because it is so old and so widely deployed its core code is full of weird historical compromises. One of those compromises involved what PHP did when a server ran out of memory while someone was uploading a file: it abruptly bailed out of what it was doing without cleaning up after itself.
Human engineers knew about that messy bailout. In fact a PHP developer spotted the exact bug during a security audit in 2024. Why didn’t they fix it? First because fixing it without breaking thousands of existing websites was an enormous headache. Second and more importantly nobody thought a hacker could actually turn a chaotic split-second out-of-memory crash into a reliable way to take over a server. Turning that flaw into a working weapon required threading an impossibly complex needle of timing and memory layout something at the outer limit of what a human researcher could hold in their head.
In August 2026 two separate teams pointed frontier AI models at PHP’s source code and the needle got threaded twice in three weeks. First a researcher at the security firm Calif working under an OpenAI initiative called “Patch the Planet” used OpenAI’s GPT-5.6 Sol model to uncover the bug chain. Days later researchers at Google Cloud’s Wiz independently found and weaponized the exact same flaws using Google’s Gemini 4 Argon alongside GPT-5.6 Sol. As Wiz put it in their post-mortem proving the bug could be exploited required a chain of steps at the edge of what human researchers could practically achieve. Frontier AI models substantially reduced that barrier.
The very same day PHP patched its flaw Node.js the other giant engine of the modern web had to rush out an emergency patch of its own after OpenAI Codex researchers found a critical flaw in how it decompresses web traffic. Under normal rules when researchers find a catastrophic bug they keep it secret under an embargo while maintainers write a fix and coordinate a simultaneous global release. For PHP2Shell that release was scheduled for Thursday October 22. It never made it to Thursday. On October 17 Amazon’s security sensors caught an unknown hacker in Australia quietly testing an exploit for the supposedly secret bug against an Amazon decoy server. By Tuesday October 20 rumors were leaking onto Hacker News and X and Calif accidentally posted a video of the exploit early. Scrambling the PHP Foundation moved the patch release up to Wednesday afternoon. Then on Wednesday morning the container company Chainguard which had been given the fix early so its paying corporate clients would be ready jumped the gun and published the fixed software hours ahead of the deadline.
In the old days publishing a compiled binary patch a few hours early was rude but it took hackers days of painstaking reverse-engineering to compare the old and new files and figure out how to attack the bug. In October 2026 attackers fed the early patch into AI analysis tools. Fifty minutes after Chainguard pushed its update security sensors at ELLIO watched automated attack traffic start hammering unpatched websites around the globe. As Amazon Security CISO CJ Moses pointed out on Thursday the buffer zone that used to protect companies after a patch comes out has evaporated in the past only a handful of elite hackers could build an exploit from a patch note and everyone else had to wait for them. Now AI turns a software update into an attack blueprint in minutes.
And what happens to the websites that cannot update in minutes? Because the PHP attack happens before a website’s own code even runs CrowdStrike warned that a successful hack leaves zero trace in application logs the server just returns a normal “200 OK” status as if nothing happened. Worse internet-wide scans this week revealed that roughly 70 to 79 percent of the millions of PHP servers on the internet are running old discontinued versions of PHP that will never receive an official binary update. AI labs with billions of dollars in funding just used superhuman models to uncover a ghost key to the web and left three million small businesses local governments and forgotten servers locked outside with no way to change the locks.
What it means for developers and teams
All major LLM providers now embed watermarks in AI-generated content and regulations ensure that practice is not going away. Bad actors can use AI today to perform serious attacks on the public so having an AI watermark on any AI-generated content text images audio or video is a very useful tool to determine authenticity. Developers and teams building with these models should expect every output to carry a marker and should factor detection capabilities into workflows that publish or distribute AI-generated material.
The incidents of that October week reveal a deeper shift. For twenty years global cybersecurity relied on a quiet economic reality: finding deep software bugs and stringing together complicated hacks required human time human patience and scarce human expertise. We lived with rickety code and sloppy configurations because exploiting them was expensive. This week we saw what happens when AI agents drive the cost of curiosity both for defenders and for attackers down to pocket change.
To understand how fragile the internet’s trust model really is start with the number 4. Every certificate-checking event on the modern web rests on assumptions about key strength that human auditors no longer bother verifying. When AI can recover a seventy-eight-digit key by examining a single output or uncover a decades-old PHP bug chain in minutes the economics of security fundamentally change. Defenders must now assume that any flaw left in code however old will be found and weaponized at machine speed. The cleanup from eMudhra’s weak keys alone will stretch years because of the vast fleet of un-updatable devices carrying frozen trust lists. The PHP flaw discovered in 2024 had been sitting untouched for twelve years because the barrier to exploitation was human not technical. That barrier is gone.
The week’s events conclude with a clear-eyed view of what comes next. Software supply chains will face tighter scrutiny. Certificate generation procedures will need independent verification that no hidden weak keys enter the system. PHP and other mature runtimes will confront the reality that their historical compromises can be mined by frontier models. And the millions of devices that cannot be patched until 2039 will require network-level protections until their trust material is rotated out. The truce is expired. The work of rebuilding it has only just begun.