🔍 Read the full analysis: Inside The “AI-Assisted” Claim In The Palo Alto PHP2Shell Attack on ThorstenMeyerAI.com
Get the latest gadgets 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 says an attacker used PHP2Shell flaws and a previously disclosed Linux kernel bug to gain root access on 24 Palo Alto Networks firewalls, then compromised an internal management server. Dream found AI tools on the attacker’s infrastructure but said it has no direct evidence they generated the exploit or scripts; Palo Alto’s Unit 42 independently verified the tools and results.
Security company Dream reported that an attacker compromised 24 Palo Alto Networks firewalls and an internal management server in a campaign using PHP2Shell flaws, then sought access to the victim organization’s Active Directory. Dream said the attacker’s systems contained AI tools, but it has no direct evidence that AI wrote the exploit or attack scripts; Palo Alto Networks said its Unit 42 researchers independently verified the attacker’s tools and results.
Dream’s account says the attacker began an automated campaign on the evening of October 23, targeting 240 firewalls. The targets were in the United States, Japan, Taiwan and South Korea. Dream says 24 firewalls were rooted, meaning the attacker gained the highest level of system access. On October 24, the attacker used two firewalls belonging to a US government-affiliated organization to reach an internal server that manages the organization’s firewalls. Dream counts that server as the 25th compromised system.
The reported intrusion chained the two vulnerabilities known as PHP2Shell—CVE-2026-109618 and CVE-2026-109619—with Fragnesia, a Linux kernel privilege-escalation flaw, CVE-2026-46300, disclosed in May. According to Dream, PHP2Shell allowed commands to run under a low-privilege account on the firewall; Fragnesia then helped the attacker gain root access. Dream says the attack chain, including installation of a persistent back door, took less than 15 minutes. These technical details are the company’s account, not a separate reconstruction in the source material.
Dream said 22 of the 24 rooted firewalls were left with a hidden web shell. It also reported that the attacker tunneled from the government-affiliated firewalls into the internal management server and then targeted Active Directory, which controls access to network accounts and resources. The source material does not state whether the attacker succeeded in taking over Active Directory or accessed, copied or changed data.
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 Expanded the Breach
The incident illustrates how an internet-reachable administrative interface can turn a vulnerability in a security appliance into a route deeper into an organization. A firewall’s management page can control network rules and other devices; in this case, Dream says the attacker used compromised firewalls to reach a server responsible for managing them. That expanded the reported impact beyond the perimeter devices themselves.
The timing also matters. PHP released patched versions on October 21, and Palo Alto Networks published an advisory that day, but Dream says fixed PAN-OS builds for the affected 12.1 and 12.2 branches arrived between October 27 and 29. Until a fix was available, Palo Alto’s guidance was to keep the management interface off the internet. The reported campaign began two days after the advisory and before those branch fixes shipped, highlighting the exposure organizations face when a vulnerability is known but their affected product does not yet have a patch.
The “AI-assisted” label is less settled than the reported compromises. Finding AI products on an attacker’s systems can indicate tools available to that operator, but it does not establish that those tools created or ran the exploit. For defenders, the documented access path and the security controls around exposed management systems are more concrete than assumptions about the attacker’s use of AI.
Products Worth Considering
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
Amazon Kindle Paperwhite (12th Generation, 2024), 16 GB, 7-inch Display, Jade
Samsung 27 Odyssey OLED G5 (G50SF) QHD QD-OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Patch Dates and the Reported Attack Chain
Dream’s timeline says Fragnesia was disclosed in May 2026, with a public exploit and a kernel fix. The attacker reportedly set up the offensive-security platform aiscan on October 8, configuring it with the Chinese AI models DeepSeek and Kimi. Dream says that, before the October 23 campaign, the attacker identified about 19,000 PAN-OS firewalls with internet-facing management pages, obtained version information from roughly 5,000, and narrowed the list to 240 targets. Those counts describe Dream’s reconstruction; the source does not provide an independent audit of the scanning process.
On October 21, the PHP project released updates to several supported PHP branches. Palo Alto Networks published its PAN-OS advisory the same day, with fixed builds still forthcoming. Dream says it found evidence of the campaign on October 25 and published its report on October 26, updating it October 29. The US Cybersecurity and Infrastructure Security Agency added both PHP2Shell vulnerabilities to its Known Exploited Vulnerabilities catalog on October 26 and gave federal agencies three days to act, according to the supplied source.
The product-specific issue was that PAN-OS included its own PHP copy; updating a separate PHP installation would not by itself patch that embedded component. Dream identifies the included version as PHP 8.0.30. The supplied account says fixed PAN-OS builds for versions 12.1 and 12.2 shipped from October 27 through October 29. Palo Alto’s recommendation before those fixes became available was to restrict management access rather than leave the interface reachable from the public internet.
““no direct evidence””
— Dream
AI’s Role Remains Unverified
How the attacker used AI, if at all, is not established. Dream found Claude Code installed and DeepSeek and Kimi configured in aiscan, but said it had no direct evidence that AI tools produced the exploit or scripts. It also said the operation did not appear fully autonomous. The source material does not include the underlying server artifacts or a detailed analysis from Unit 42 that would clarify whether the tools contributed to planning, coding, scanning or another task.
Other parts of the impact remain open as well. Dream reports that the attacker went after Active Directory, but the supplied account does not confirm whether that system was compromised or what information, if any, was accessed or removed. It also does not identify the affected organization by name or state whether all 24 firewall owners were notified. The source says fixes shipped for the affected 12.1 and 12.2 branches by October 29, but does not provide a full list of affected builds or say how many exposed devices have since been patched.
Patch Status and Intrusion Findings
Organizations using affected PAN-OS versions should check Palo Alto Networks’ current advisory for the applicable fixed build and confirm whether management interfaces were exposed to the internet. The immediate priorities described in the source are to apply the vendor’s update and review systems for signs of compromise, including unauthorized persistent access. CISA’s catalog entry and deadline also put federal agencies under a specific remediation timetable.
Further clarity depends on updates from Dream, Palo Alto Networks, CISA or the affected organization. Those updates could establish whether Active Directory access succeeded, what data or accounts were affected, and whether investigators found evidence tying AI tools to any part of the attack. Until such evidence is reported, the supported conclusion is narrower: Dream documented AI tools on the attacker’s systems, while the role they played remains unconfirmed.
Key Questions
What happened in the PHP2Shell attack?
Dream says an attacker chained PHP2Shell vulnerabilities with the Linux kernel flaw Fragnesia to gain root access on 24 Palo Alto Networks firewalls. The attacker then used firewalls belonging to a US government-affiliated organization to reach an internal management server.
Does the report prove that AI created the exploit?
No. Dream found Claude Code installed and DeepSeek and Kimi configured on the attacker’s systems, but said it had no direct evidence that AI wrote the exploit or scripts. The tools’ specific role remains unclear.
Were the vulnerabilities patched?
The PHP project released fixes on October 21. According to the supplied account, Palo Alto Networks’ fixed PAN-OS builds for affected 12.1 and 12.2 branches shipped between October 27 and 29. Organizations should consult the vendor’s advisory for their exact version and remediation steps.
Was Active Directory compromised?
Dream says the attacker targeted the organization’s Active Directory after reaching an internal firewall management server. The supplied report does not confirm whether the directory was taken over or whether data was accessed or removed.
What should administrators do?
Check the current Palo Alto Networks advisory, install the fixed PAN-OS build that applies to the device, and restrict management access from the public internet. Administrators should also investigate for unauthorized access and persistence, following vendor and agency guidance.
Source: ThorstenMeyerAI.com
