The internet had a very bad week.
Here's what the world was reading, saying and doing between 17 and 23 October 2026.
The people running the internet
"I think we're going to have a couple years where every single week it's going to feel like the sky is falling."
"I no longer think we're going to be able to just patch all the bugs."
"As bad as things have gotten in the past 4 days, they are going to get a lot worse before they get better."
"Jason is 100% right. Code red."
The flaw "impacts the majority of the Internet."
"We're in the part of the movie where you need to throw whatever you can in the path of the zombies."
Who pulled the plug
MUFG halted some online banking. Mizuho Bank and Daiwa Securities ran emergency maintenance. Shizuoka Bank switched off its app.
Jiji Press · 22 OctGermany, France, the Netherlands, Finland, Belgium and Czechia took government sites offline as a precaution.
Reuters · 23 Oct"If an immediate update is not feasible, it is recommended that organizations take the system offline."
NSA advisory · 21 OctRated the PHP flaws critical in note CIVN-2026-0510.
CERT-In · 21 OctTook systems down as a precaution until they could be safely patched.
Reuters · 23 OctMorgan Stanley began blocking outside AI agents. JPMorgan, Bank of America and Citi are restricting them.
Axios · 22 OctWhat is Black October?
Black October is the name people gave to the week of 17 to 23 October 2026. AI found two serious holes in PHP, the hidden code behind about 7 in 10 websites. The details leaked before the fix was out, attackers rushed in, and governments, banks and big websites went offline to patch. Three other security problems landed the same week, so the whole thing got one name.
Here's how it happened, step by stepFirst, understanding PHP
Every website has two parts: what you see, and the hidden machinery that makes it work. Black October happened in the hidden part.
↔Drag the line · Illustration, not real code
What you see is built with HTML, CSS and JavaScript. The hidden part that does the work is very often PHP.
PHP runs on the website's computer, called a server. It has quietly powered online shops, news sites, blogs, college portals and government pages since 1995.
So when something breaks inside PHP itself, it isn't one website's problem. It's most of the internet's.
So what was the hole?
Two flaws inside PHP itself, nicknamed PHP2Shell, let a stranger skip the login and run their own commands on a website's server. No password needed.
Who found it? AI did.
For 14 years, nobody saw how serious it was. Then AI security tools read through PHP's code and flagged it.
The catch: AI can find flaws for anyone who asks. Defenders got there first this time. The race is getting shorter.
Illustration, not PHP's real code. Sources: SecurityWeek, Axios, The Hacker News.
Then why is everyone panicking?
Because the secret got out before the fix did. Keep scrolling and watch the week unfold.
- AUGUSTAI finds it firstCalif and OpenAI report it to PHP privately. Wiz finds it too.
- 17 OCTFirst attempt spottedAmazon's decoy servers log an attack, four days before any fix.
- 18 OCTeMudhra certificates pulled8 of its certificate-authority keys were found weak and revoked. Chrome and Firefox block them.
- 20 OCTDetails leak earlyHow the flaw works gets out two days before the planned reveal.
- 21 OCTFix out. Rush begins.PHP ships the fix at about 7:20 pm IST. Within 45 minutes, tens of thousands of attempts, says Cloudflare. Government sites go offline on purpose. LiteLLM's poisoned update goes out.
- 22 OCTA name sticks"Black October" spreads. eMudhra exits the global certificate business. Some Japanese banks pause services.
The US agencies NSA and CISA told organisations to update right away, or take systems offline if they couldn't.
21 Oct 2026 · ExecutiveGov, SecureWorldDid anyone actually get hacked?
The part most headlines skip.
attempts to get in
"Millions", says Cloudflare's CEOconfirmed break-ins, so far
No successful attack confirmed by Germany, the Netherlands or Japan, as of 23 OctAttempt means someone tried the door. Break-in means they got through.
So why were websites down? Many went offline on purpose, to update safely.
WHAT YOU MIGHT HEAR, AND WHAT'S TRUE
"The internet is going down."
Some sites went offline on purpose, briefly, to patch safely.
"Hackers broke into millions of websites."
Millions of attempts. No confirmed break-in so far.
"My phone got hacked through PHP."
PHP runs on web servers, not on your phone or laptop.
"Indian digital signatures are unsafe now."
eMudhra says DSC, eSign and emSigner carry on as normal.
- CERT-In rated PHP2Shell critical (note CIVN-2026-0510, 21 Oct).
- No Indian government shutdowns or Indian victims have been reported.
- eMudhra, an Indian company, is leaving the global website-certificate business. It says that's about 1% of revenue.
- India's IT ministry pushed back on panic, saying some social media accounts were "indulging in fear mongering" about the eMudhra incident.
- CERT-In warned on 15 Oct that AI agents had read data at Indian organisations, mostly through exposed passwords and over-broad access.
It wasn't just PHP.
Three other security problems landed the same week. That's why the whole thing got one name. Tap each card.
Separate problems, same week. Not one big attack. And nobody knows who said “Black October” first.
So, what should you do?
Pick the one that's you. Tick things off as you go.
-
Copy, paste, send
Hi, please confirm our website's server has the 21 October PHP security update (8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer). If it's on an older PHP version, please upgrade it. Thanks!
All done. You're ahead of most of the internet.
A 14-year-old flaw, found by AI, leaked and attacked within days. Fixed on 21 Oct. No confirmed break-ins so far. Update your stuff.
Sources (32)
- Sam Altman: "I no longer think we're gonna be able to just patch all the bugs" Gizmodo
- Certificate security incident eMudhra (official)
- CERT-In warns AI agents accessed Indian systems The Hacker News
- PHP2Shell vulnerability exploitation Recorded Future
- NSA advisory: critical patches recommended for PHP vulnerabilities NSA (official)
- Vulnerability note CIVN-2026-0510 CERT-In (official)
- Govts, companies take websites offline over PHP vulnerabilities Reuters, via Korea Times
- Cloudflare CEO: 'every single week it's going to feel like the sky is falling' PC Gamer
- What smart people are saying about the 'vulnerability tsunami' Business Insider
- Government websites in the EU and Canada taken offline Engadget
- The PHP bug marks a dangerous new era for the internet Fortune
- Japan PM warns of vulnerabilities in PHP Jiji Press
- eMudhra to exit global SSL/TLS certificate business Business Today
- Anthropic security chief issues stark warning Business Today
- Why eMudhra's exit is not enough (incl. MeitY statement) MediaNama
- LiteLLM hit by second supply chain attack this year Help Net Security
- PHP2Shell patches land as first exploitation attempts hit sensors SecurityWeek
- PHP2Shell vulnerabilities patched Help Net Security
- AI is changing everything about hacking 404 Media
- Millions of exploit attempts, no confirmed breaches The Next Web
- NSA and CISA urge immediate patching ExecutiveGov
- Who found the PHP bug; governments unplug websites Decrypt
- eMudhra certificates' private keys compromised Help Net Security
- eMudhra to exit global SSL/TLS business eMudhra
- Security incident, 21 Oct 2026 LiteLLM
- Brotli decoder flaw behind Node.js issue The Hacker News
- AI agents in bank accounts Axios
- PHP security flaw: which Indian websites are affected Free Press Journal
- CERT-In alert on AI agents Business Standard
- Black October is a disclosure wave Forkast
- Japanese banks pause online services Nippon.com / Jiji
- Usage of PHP for websites W3Techs
Quotes and headlines are reproduced word for word. Facts checked against these sources on 25 Oct 2026.
Did we miss
something?
Spotted a gap, want a part explained differently, or have a headline nobody's explaining? Write to us. We read everything.