TechnologyNewsDeveloping story

AWS detected PHP2Shell exploit attempt four days before public disclosure

Amazon says its security telemetry recorded an attempt to exploit critical PHP flaws on October 17, before fixes were released. It remains unclear how the actor learned of the flaws.

Amazon Web Services office building at CityCentre Five in Houston, Texas.
File photograph of the Amazon Web Services office at CityCentre Five in Houston, Texas, taken in 2019. Tony Webster from Minneapolis, Minnesota, United States — AWS - Amazon Web Services Office in Houston, Texas (46600198075), Tony Webster (resized and converted to WebP). CC BY 2.0.Image sourceImage licence: CC BY 2.0
WhatsAppXLinkedInEmail
Save for later

Amazon Web Services said on October 21 that its threat monitoring system recorded an attempt to exploit critical PHP vulnerabilities on October 17, four days before the flaws were publicly disclosed and fixes were released. The early attempt means security teams checking for PHP2Shell activity may need to examine records from before the public alert.

The attempt targeted MadPot, an AWS system designed to attract malicious activity, and came from an IP address associated with a commercial anonymization network. AWS chief information security officer CJ Moses said that combination suggested a threat actor, but it was unclear how the actor obtained exploit information while the flaws were under embargo. AWS said it could not tell whether any of the attempts it observed would have succeeded against a real-world system.

Attempts appeared before the PHP fixes

The two vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619, were due to remain under embargo until October 21 at 14:00 UTC, according to AWS. Its team also found multiple proof-of-concept exploits on October 21, the earliest at about 02:00 UTC, and further attempts against MadPot between 02:00 and 08:00 UTC. The payloads and anonymization services varied, which AWS said suggested more than one actor was involved.

PHP developers released fixes on October 21 and urged users to update immediately, Reuters reported. AWS advised security teams investigating possible PHP2Shell activity to look back at least as far as October 17, the date of its earliest observed attempt. That date marks an attempt against AWS's monitoring system, rather than a confirmed breach of a website or service.

Reported attempts surged after disclosure

Cloudflare chief executive Matthew Prince said the company's network saw thousands of exploitation attempts in the 10 hours before the public announcement, according to Reuters. He said the count rose to tens of thousands within 45 minutes of the announcement, hundreds of thousands within two hours and then millions. Those figures describe attempts across Cloudflare's network; they do not establish that the attacks succeeded.

Some companies and governments took sites or services offline as a precaution while fixes were applied, Reuters reported. Finland's government IT provider Valtori said its service interruptions were not caused by exploitation of the vulnerabilities or by a cyber breach, and that it was unaware of active exploitation of the flaws affecting its systems.

Elizabeth Barron, executive director of the PHP Foundation, told WIRED the organization had not known about AWS's findings before they were published and did not immediately have a comment on them. WIRED reported that the foundation knew of no successful remote-code-execution attempt. AWS said its technical analysis was continuing.

Read in depth: Technology

Sources and context

AI-assisted article checked against the listed sources. NewsJaws did not conduct interviews or attend the reported events.

Topics in this story

About NewsJaws Desk

AI-assisted reporting and explainers reviewed against the linked source documents. No claim of on-scene reporting or original interviews.

More from NewsJaws Desk

More from Technology

See all