Black October

Eleven major digital-infrastructure failures struck within a single October week, including two critical PHP vulnerabilities affecting roughly 70 percent of all websites, eight weak-key certificates that forced Mozilla, Chrome and Microsoft to revoke trust and left about 30,000 certificates needing replacement, and an AI-agent hacking campaign that tested more than 1,100 attack projects across 14 dashboards at roughly $5 per task. Security firm NorForge investigated exposed control panels for the Cairn tool, which coordinates AI agents to find and exploit website weaknesses; Reuters identified victims including Deere, SharkNinja and Cummins, with the average time from reconnaissance to compromise under 23 hours. Hosting platforms Railway and Zeabur were also breached, with Zeabur's leaked administrative password exposing 321,000 accounts and more than 3 million stored secrets before the company said it would shut down by the end of December.

You are trying to pay a utility bill online, but the page just hangs. You refresh, and the entire site is gone. Your internet is fine. The problem is that the neighborhood’s digital plumbing — the unglamorous code your bank and your grocery store both depend on — stopped working, all at once, for reasons nobody planned. This was not a single, coordinated attack by a central villain. It was a strange, overlapping chain of eleven major failures in one October week. No single AI system caused them all. There is no evidence of a grand conspiracy. There is just a lot of broken infrastructure at the same time — which, depending on your temperament, is either reassuring or considerably worse. Start with the plumbing. PHP is the programming language that runs about 70 percent of all websites — the part most people never see or think about. In mid-October, two critical vulnerabilities in that language were disclosed, bugs serious enough that the U.S. cybersecurity agency issued an urgent alert. Amazon’s threat-intelligence team spotted exploitation attempts four days before anyone was supposed to know. Governments in the Netherlands, Finland, and Belgium shut down their own public websites rather than leave them exposed. They were not hacked. They chose to go offline, the way you might close the store when the foundation starts to shake. The trust that tells your browser a website is real broke too. Eight certificates — the digital stamps a company called a certificate authority issues to prove a website is who it claims to be — had been generated with private keys so weak that researchers found one of them was literally the number 4. The error traced back to a script flaw at a key-ceremony more than a year earlier. When the problem was reported in mid-October, browsers moved fast: Mozilla revoked trust, Chrome blocked connections, Microsoft followed. About 30,000 certificates now need to be replaced. If you visited a site that relied on those stamps and your browser had not yet updated, there was no way to know whether the site was the real one. Then there was the AI-hacking toolkit that barely needed a human in the room. A security firm called NorForge investigated exposed control panels for a tool called Cairn, which coordinates AI agents to find weaknesses in websites and break in. One campaign, run in Chinese and likely a single operator, tested more than 1,100 attack projects across 14 dashboards. Reuters identified victims https://www.reuters.com/legal/government/how-one-hacker-used-ai-agents-few-thousand-dollars-break-into-scores-sites-2026-10-19/ — including Deere, SharkNinja, and Cummins — by reviewing the attacker’s activity. The cost was roughly $5 per task https://norforge.com/blog/inside cairn on average — and since about one try in ten succeeds, that works out to roughly $50 per successful compromise, with considerable uncertainty in the researchers’ own numbers. The average time from starting to poking around to getting inside was under 23 hours. The agent setup was repurposed from a competitive hacking-game framework, the sort of thing university students practice on. Now it picks real locks. The developers who build the apps on your phone were hit too. Railway, a platform where engineering teams host their projects, disclosed that a stranger had gotten into the systems storing secret keys — the login credentials apps use behind the scenes to connect to databases and services. It told every customer to change every key immediately and paused all new deployments while it investigated. Zeabur, a similar platform, was breached more completely: a leaked administrative password left accessible on the open internet gave an attacker access to 321,000 accounts and more than 3 million stored secrets. The attacker also added their own access keys to fifty servers. Zeabur decided to shut down for good by the end of December. A bug in Signal, the messaging app millions use precisely because it promises privacy, meant that after you hung up a voice call, the other person’s phone might keep receiving your audio — and potentially your video — because the remote party could flood the call’s controls and prevent it from closing properly. The fix is out. If you have not updated recently, it is worth doing now. In the grocery aisle, the effect was concrete. Ahold Delhaize, the company behind Food Lion, Stop & Shop, Hannaford, and Giant Food, detected suspicious activity on October 12 and took its own digital systems offline — websites, mobile apps, internal tools. They stayed dark for more than a week. The physical stores never closed, but if you were trying to order groceries online through any of those brands, you were out of luck. By October 19, the company confirmed that someone malicious had gotten in. AI had a supply-chain problem too. A popular developer tool called LiteLLM, used to route AI queries to different services, was briefly infected on October 21 with code designed to steal passwords. An attacker had stolen authentication tokens from three of the tool’s engineers, according to the project’s own incident report, and pushed a poisoned update that, once installed, quietly harvested browser passwords, cloud credentials, and secrets tied to more than twenty AI coding tools. The tainted version was live for about two hours on a public package registry before it was caught and pulled. Meta’s AI assistant, Muse, left private conversations exposed in a different way. Security researchers found that more than 6,800 shareable links to private Muse conversations — threads containing bank transaction details, loan applications, and work calendars — had been indexed through the domain-name records their web addresses generated. Anyone with a browser could open them. The researchers opened only a few hundred and said nearly every live link opened on sight with no login required. Meta paused the sharing feature after the researchers reported it. More was happening too, reported but less fully verified at this writing. Hundreds of Tor connections were reported hijacked. Malware was reported planted on thousands of servers in Japan. None of it was coordinated. All of it was real. Stack these incidents side by side and the volume itself becomes the story. Any one of them is a bad week for IT teams. All of them in the same seven days is something else — not a coordinated cyberwar, but the sound of a system that is too complex to manage finding that out all at once. The internet is not a solid floor. It is a web, and in October, it frayed in a dozen places at the same time. If that makes you want to update your passwords and call it a day, that is not a bad instinct. It might also not be enough.