An attacker abused CyberPower PowerPanel Business, software that manages uninterruptible power supplies, to execute scripts with SYSTEM privileges on a domain controller, Symantec reported. The intrusion used a built-in feature of the product rather than a software vulnerability.
PowerPanel Business Script Feature Gave the Attacker SYSTEM Execution
PowerPanel Business can launch a script when a power event occurs, and its service runs that script as SYSTEM. According to Symantec, the attacker uploaded scripts through the product’s web console. Because the feature works as designed, the attacker needed no software bug, no new service and no scheduled task to get code running at the highest local privilege level.
Symantec did not name the victim or the threat actor.
Scripts Staged an Antivirus Killer and Copied the Active Directory Database
The uploaded scripts staged an antivirus killer and copied the Active Directory database. A persistent implant was then loaded through DLL sideloading. For most of the intrusion, the attacker relied on tools already built into Windows.
Copying the Active Directory database means the credential store of the domain was exposed, the outcome Symantec lists as credential database theft and persistence on a domain controller.
High-Value Hosts Often Run the Same Management Software
PowerPanel Business often runs on high-value systems, including hypervisors, database servers and file servers. Those machines are the ones that need protection against power loss, which places the power management software on hosts attackers want to control. An administrative console for the software becomes a route to running code on any machine where the agent is installed.
Living Off the Land Reduces Detection Opportunities
The attacker’s reliance on a legitimate product feature and Windows built-in tools left little malware to detect during the early stages. No exploit was involved, so patching would not have prevented this path. The antivirus killer staged by the scripts did, however, leave a trace of intent, and the DLL sideloading step introduced a persistent implant that stayed on the domain controller.
What Symantec Did and Did Not Disclose
Symantec published its report on November 18, and trade coverage followed the next day. The source reporting does not describe mitigation steps, and it identifies neither the victim nor the actor behind the intrusion. The available details therefore describe a technique rather than a specific campaign: an attacker with access to the web console can turn a UPS script hook into SYSTEM-level code execution.
The case illustrates a category of risk that sits outside vulnerability management, where a legitimate administrative feature, rather than a flaw, supplies the privilege the attacker needs. Organizations that run PowerPanel Business have a console that can execute scripts as SYSTEM on the hosts it manages, including domain controllers, and the Symantec report documents one intrusion in which an attacker used that capability to copy a domain’s Active Directory database.
Where the Technique Fits Among Living-Off-the-Land Intrusions
The intrusion relied on a feature rather than a flaw, which places it in the category of living-off-the-land activity. Symantec noted that the attacker used mostly Windows built-in tools after the scripts ran. The sequence is a compact one: web console access, script upload, SYSTEM execution on a power event, an antivirus killer, a copy of the Active Directory database, and DLL sideloading for persistence. Each stage uses an ordinary capability, and the first step shows that access to the PowerPanel Business console was enough to start the chain. How the attacker reached the console is not described in the reporting.
The Symantec report also leaves open how widely the technique could apply. PowerPanel Business runs on hypervisors, database servers and file servers as well as domain controllers, so the same console feature could in principle run scripts as SYSTEM on any of those hosts. The reporting documents only the single domain controller intrusion, and does not say whether the attacker used the same method elsewhere in the victim network.
