What PHP2Shell Is and Why It’s Different
PHP powers a large share of the internet. WordPress, government portals, banking platforms, and business websites often run on it. That makes PHP vulnerabilities particularly high-value targets.
PHP2Shell refers to two vulnerabilities in the PHP runtime engine , the actual execution environment that runs PHP code, not in any specific website or application built on top of it.
The two CVEs are:
- CVE-2026-109618 , exploits a memory corruption bug that occurs when PHP handles out-of-memory conditions during multipart HTTP request processing
- CVE-2026-109619 , exploits stale global state that PHP carries between requests under certain conditions
Both carry a CVSS v4.0 score of 9.2 (Critical), and both allow an attacker to execute code on the target server remotely without needing any login credentials. CISA added both vulnerabilities to its Known Exploited Vulnerabilities catalog after confirmed cases of exploitation in the wild.
The key detail , the one CYFIRMA specifically flags , is that the flaw sits in the PHP engine itself, not in WordPress, Drupal, or any other PHP-based application. Updating a website’s plugins, themes, or CMS version will not close this vulnerability. The PHP core itself must be patched.
The Dark Web Chats CYFIRMA Obtained
CYFIRMA’s advisory , published October 29, 2026 under reference CYF-FS-2026-1029-PHP2SHELL-DPRK , describes monitoring a closed anonymous network where Korean-speaking operators discussed specific attack targets.
The communications were on what appears to be I2P (Invisible Internet Project), a type of hidden network similar in purpose to the Tor-based dark web but specifically designed for internal service communication within criminal groups. CYFIRMA also tracked the campaign under the internal designation “June 2026 Minjun.”
On October 28, the hackers explicitly named promising IP ranges in South Korea, Japan, the United States, Thailand, Indonesia, and India. CYFIRMA subsequently obtained a target list of 216 servers across 10 countries that the group had compiled for potential exploitation.
The breakdown by country:
- United States: 49 servers
- Japan: 47 servers
- India: 31 servers
- South Korea: 30 servers
- Plus targets in Australia, Taiwan, Singapore, Thailand, Indonesia, UAE, Saudi Arabia, and the EU
Appearing on the list doesn’t confirm those servers were breached. CYFIRMA stated it had not confirmed any actual damage at time of reporting.
The hackers operated through 21 compromised IP addresses used as scanning nodes , a technique that obscures their real origin while probing thousands of potential targets. This is the same approach we’ve documented in looking at how dark web early warning signals appear before attacks become public.
Why This Points to Lazarus Group
CYFIRMA rates its attribution to the Lazarus Group ecosystem at moderate confidence , not a definitive claim, but grounded in multiple overlapping indicators.
The operators communicated in Korean. The target list prioritised government agencies and financial institutions, which align directly with Lazarus’s documented focus on financial theft and espionage rather than random opportunistic attacks. The technique , planting web shells to maintain persistent remote control , matches Lazarus’s historical use of PHP web shell tradecraft documented in multiple past campaigns.
Lazarus Group operates under North Korea’s Reconnaissance General Bureau (RGB), the intelligence organisation responsible for clandestine offensive operations. The group is also tracked under names including APT38, HIDDEN COBRA, ZINC, and Diamond Sleet. MITRE ATT&CK catalogues them as group G0032.
Their financial motivation is well documented. Lazarus is linked to some of the largest cryptocurrency thefts in history, including the $235 million WazirX exchange hack in 2024, and is estimated to have stolen billions in digital assets to fund North Korea’s weapons programme.
The targeting of South Korea, Japan, and the United States , countries representing significant diplomatic and economic relationships , fits a campaign with both financial and espionage objectives rather than purely opportunistic mass exploitation.
The Seven Sectors Being Targeted
The hackers weren’t casting a wide net randomly. CYFIRMA’s report identifies seven sector categories that the operators specifically prioritised in their target countries:
Government agencies. Banks and financial institutions. Telecommunications. Critical infrastructure. Logistics and aviation. Manufacturing. Online trading platforms.
The concentration on government and financial sectors as “Tier 1” targets is consistent with both financial theft at scale (extracting funds from banks, manipulating trading platforms) and espionage (accessing government communications, policy documents, and intelligence).
This is exactly the type of infrastructure targeting that South Korea’s 700-billion-parameter security AI project, backed by S2W and Naver Cloud, was specifically designed to detect and respond to , the same government and financial sectors that the dark web intelligence layer is built to protect.
The South Korean Government Response
South Korea’s Ministry of Science and ICT and the Korea Internet & Security Agency (KISA) issued a formal “caution” alert for the PHP2Shell vulnerability and distributed security response guidelines to businesses and government institutions across the country.
This institutional response indicates that the South Korean government treated the CYFIRMA intelligence as credible and actionable, not as a theoretical risk.
Japan similarly sits in the crosshairs. With 47 servers on the target list, Japan is the second-most targeted country. Japan’s Active Cyber Defense Law and the Fujitsu-KELA security partnership that launched this year specifically to handle exactly this category of threat , government and critical infrastructure targeting through dark web-coordinated campaigns , are facing a real test.
What Server Operators Must Actually Do
CYFIRMA’s patching advice is specific, and the specific part is what most general guidance misses.
Step 1: Patch PHP core. The fix is available in PHP 8.2.35, 8.3.36, and 8.4.27. These are not application patches , they are patches to the PHP runtime engine itself.
Step 2: Fully restart all web-related processes. Applying the patch without restarting leaves old PHP processes in memory that may still carry the vulnerable state. A full restart is required, not just a service reload.
Step 3: Monitor logs for the specific attack signature. Look for abnormal multipart HTTP requests in PHP worker and web server logs. Check web root directories for newly created PHP files. Watch for abnormal shell processes spawned by PHP processes.
Operators running PHP-based government portals, banking platforms, or telecoms infrastructure who assume a CMS update resolves this are still exposed. The flaw is in the layer underneath everything those applications run on.
Frequently Asked Questions
What is PHP2Shell?
Two critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619) in the PHP runtime engine itself that allow remote code execution without a password.
Who is Lazarus Group?
A North Korean state-sponsored hacking group linked to the Reconnaissance General Bureau, known for large-scale financial theft and espionage campaigns.
How confident is the attribution to Lazarus?
CYFIRMA rates attribution to the Lazarus Group ecosystem at moderate confidence — not confirmed, but supported by Korean-language communications, target selection, and tactics consistent with Lazarus’s historical methods.
How many servers were targeted?
216 servers across 10 countries, with the US (49), Japan (47), India (31), and South Korea (30) as the top four.
Will updating WordPress fix this?
No. The vulnerability is in the PHP core, not in website applications. The PHP engine itself must be patched to version 8.2.35, 8.3.36, or 8.4.27 or later.
What sectors are at risk?
Government agencies, banks and financial institutions, telecommunications, critical infrastructure, logistics and aviation, manufacturing, and online trading platforms.