This is a historical snapshot through 25 October 2026, not a live threat feed. Consult the linked sources for later developments.

What happened after the patch

The fixes from 21 October 2026 are unchanged: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35, or a distribution package that backports them. Since then, attackers have tried the bugs, including operators of a Mirai-derived botnet. A same-day Sophos report of a successful compromise was withdrawn. Updating is still the only complete fix.

Checked 2026-10-25. Each figure below is what the linked report says, not a count this site measured. This page has no exploit code, payloads or attack steps.

The short version

ReportWhat it saysWhen
SophosScanning and a few failed attempts. A Mirai-derived payload named Potassium was blocked and not installed. An earlier “successful exploitation” note was withdrawn.22 Oct, correction at 21:21 UTC
Hunt.ioOne operator ran 10 rounds against up to 123 servers. About 57 were running PHP. None was exploited.Activity on 21 Oct, written up 22 Oct
VulnCheckSays its customer exploit for CVE-2026-109618 works on some production builds with ASLR enabled. Not a public proof of concept.23 Oct
UK government, via the BBC32 services unavailable and 4 partly unavailable, largely as a precaution while updates were applied. Not described as a breach.22 Oct
QualysIn its customer data, 110 million installs (71% of those with a known version) were on end-of-life PHP 5.4–8.1. 581,000 were patched in the first 24 hours.23 Oct

Mirai operators joined the attempts

Sophos says it saw attempts to install Potassium, a Mirai-derived botnet it first tracked earlier in 2026. The sample can download further programs and launch denial-of-service traffic. The attempt Sophos analysed was stopped by its own countermeasures, so the payload never landed. At 16:18 UTC on 22 October Sophos had called one case a successful exploitation. At 21:21 UTC it corrected that: customer telemetry showed scanning and a small number of failed attempts, and no successful compromise through these bugs.

Hunt.io ties the scanning it saw to a Mirai-style botnet active since at least May 2026, which added php2shell to the ways it spreads. In captured attacker files, the only mass-exploitation operator it describes ran ten passes, grew a target list from 23 servers to 123, and logged no shells. About 57 of those servers were running PHP, and 10 rejected the request. SecurityWeek summarised the same finding on 23 October: attempts, including this botnet, and no confirmed compromise in the reports it reviewed.

A matching user agent that contains php2shell is one indicator Hunt.io published. It shows an attempt. It does not show that code ran.

Reports of a real compromise do not yet agree

CISA, revising its alert on 23 October, said it had not observed successful exploitation and still urged immediate updates. Organisations that cannot update, or that run PHP 8.1 or older without a vendor fix, should take those systems offline until they can. As of that revision, neither CVE was listed in CISA’s Known Exploited Vulnerabilities catalog; SecurityWeek said the same of the catalog on the morning of 23 October.

Unit 42 describes a different case. In an update on 23 October it says attackers reached a European government entity and, within two hours of initial exploitation, obtained password hashes and multi-factor authentication secrets.The Dutch NCSC, updating the same day, said it knew of one report of a possible exploit abroad and that the attack had not been confirmed as successful. Read the Unit 42 case as a vendor report that a national authority has not confirmed, not as a settled fact and not as evidence of widespread compromise.

ASLR is not a reason to wait

Getting memory corruption is not the same as getting code execution on a hardened server. Hunt.io’s 22 October write-up judged the public code it had reviewed short of reliable execution on ordinary x86-64 hosts.VulnCheck later said that, as of 17:30 ET on 23 October, an exploit it supplies to its own customers reaches code execution for CVE-2026-109618 on PHP 8.4.10 through 8.4.26 and on 8.5.10 and 8.5.11, on AMD64 and ARM64, with ASLR enabled and display_errors off, including a default WordPress container on those versions. Those builds are all older than the fixed releases. VulnCheck also says it is not aware of another public or commercial exploit with that coverage, and that most public repositories which claim an exploit do not work.

This site does not link to exploit code and does not describe how any of those attempts work. The practical reading is that an unpatched server should be updated even if ASLR is on.

Outages were mostly precautionary

On 22 October, tech minister Baroness Lloyd of Effra told the House of Lords that 32 UK government services were unavailable and four were partly unavailable. She said this had largely resulted from precautionary measures while updates and mitigations were applied. The government did not name the services. It said no large UK public-facing critical service had been affected, and that the outages did not mean those services had been hacked. The BBC reported the statement the same day.

Most installs in Qualys’s data were still old

Qualys measured anonymized telemetry from more than 10,000 of its customers, not the whole web. It counted 167 million PHP package installations and said 73% were on internet-facing assets. Among 156 million with a known version:

A header that still shows an older number can already be a patched vendor build. The checker on this site says “check your vendor” for that reason.

What to do

  1. Check the version your site announces, then confirm it on the server with the self-check commands.
  2. Update to 8.5.12, 8.4.27, 8.3.36, 8.2.35 or your vendor’s fixed package, and restart every PHP worker. Guides: pick your environment.
  3. If you cannot update today, apply the temporary mitigations and, where CISA’s advice fits, take the system off the internet until it is fixed.
  4. After the update, look for attempts in your logs. A user agent containing php2shell is a sign you were targeted. It is not, by itself, a sign of compromise.

FAQ

Has php2shell been exploited successfully?

Attackers are trying. On 22 October Sophos withdrew an earlier claim of a successful compromise: the attempt it analysed was blocked, and a Mirai-derived payload was not installed. Hunt.io logged ten attack rounds against up to 123 servers and no shells. CISA’s 23 October update says it has not observed successful exploitation. Unit 42 has described one European government case; the Dutch NCSC, the same day, said that report was not confirmed.

Did a Mirai botnet use these bugs?

Sophos says attackers tried to install Potassium, which it believes is a Mirai-derived botnet, and that its product blocked the attempt before the payload was delivered. Hunt.io attributes scanning it saw to an existing Mirai-style botnet that added these bugs to its kit. Neither report shows a confirmed installation through php2shell.

Were UK government sites hacked?

The government has not described this as a hack. On 22 October a minister told the House of Lords that 32 services were unavailable and four were partly unavailable, largely because of precautionary updates and mitigations. The government said no large UK public-facing critical service was affected.

Does ASLR mean an unpatched server is safe?

No. Address-space randomisation makes reliable code execution harder, and many public demonstrations fail outside a lab. VulnCheck says an exploit it provides to its customers reaches code execution on some unpatched PHP 8.4 and 8.5 builds with ASLR left on. Treat that as a reason to update, not as instructions: this site does not publish exploit code.