Amazon detects PHP2Shell exploit attempts four days before patches
Amazon Threat Intelligence found the first PHP2Shell exploit attempt on October 17, four days before patches for two critical PHP flaws were released on October 21, as attacks climbed into the millions.
Photo: WiredKey points
Amazon Threat Intelligence detected an attempt to exploit the PHP2Shell vulnerabilities on October 17, four days before patches were released on October 21, with attacks since climbing into the millions.
Amazon Threat Intelligence detected an attempt to exploit two critical PHP vulnerabilities on October 17, four days before security patches were released on October 21. The flaws, tracked as CVE-2026-109618 and CVE-2026-109619 and collectively known as PHP2Shell, let unauthenticated attackers execute malicious code on vulnerable servers. Amazon's chief information security officer CJ Moses said PHP2Shell is now being broadly exploited across the internet.
The detection matters because it shows exploitation began before the vulnerabilities were publicly disclosed, breaking the usual pattern where attacks follow a public proof of concept. Amazon's honeypot network, called MadPot, captured the October 17 attempt from an IP address linked to a commercial anonymization network. Moses wrote that the targeting of a honeypot from an anonymized IP address suggests a threat actor was involved, though how the actor obtained exploit information before disclosure remains unclear.
Why the flaws matter
Both vulnerabilities carry a critical 9.2 severity rating and affect how PHP handles memory, potentially allowing unauthenticated attackers to run malicious code on vulnerable servers. Unlike flaws in individual plugins or applications, these bugs affect the PHP runtime itself, putting a potentially enormous number of websites at risk regardless of which content management system they use. PHP powers up to 80% of all websites, including those running WordPress, Drupal, and Joomla.
The PHP security team patched the flaws on October 21 after urging administrators one day earlier to prepare to install updates as soon as they became available. PHP core developer Gina Peter Banyard warned before disclosure that applying the official security patches is the only permanent defence. The UK National Cyber Security Centre asked UK organisations to immediately update PHP servers or take them offline until they can be patched.
Cloudflare recorded thousands of exploitation attempts in the 10 hours before the vulnerabilities were publicly announced, according to CEO Matthew Prince. 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 tweaked their payloads to sneak past Cloudflare's web application firewall protections, apparently using feedback from blocked requests to work out what might get through.
How the attacks scaled
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.
Security firm Hadrian reported on October 21 that PHP2Shell was being exploited in the wild at scale, noting that most observed attacks abuse PHP's session upload-progress path. The PHP Foundation has accused supply-chain security vendor Chainguard of putting websites at risk by publishing patched PHP builds before the agreed disclosure deadline. Amazon's October 17 detection suggests at least one attacker was already trying to exploit the bugs before that incident.
Amazon advises organisations to investigate suspicious activity dating back to at least October 17, rather than assuming their systems were safe until the vulnerabilities became public. Cloudflare has deployed web application firewall protections across its free and paid plans but stressed these are no substitute for patching. Moses warned that defenders should not assume the public disclosure date is the earliest date of exploitation.
Frequently asked questions
When did the PHP2Shell exploitation attempts begin?
Amazon Threat Intelligence detected the first exploit attempt on October 17, four days before the PHP security team released patches on October 21. The attempt came from an IP address linked to a commercial anonymization network, caught by Amazon's MadPot honeypots.
How many exploit attempts have been recorded?
Cloudflare recorded thousands of attempts in the 10 hours before disclosure, tens of thousands within 45 minutes of disclosure, hundreds of thousands within two hours, and has since seen attempts climb into the millions.


