CyberPower PowerPanel Business as a SYSTEM script channel on a domain controller: Symantec traces ntds.dit extraction with ntdsutil ifm and esentutl /vss and a side-loaded implant to scripts that the UPS-management service ppbed.exe runs as SYSTEM; Symantec does not say how the console was reached and no actor is named
Symantec: attacker ran SYSTEM commands on a domain controller through CyberPower PowerPanel Business, then took ntds.dit
Defender actions
- On every host that runs CyberPower PowerPanel Business, domain controllers first, compare the extcmd and temp\\profile\\extcmd folders with the product defaults and compare the extcmd folders and the console's event-to-command assignments with what administrators configured and treat unknown scripts as hostile; where the techniques Symantec lists are found (ntdsutil or esentutl on a domain controller, scripts staged under extcmd that no administrator configured, a side-loaded implant), assume Active Directory credentials are exposed and plan a krbtgt reset and wider credential rotation, because Symantec saw this channel used to export ntds.dit from a domain controller.
Analysis
Symantec analysed an intrusion in which the attacker used CyberPower PowerPanel Business (PPB), software that manages UPS devices, as the execution channel on a Windows domain controller (Symantec, 2026-11-18). Scripts placed in the product's extcmd folder and staged first under temp\profile\extcmd, are run by the PPB service ppbed.exe as SYSTEM, so the commands of the chain have ppbed.exe as their ancestor and the lineage runs ppbed.exe, cmd.exe, powershell.exe and then the implant (Symantec, 2026-11-18). The attacker pushed the scripts to the PPB web service endpoint /local/rest/v1/file/upload on TCP port 3052, worked hands-on, iterating scripts until ntds.dit was exported with ntdsutil ifm and esentutl /vss, and then side-loaded the implant, an old trusted executable paired with an unknown DLL in a user-profile path (Symantec, 2026-11-18). The channel is a documented product function: CyberPower describes user-programmable command executions for event actions (CyberPower, 2026-11-19), and Symantec notes the attacker did not use power events to trigger them (Symantec, 2026-11-18).
Symantec does not say how the attacker reached the console; public advisories or stolen administrator credentials could give that access, and it names no actor, victim sector or product version (Symantec, 2026-11-18). CISA's 2024 advisory lists PowerPanel Business 4.9.0 and prior as affected by weaknesses fixed in version 4.10.1 or later, which Symantec does not cite (CISA, 2024-05-02).
Triage: the activity looks like a power-management product launching cmd.exe, which defenders may dismiss as a routine power-related recovery process; scripts or event-to-command assignments that no administrator configured, children that are not shutdown or notification routines (which follows from the mechanism) and the absence of a preceding power event separate it from benign use (Symantec, 2026-11-18).
Cited evidence
The commands in this attack chain have ppbed.exe as their ancestor and run as SYSTEM.
In process telemetry, the activity looks like a power-management product launching cmd.exe, which defenders may dismiss as a standard power-related recovery process without further investigation.
Any of these, or stolen administrator credentials, could give an attacker the necessary console access to carry out the attack described in this blog.
If you find them, assume Active Directory credentials are exposed and plan a krbtgt reset and wider credential rotation.
Sources3
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.