Skip to main content

Kaer NewsSoftware

Attackers hit PHP2Shell honeypot four days before patches

Amazon Threat Intelligence detected a PHP2Shell exploit attempt on October 17, four days before patches for two critical PHP vulnerabilities were released on Wednesday, with attacks since reaching millions.

4 min read
Attackers hit PHP2Shell honeypot four days before patchesPhoto: WIRED

Key points

Attackers attempted to exploit two critical PHP vulnerabilities on October 17, four days before patches were released on Wednesday, with exploit attempts reaching millions since disclosure.

Attackers attempted to exploit two critical PHP vulnerabilities on October 17, four days before patches were released on Wednesday, according to Amazon Threat Intelligence. The attempt was detected through MadPot, Amazon's network of honeypots designed to lure attackers. The flaws, tracked as CVE-2026-109618 and CVE-2026-109619, carry a critical 9.2 severity rating and affect PHP's handling of memory, potentially allowing unauthenticated attackers to execute malicious code on vulnerable servers.

The October 17 detection matters because it shows at least one actor was probing the vulnerabilities before any patches existed, leaving administrators with no fix to apply. Amazon's chief information security officer CJ Moses wrote that the targeting of a honeypot from an anonymized IP address suggests the activity was conducted by a threat actor, though it remains unclear how the actor acquired exploit information prior to disclosure. The IP address is linked to a commercial anonymization network, meaning a proxy network or VPN.

What the honeypot found

Amazon analysts spotted the October 17 exploitation on Wednesday while reviewing activity on their honeypots, which are intentionally vulnerable web servers used to study attack methods. Proof-of-concept exploits began emerging publicly on Wednesday, some appearing hours before the public disclosure at 10 am ET. In the hours before disclosure, AWS honeypots were hit with multiple exploitation attempts anonymized using various providers and with various attack goals, likely indicating multiple different actors.

Amazon detected multiple proof-of-concept exploits on October 21, with the earliest appearing around 0200 UTC, some 12 hours before the patches were released. Over the following six hours, further attempts arrived from different anonymized infrastructure using a variety of payloads. Amazon said this points to multiple attackers rather than a single group. Whether any of those attempts would have worked against real-world systems remains unclear, Moses wrote.

Cloudflare recorded a sharp escalation in attacks after disclosure. According to Cloudflare chief executive Matthew Prince, the company spotted thousands of exploitation attempts in the 10 hours before the vulnerabilities were publicly announced. That figure jumped to tens of thousands within 45 minutes of disclosure, hundreds of thousands within two hours, and has since climbed into the millions. Attackers are tweaking payloads to bypass Cloudflare's web application firewall protections, using feedback from blocked requests to work out what might get through.

How attacks scaled after disclosure

Security firm Hadrian reported on October 21 that PHP2Shell was being exploited in the wild at scale. The company said most observed attacks abuse PHP's session upload-progress path, and it expects more exploit paths to appear before and after the fix ships. Cloudflare has deployed web application firewall protections across its free and paid plans but stressed these are no substitute for patching. Amazon is advising organisations to investigate suspicious activity dating back to at least October 17.

The PHP Foundation initially theorised the bug in 2024. Its security team came up with potential solutions, but a fix was delayed due to backward compatibility breaks, new denial-of-service potential, or requiring changes to many third-party extensions which seemed impossible to coordinate. As the Foundation prepared to ship the fix, details about the bugs began trickling out on forums and social media, with some security firms releasing information before the official release.

Elizabeth Barron, the PHP Foundation's executive director, said the organisation was unaware of Amazon's research before publication. She said that although upgrading is absolutely imperative, to the Foundation's knowledge there has been no successful attempt at remote code execution. The Foundation has accused supply-chain security vendor Chainguard of publishing patched PHP builds before the agreed disclosure deadline, putting websites at risk. Amazon's October 17 detection suggests at least one attacker was already trying to exploit the bugs before that incident.

Why the fix took years

Moses wrote that the time from patch to working exploit is shrinking for structural reasons. In the past, most exploitation came after a public proof of concept was released, with a small number of capable actors building exploits others waited for. That dependency is weakening, he wrote, because AI-assisted analysis makes it cheaper to turn a patch diff or advisory into a working exploit, letting more actors act within hours or minutes of disclosure.

The PHP Foundation said it is changing processes so leadership can help steer serious vulnerabilities with hard trade-offs to a timely resolution, and is prioritising measures to ensure vulnerabilities needing similarly complex fixes get resolved faster when reported. Amazon is advising organisations to investigate suspicious activity dating back to at least October 17, rather than assuming their systems were safe until the vulnerabilities became public.

Frequently asked questions

When was the PHP2Shell exploit attempt first detected?

Amazon Threat Intelligence detected a PHP2Shell exploit attempt on October 17, four days before patches were released on Wednesday. The activity was picked up by MadPot, Amazon's network of honeypots, from an IP address linked to a commercial anonymization network.

How many exploit attempts have been recorded since disclosure?

Cloudflare recorded thousands of attempts in the 10 hours before disclosure, tens of thousands within 45 minutes, hundreds of thousands within two hours, and has since climbed into the millions of attempts targeting the two vulnerabilities.

More from this edition