Black October explained: what PHP2Shell and the "27 hacks" really mean
Black October was not 27 hacks in 48 hours. What PHP2Shell is, who is affected, how it happened and exactly what to do now.
Three things to know, as of 25 October 2026:
- PHP2Shell is two critical flaws in PHP (CVE-2026-109618 and CVE-2026-109619), patched on 21 October 2026 and now being exploited in the wild.1,3,4
- The viral "27 incidents in 48 hours" list is mostly real items, spread over about three weeks. No source ties them to one attacker.5
- Ask your host to confirm PHP is patched, rotate keys on any affected platform, and ignore emailed "patch" links.

What happened, and who it affects
"Black October" is a label from social media, not an official name. The earliest trace is an X post on 22 October, and no vendor or government advisory uses it. A viral list of about 27 incidents followed. One independent check found 24 of the 27 were real, and that they span about three weeks, not 48 hours.5
The spark was PHP2Shell. Two flaws, each rated 9.2 on the CVSS v4 scale, could let an attacker run code on a server without logging in.2 PHP shipped fixes on 21 October (8.5.12, 8.4.27, 8.3.36 and 8.2.35), a day early because news of the bug leaked.1 Government sites in the Netherlands, Finland, France, Denmark and Germany went offline as a precaution, and so did parts of Wikipedia.6
Two cautions. The "70% of the web" figure is PHP's share among sites whose server language is known, not the share that is vulnerable.7 And the flaws need effort to exploit, so "one click" is wrong.2 That has not stopped attackers: exploitation in the wild is confirmed, and India's CERT-In reports it at large scale.3,4 If you have not patched, treat it as urgent.
Who is affected
- Anyone running PHP, including WordPress, Drupal and Joomla sites. The fix has to come from the PHP runtime, so it is your host's job or yours.
- Developers and AI builders. LiteLLM version 1.107.0 was malicious for under two hours on 21 October.8 Railway says customer keys may have been accessed.9 Zeabur says 321,810 accounts' records were read, and it is shutting down on 31 December 2026.10
- People whose data sat with someone else. SBI confirmed 3,897 customer records containing personal information, within a dark-web dump of about 3.75 lakh records.11 Medi-Cal says more than 970,000 members were hit, in a breach dating to October 2025.12
- Japanese FX traders. Onamae suspended its desktop cloud service, with 26,739 servers potentially affected.13
| Viral claim | What the evidence supports |
|---|---|
| 27 incidents in 48 hours | 24 of 27 were real, spread over about three weeks5 |
| 70% of the web is vulnerable | 70% is PHP's share among sites with a known server language7 |
| AI found PHP2Shell | Two teams found it independently using AI tools; humans did the exploit work and the fix14 |
| A criminal group called Cairn breached 100+ companies | Cairn is an open-source AI agent platform; one actor targeted 100+ company websites15 |
| Zeabur lost 285,369 accounts | 321,810 accounts10 |
How it happened, and how it could have been prevented
Both PHP flaws are memory bugs in how PHP cleans up after a request that fails. They sat in the code for over a decade. A PHP developer noticed the weakness in 2024, but competing fixes stalled, and the PHP Foundation calls that a structural failure.14 In August 2026, Calif and Wiz each found the bugs using frontier AI tools, and humans did the exploit work and the fix. An embargo leak forced the early release.14
Most of the other incidents came down to credentials being in the wrong place:
- LiteLLM: stolen GitHub tokens let an attacker redirect the release pipeline.8
- Zeabur: an admin token that never expired.10
- UpdraftCentral: stolen management keys used to push backdoor plugins to WordPress sites.16
AI on offence is documented in one well-reported case: one actor used the open-source Cairn agent platform against more than 100 company websites, at an estimated $50 per successful break-in.15
What would have helped
- Treat hard-to-exploit memory bugs as security issues, and fuzz error paths.
- Audit critical open-source code with AI before attackers do.
- Use short-lived, narrowly scoped tokens, and keep them out of logs.
- Lock down release workflows, and wait a day or two before installing brand-new package versions.
- Patch fast.
This list is our own analysis, not a published finding.
What to do now
If you run a website
- Find out which PHP version your host runs for your site, and ask the host in writing to confirm the fix.
- Updating WordPress, plugins or themes does not fix PHP2Shell.
- If you control PHP, move to a fixed release (8.5.12, 8.4.27, 8.3.36 or 8.2.35) and restart PHP-FPM and your web server.1
- Set
session.upload_progress.enabled=0. It is the interim protection for a third flaw, CVE-2026-115560, which has no fix yet.17 - Look for unknown admin users, new plugins and odd files, going back to 17 October. Patching does not remove a backdoor.
- Turn on two-factor sign-in for your host, domain registrar, email and WordPress admin.
If you build software
- Rotate every key stored on Railway or Zeabur, starting with AI-provider keys, and set spend caps.9,10
- If you installed LiteLLM 1.107.0, treat the machine as breached and rebuild on 1.106.2.8
If you are just visiting websites
- Your phone and laptop are not infected by visiting an affected site. Leave any page that behaves oddly.
- Ignore emails or texts telling you to apply a patch or log in to your host.
In India
- CERT-In's note CIVN-2026-0510 lists fixed versions for PHP 8.2 to 8.5 only. That does not mean 7.x, 8.0 and 8.1 are safe.3
- SBI customers should treat unexpected calls or texts about a loan or account as suspect, and never share an OTP or PIN.
Questions people are asking
Is PHP2Shell being exploited? Yes. Exploitation in the wild is confirmed, and India's CERT-In reports large-scale exploitation.3,4 Patch now.
Was Black October one coordinated attack? No source shows that. Analysts describe a wave of disclosures, not one campaign.5
Is PHP2Shell fully fixed? Not yet. A third flaw, CVE-2026-115560, was disclosed on 23 October as an informational advisory and has no patch. PHP will fix it in its regular bugfix release rather than an emergency one. Until then, set session.upload_progress.enabled=0.17,18
Do I need to change my passwords? Only if you used an affected platform or suspect a break-in. Rotate keys first, then passwords.
Facts are current to 25 October 2026. This is a fast-moving story; the sources below carry the latest.
Want a second pair of eyes on your exposure? Book a scoping call.
Sources
- PHP project, 2026 news archive: security releases and advisories.
- Rapid7, analysis of CVE-2026-109618 and CVE-2026-109619 (October 2026).
- CERT-In, vulnerability note CIVN-2026-0510 (updated 24 October 2026).
- Huntress, rapid response on the PHP2Shell vulnerabilities (October 2026).
- State of the Future, reality check on the "Black October" list (October 2026).
- Reuters via The Daily Record, government websites taken offline after the PHP flaw (21 October 2026).
- Insurance Business, on the PHP2Shell warnings and the 70% figure (October 2026).
- LiteLLM, security incident report, 21 October 2026.
- Railway, security disclosure, 21 October 2026.
- Zeabur, October 2026 security incident report.
- Internet Freedom Foundation, on SBI's filing and the 3,897 affected customers (October 2026).
- SecurityWeek, Medi-Cal members affected by the Paradigm breach (October 2026).
- Onamae, Desktop Cloud service notice (October 2026).
- The Next Web, on the PHP Foundation and the 2024 miss (October 2026).
- Reuters via the Honolulu Star-Advertiser, one hacker, AI agents and 100+ company websites (19 October 2026).
- Patchstack, UpdraftCentral key compromise and WordPress backdoors (October 2026).
- Threat Landscape, PHP CVE-2026-115560 advisory (October 2026).
- CERT-EU, security advisory 2026-018 (October 2026).