Php2shell Attacks Hit Check Point Gateways With Wiper

Php2shell Attacks Hit Check Point Gateways With Wiper

Attackers used PHP2Shell flaws to get into Check Point gateways and ran a wiper on a host running VMware ESXi during the initial attacks targeting Israeli organizations, Check Point reports. A later round of attacks hit organizations in several countries, but Check Point saw no destructive activity in those attacks.

How the php2shell Attacks Reached Internal Systems

PHP2Shell is the name for CVE-2026-109618 and CVE-2026-109619, two critical flaws that let attackers run code remotely on an affected system. The affected PHP releases go back to PHP 5. Patches came out on October 21. Attackers were already exploiting the flaws by then, and widespread attacks followed not long after. Check Point gave this account of what happened once attackers got into the gateways.

  • Attackers used PHP2Shell to get into the affected appliances.
  • A local privilege-escalation flaw in DynamicCLI, CVE-2026-123039, let attackers get root access, giving them the highest level of access on the system.
  • Attackers placed PHP webshells—scripts that take commands from attackers—in a directory where Mobile Access builds portal login pages.
  • TSGA and TSProxy gave attackers a backdoor into the systems and let them intercept network functions.
  • Attackers found internal assets, moved onto a host running VMware ESXi and ran a wiper, then left a note that mentioned Dream Security.

TSGA and TSProxy are versions of PhiliKit, a malware framework that had previously been linked to attacks on Ivanti products by China-linked UNC5221. Check Point said the break-ins involving Mobile Access happened in late October.

TimingEventAffected scope
Before October 21Exploitation beganPHP2Shell vulnerabilities
October 21Patches releasedPHP2Shell vulnerabilities
October 30Destructive wave beganIsraeli organizations
November 2Later wave beganOrganizations in multiple countries

Who Was Behind either Wave Is Still Unclear

Dream has said Chinese hackers were tied to PHP2Shell attacks against Palo Alto Networks firewalls. That security firm was mentioned in the note left behind during the attacks against Check Point. Check Point also said the timing of the activity matched working hours in China, while the malware and infrastructure had links to China. But that was not enough to say who carried out the destructive attacks. Check Point said running a wiper was out of line with what is known about Chinese cyber operations. The same actor could have done everything, or another actor could have supplied the initial access; the attacks could also have been a false-flag operation, or the destruction could have been an attempt to cover up other activity.

The next round of attacks reached Check Point Security Gateways worldwide, including those at Israeli organizations hit in the earlier round.

No particular industry seemed to be the focus of either round. Check Point said that pattern suggested the attackers were getting into systems wherever they found an opportunity.

FAQ

Which systems are affected?

The PHP releases affected by PHP2Shell go back to PHP 5. Reports named Check Point’s Mobile Access and Security Gateways among the targets.

When were patches released?

PHP2Shell patches were released on October 21. The flaws were already being exploited before that date, and attacks became widespread soon afterward.

What signs of the reported attacks can defenders look for?

Check Point said it found PHP webshells where Mobile Access builds login pages, as well as TSGA and TSProxy, and reported that attackers searched for internal assets and moved onto a host running VMware ESXi.

Was there wiping in the worldwide wave too?

Check Point said it saw no destructive activity during the round of attacks that began on November 2. The wiper was reported in the earlier round targeting Israeli organizations.

Subscribe to our weekly news digest.

Join now and become a part of our fast-growing community.

Invalid Email Address
Thanks for Subscribing!
We'll be sending you our best soon!
Something went wrong, please try again later