News with an accent.

Edificio de Check Point Software Technologies en Tel Aviv.Avi1111 (Wikimedia Commons, CC BY-SA 4.0)
Privacy

Check Point root flaw used to wipe data on ESXi servers

Attackers got in through the Mobile Access portal and gained root with CVE-2026-123039. Hotfixes cover R81.20 through R82.20, but not R81.10 or R81.

Check Point security gateways with the Mobile Access portal exposed to the internet were the way in for a string of intrusions that ended with data wiped on a VMware ESXi server. The attackers escalated to root, full control of the machine, through CVE-2026-123039, a flaw in Check Point's own product that now has hotfixes for four release lines. The account rests on a detailed analysis of the intrusions dated Nov. 12.

The company acknowledges active exploitation against a couple of dozen customers. Everything below comes from its two documents; there is no independent confirmation yet.

How the flaws were chained

The way in came first. Mobile Access was exposed by PHP2Shell, the name Check Point gives to two critical PHP flaws (CVE-2026-109618 and CVE-2026-109619) that allow code to run without logging in. PHP had released emergency patches on Oct. 21. Activity began roughly a week after a fix became available, the company says, and the first attacks date to Oct. 30.

Next came the jump to root. CVE-2026-123039 carries a CVSS score of 7.8 and sits in the DynamicCLI process. A gateway is the machine that separates an internal network from the internet; with full control over it, the intruder was no longer a limited visitor.

Then the damage. From the gateway, the attackers used SSH, through the vpxuser account ESXi uses for administration, to reach a virtualization host. There they ran destroy_v6, a *wiper*: a program built to destroy data, not to demand a ransom. It walks a directory and deletes the files, overwriting them with zeros first by default, and leaves a note called DREAM_ANNEXATION.txt in every folder it touches.

Organizations in Israel were the targets of the first wave, on Oct. 30, and several of them lost data. The second wave, on Nov. 2, hit companies in several countries and sectors; there is no evidence of destruction from that one so far. The analysis does not name those countries or tie the attacks to any group, and attribution remains unconfirmed. It does not mention victims in Mexico.

Affected versions and fixes

Advisory sk1000362 covers Force Firewalls, Management and Log Servers, Multi-Domain Security Management, Multi-Domain Log Server and Maestro Orchestrator. Spark Firewalls and Smart-1 Cloud are not affected.

VersionFix, per the advisory
R82.20Jumbo Hotfix Accumulator, from Take 14
R82.10Jumbo Hotfix Accumulator, from Take 52
R82Jumbo Hotfix Accumulator, from Take 132
R81.20Jumbo Hotfix Accumulator, from Take 174
R81.10 and R81No patch in the advisory; manual mitigation only

Source: Check Point Support, sk1000362

For R81.10 and R81, Check Point's mitigation is to stop the dynamic_server process. The trade-off: Dynamic CLI commands stop working.

What to look for

For anyone going through logs, the analysis lists these indicators of compromise:

  • Connections from the addresses 130.94.19[.]204 and 130.94.19[.]168.
  • In the templates folder, files named `zz*.tpl`; on the system, `/tmp/CPconfigdaemon` and `/lib/libcpfwcommon.so`.
  • Traffic on TCP port 11072 and the socket `/tmp/.p_sock`.

A wiper leaves nothing to negotiate, so what matters is whether an offline backup exists before one strikes. For Mexican companies that offer remote access through Mobile Access, the immediate question is which release line they run, and whether it appears in the table with a hotfix or among the two that rely on the manual mitigation.

Keep reading

El Mediático counts visits without cookies, with its own measurement and with Google Analytics, which receives basic data about your visit. Only if you accept does Google Analytics also store cookies and, where advertising is active, show personalized ads. You can accept all, reject all, or choose what to allow. The cookie policy is available in Spanish only. More about cookies (Spanish)