SOCLYDE logo
Current languageEN
Cybersecurity newscybersecuritycheckpoint

Check Point gateway intrusions turn destructive

Check Point describes PHP2Shell intrusions, local privilege escalation and an ESXi wiper. Patching and persistence investigation belong in the same response.

Published on

By Soclyde

A technician disconnects a network gateway in a logistics depot

In summary

  • The November 12 research describes an attack chain from gateway to ESXi.
  • Destruction affected some first-wave cases rather than every target.
  • Patching should be accompanied by an intrusion investigation.

Explore next

Soclyde resources

Article contents

On November 12, 2026, Check Point Research published an investigation connecting Mobile Access gateway intrusions to data destruction on VMware ESXi. For a business using those remote-access systems, the issue extends beyond patching PHP: what happened behind the gateway also needs investigation.

One observed chain, two distinct waves

The research connects PHP2Shell, local escalation through CVE-2026-123039, TSGA persistence and movement to ESXi. It distinguishes the October 30 wave, with destruction in some cases, from November 2 activity with none observed. It does not establish confident attribution.

These new findings complement our earlier PHP patch coverage. They do not mean that every PHP installation or Check Point customer experienced the same intrusion.

Look beyond the VPN entry point

BleepingComputer describes the role of the destroy_v6 wiping tool. The Hacker News explains that privilege escalation requires prior local execution. Fixing one step therefore cannot document the condition of the entire attack chain.

We recommend requesting an inventory of exposed appliances, versions and measures taken from your provider. A reply saying the VPN works does not answer questions about persistent access or internal system integrity.

Follow the vendor’s remediation instructions

Check Point recommends the November Jumbo Hotfix for management servers and security gateways. Use the vendor advisory to confirm its application to your version. We recommend coordinating maintenance with the remote-access owner and preserving initial evidence useful to the investigation before reinstalling.

If compromise is suspected, have the responsible team define containment. Avoid restoring the gateway solely because an update completed without an error.

Review internal access and restoration

Ask for the investigation to cover service accounts, administrative hypervisor access and paths reachable from the gateway. For virtualized infrastructure, also prepare evidence that restoration can use an appropriate, verified backup.

If secrets need replacement, coordinate rotation with cleanup. Giving fresh credentials to a still-compromised machine can undermine the rotation. Record operations without recording the passwords themselves.

The connection with Soclyde

The Check Point chain illustrates why administrative logins should be distinct and easy to find. Soclyde keeps them in an encrypted vault on your devices, reducing scattered copies in exchanges with a provider. It does not patch the gateway, remove TSGA or restore deleted files.

What to remember

Request evidence of patching and an investigation conclusion, alongside a successful restart. For human accounts selected for rotation, prepare unique passwords with the Soclyde generator.

Frequently asked questions

Did the wiper affect every target?

No. Check Point reports destruction in some first-wave cases and no evidence of destructive activity in the second wave.

Can the privilege flaw alone be exploited remotely?

CVE-2026-123039 requires existing local code execution. In this chain, attackers first obtained access through PHP2Shell.

Does a patch establish that the gateway is clean?

No. The described intrusions include persistence mechanisms. Have the gateway and reachable internal systems assessed before closing the incident.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading