🔍 Read the full analysis: Could AI Have Helped With The PHP2Shell Chain? A Palo Alto Case Study on ThorstenMeyerAI.com
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Dream reported that an attacker used PHP2Shell and a previously disclosed Linux kernel flaw to gain root access on 24 Palo Alto Networks firewalls, then compromised a related management server. Dream found AI tools on the attacker’s systems but said it has no direct evidence that AI wrote the exploit or scripts. The case highlights the risks of internet-exposed management interfaces and delays before patched PAN-OS builds became available.
Researchers at Dream say an attacker used two software flaws to gain root access on 24 Palo Alto Networks PAN-OS firewalls and then compromise a connected server inside a U.S. government-affiliated network. Palo Alto Networks says its Unit 42 team independently verified the attacker’s tools and results. Dream found AI tools on the attacker’s systems, but says it has no direct evidence that AI created the exploit or attack scripts.
Dream’s account says the attacker began an automated campaign on the evening of October 23, about two days after the PHP project released fixes for the PHP2Shell flaws. The campaign targeted 240 firewalls and gained root access on 24, according to the company. The targets were in the United States, Japan, Taiwan and South Korea. Dream says 22 compromised firewalls were left with a hidden web shell, while two were associated with the U.S. government-affiliated organization.
Those two firewalls provided a route into the organization’s network. On October 24, the attacker used a tunnel through one of them to reach the organization’s internal firewall management server, which Dream counts as the 25th compromised server. Dream says the attacker then targeted Active Directory, the system used to manage identities and access. The report does not establish the extent of any resulting access to user accounts or data.
The chain combined PHP2Shell, identified as CVE-2026-109618 and CVE-2026-109619, with Fragnesia, a Linux kernel privilege-escalation flaw identified as CVE-2026-46300 and publicly disclosed in May. Dream says PHP2Shell initially allowed code execution with limited privileges, while Fragnesia helped the attacker obtain root access. The company estimates the attack chain, including installation of a persistent back door, could take under 15 minutes; that timing is Dream’s assessment, not a general measure of how quickly all systems could be compromised.
Infographic 01 · PHP2Shell on Palo Alto firewalls
Two days from patch to root.
PHP fixed the bug on 21 October. Fixed firewall software for the attacked branches arrived almost a week later. The attack ran in between.
- 13–23 MayFragnesia goes public, kernel fix followsLinux privilege-escalation bug with a public exploit; CVE-2026-46300.
- 8 OctAttacker sets up an AI platformaiscan configured with DeepSeek and Kimi, per Dream’s timeline.
- 21 OctPHP fixes PHP2ShellPHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. Palo Alto advisory the same day; PAN-OS fixes “upcoming”.
- 23 Oct, evening UTCBatch run: 240 targets, 24 rootedFound via device search engine, filtered to US, Japan, Taiwan, South Korea.
- 24 OctInto a government-affiliated networkTunnel, persistence, internal management server rooted (no. 25), Active Directory attacked.
- 26 OctDream publishes · CISA lists PHP2ShellFederal deadline 29 Oct.
- 27–29 OctFixed PAN-OS builds for 12.2 and 12.1CISA lists Fragnesia on 28 Oct; Unit 42 confirms Dream’s results on 29 Oct.
The fix for PHP existed. The fix for the firewall did not, yet. The open management page was the only door that mattered.Thorsten Meyer · my reading
Sources: Dream Research, 26 Oct 2026 (updated 29 Oct); php.net, 21 Oct 2026; Palo Alto Networks advisory (updated 29 Oct 2026); CISA KEV catalog, version 29 Oct 2026; oss-security, 13 May 2026; Unit 42, 29 Oct 2026. Day count: Thorsten Meyer.
Powered by Thorsten Meyer AI
Exposed Management Pages Raised Risk
The reported campaign shows how a recently patched application flaw can pose an immediate risk when an internet-facing management interface is reachable and a second, already disclosed flaw can elevate access. Dream says its search and filtering process narrowed an initial set of roughly 19,000 internet-exposed management pages to 240 targets, using device-search results, version information, countries and software versions. Those figures describe the researchers’ reported discovery and selection process; they are not a count of all vulnerable or compromised firewalls.
For organizations, the case puts emphasis on limiting access to administrative interfaces, applying vendor updates promptly, and checking systems for signs of persistence after a compromise. Palo Alto Networks’ advisory appeared on October 21, but fixed builds for the affected PAN-OS 12.1 and 12.2 branches were released between October 27 and 29, according to the source account. Until fixes were available, the stated mitigation was to keep the management interface off the public internet. A device that has been compromised may require investigation beyond simply installing an update.
The AI angle matters because the attacker’s systems reportedly contained tools associated with coding and offensive security. But the evidence described by Dream does not show that an AI model generated the exploit, selected the targets, or ran the campaign. The confirmed practical concern is the attack chain and the systems exposed to it; AI’s contribution remains an open question.
Products Worth Considering
Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
LG UltraGear 27-Inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1
As an affiliate, we earn on qualifying purchases.
From May Kernel Bug to October Campaign
Fragnesia was disclosed in May 2026 with a public exploit and a kernel fix, according to the source material. Dream’s timeline says the attacker configured an offensive-security platform called aiscan on October 8, with DeepSeek and Kimi models. PHP released updates on October 21 for several PHP branches and urged users to update. Palo Alto Networks also issued an advisory that day, with fixed PAN-OS builds still forthcoming.
Dream says it identified about 19,000 PAN-OS firewalls with management pages exposed to the internet through FOFA, a search service for internet-connected devices. A custom scanner returned version information for about 5,000, after which the researchers say country and version filters reduced the campaign’s target list to 240. The attack was conducted in automated batches, according to the report. On October 26, the U.S. Cybersecurity and Infrastructure Security Agency added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog and set a three-day deadline for federal agencies, the source material says.
Dream published its findings on October 26 and updated them on October 29. Palo Alto Networks’ Unit 42 independently verified the attacker’s tools and results, according to the supplied account. The report describes a particular campaign against PAN-OS devices; it does not establish that every device running the affected software was targeted or compromised.
““no direct evidence””
— Dream
AI’s Role Remains Unverified
The available account does not show whether the attacker used Claude Code, DeepSeek or Kimi to write, modify or troubleshoot any part of the exploit chain. Dream says it found Claude Code installed and DeepSeek and Kimi configured in aiscan, but tool presence alone does not establish how they were used. Dream also says the operation did not appear fully autonomous.
It is not clear from the supplied material whether the attacker obtained data, created additional access beyond the reported back doors, or maintained access after the campaign was discovered. The extent of the Active Directory targeting, the identities of the affected organizations beyond the government-affiliated network, and the full number of exposed devices that were vulnerable are also not specified. Palo Alto’s reported verification supports the account of tools and results, but further technical details and independently published findings could change what is known.
Patch, Restrict, and Investigate
Organizations using affected PAN-OS branches should consult Palo Alto Networks’ current advisories and install the applicable fixed builds. Where a fix is not yet installed, the source account identifies restricting management access from the public internet as a mitigation. Administrators should also review exposed management interfaces and investigate devices for unauthorized accounts, web shells or other signs of persistence, following vendor and incident-response guidance.
Federal agencies were given a three-day remediation deadline after CISA added the PHP2Shell CVEs to its exploited-vulnerability catalog, according to the supplied timeline. The next useful evidence will be further vendor, government or incident-response updates on affected versions, the scope of the network intrusion, and any confirmed use of AI tools during the operation. Until then, the AI connection should be treated as a reported observation and an unresolved attribution question, not proof that AI built or executed the chain.
Key Questions
What was PHP2Shell used for in this campaign?
Dream says the PHP2Shell flaws allowed the attacker to run code on targeted firewalls with limited privileges. The attacker then chained that access with the Fragnesia Linux kernel flaw to obtain root access, according to the report.
Did AI write the exploit?
That has not been established. Dream found AI-related tools on the attacker’s systems but said it had no direct evidence that AI wrote the exploit or scripts.
How many systems were reportedly compromised?
Dream reported root access on 24 PAN-OS firewalls and access to one internal firewall management server, for 25 servers in total. The report says the targets were in four countries.
What should PAN-OS administrators do?
Check Palo Alto Networks’ advisories for the applicable fixed release and install it. The source account also says management interfaces should not be exposed to the public internet; organizations should investigate potentially affected devices for persistence rather than assuming an update alone removes it.
Was the organization’s Active Directory compromised?
Dream says the attacker went after the organization’s Active Directory after reaching its internal firewall management server. The supplied material does not specify whether accounts or directory data were successfully taken over.
Source: ThorstenMeyerAI.com
